Zugg Software :: View topic

Apprentice Joined: 06 Apr 2004 Posts: 173

I'm not sure if you'd classify this as a bug, a feature or just an annoyance.

the search filter seems to have ultimate precedence over editing.

If you have a word in the filter, such as %eval and modify a trigger you're currently looking at that has an eval in it (and remove that word), upon looking at the compiled code you are no longer looking at the same trigger.

Also, double clicking a variable/alias will not go to the definition of that variable while there is a word in the search bar.

Posted: Sat Sep 01, 2007 1:29 am

Yes, that's true. Call it a "feature" or an "annoyance". The Search bar creates a database filter. The package editor is a database viewer/editor. So if the records are being filtered, you will only see records that match the filter. There is no way to say "show settings that match these words, except for the one I just edited".

So, you just need to remember to clear the search bar when you don't want the view to be filtered.

Apprentice Joined: 06 Apr 2004 Posts: 173

Is there a way to have it only search when you hit a button instead of all the time? Once you've done your initial search you pretty much know which settings have the item in it.

EDIT: or you could make the trigger/alias/variable in the editing window not be affected by spontaneous view changes unless the user clicks on a new trigger...?

Posted: Mon Sep 03, 2007 5:14 pm

Unfortunately not. In the future if I rewrite the settings editor so that it doesn't use a live database, then this might be possible. But that requires a complete rewrite. The current settings editor was *designed* to be live, which means that filters run in real time against the database. So as soon as your setting no longer matches the filter, it is removed from the list. That's how live database viewers/editors work, sorry.