Quote:
Originally Posted by kiwidude
An alternative suggestion (since it is only fair if I say something I found unexpected is to suggest an alternative, however crap it may be) is:
(a) *Current search always stayed there
(b) a new entry of *dragon appeared below *Current search
|
Done, with the addition that the current search (the new line) is remembered. You can select some other search, then come back and select the 'new entry' again.
I don't see a need to clear that search if I select *current search with an empty search box. Instead I select index 0, which clears the restriction.
Quote:
My final comment - could the tooltip for the restriction dropdown show the full text of the current search when you have one selected. As it gets shortened in the non-resizable dropdown to illegibility 
|
Done
Quote:
Yes using a variable would work. Though I still need a disconnect method (I think) for invoking to allow the object to be garbage collected when I create a new instance by the user switching libraries. And obviously some connect code when the object gets created. So we'll see what I ens up with 
|
Yes, you certainly do need to disconnect if you abandon the instance. Alternatively, you can do the connection in the base plugin class that I am sure you don't abandon, then have it call whatever you want in the current instance.