<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - No way to filter devices"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63807#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - No way to filter devices"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63807">bug 63807</a>
from <span class="vcard"><a class="email" href="mailto:marcandre.lureau@gmail.com" title="Marc-Andre Lureau <marcandre.lureau@gmail.com>"> <span class="fn">Marc-Andre Lureau</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=63807#c2">comment #2</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=63807#c1">comment #1</a>)
> > This is fixed by this commit, closing:
> > <a href="http://cgit.freedesktop.org/spice/spice-gtk/commit/">http://cgit.freedesktop.org/spice/spice-gtk/commit/</a>
> > ?id=0ebcc23c0642d2bddcb05ed4152497c99cb3ca1d
>
> Sorry but you are not getting away that easy. :) As I pointed out on IRC,
> its a very ugly API if you are asking apps to give you a very cryptic string
> for filter. Surely you can add some enums/flags and allow apps to filter
> through that. If you fail in that, at the very least add some docs
> explaining the syntax of the filter string you are expecting from apps.</span >
I have to disagree, a query string is actually more friendly API here.
However, I agree with you the API could be better documented (move the filter
description to the API section & add links).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>