<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c7">Comment # 7</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 <a class="email" href="mailto:zeenix@gmail.com" title="Zeeshan Ali <zeenix@gmail.com>"> Zeeshan Ali</a> <pre>(In reply to <a href="show_bug.cgi?id=63807#c6">comment #6</a>) > (In reply to <a href="show_bug.cgi?id=63807#c2">comment #2</a>) > > (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. > > I have to disagree, a query string is actually more friendly API here. You'll have to do better than just saying that. :) Most APIs can be "easy" with strings but more static APIs are always preferred for a few reasons. Firstly, you get errors from compiler if you screw up with static API. Secondly, with C many times developers just reference API from headers rather than docs if the API is obvious (which we should try our best to do). Also, its not nice that you have ignored this up til now when someone decided to fix the issue. :(</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>