Maintain "Persistence" of Find after done command is completed while routing.

Paul, I believe that the intended use model (and how I've been using the application modes) is to not necessarily use the commands.  And then, your find filter is retained as it switches to the different application mode. I tend to leave all objects selected in each application mode, When you do this, in Etch Edit, it knows that if you hover over a pin and click on it, it knows that you want to add connect.  Similarly, if you are in placement edit mode and you click on the same pin, it knows that you want to move the component.  This way, I eliminate the notion of picking my action first and then picking where I want to apply that action.  I still pick the application mode first, but now the list of available actions is greatly reduced (mostly add connect and slide in etch edit).  Once you are outside of getting all of your standard etch, and placements and shapes, then I go back into General Edit mode and continue to operate as we used to back before the application modes were a thing.

If for example I want to focus in on one particular thing (e.g. moving text only in placement edit), then I will use the super filter.  The super filter then selects just that one type of object.  It's available from the right-click menu and you don't have to go find it over in the window pane.  The 'super filter' is not retained as you switch between application modes and is also overridden if you select a command within an application mode.

I guess I'm saying, leave the find filter for all application modes, use the application modes to inherently drive your find filter, then utilize super filter when it makes sense and if all else fails, go to General Edit and use the find filter in a 'legacy' manner.  That's at least what I've been using, and it's been working well.  Granted, it's been very difficult to shake old habits, but when I remember to use the tool that way, it does work pretty well.

~ Pat

Pat,

What I did is went to each mode  without invoking any commands and set the find filter for the objects of interest. So right now I have different find options for
both General Edit Mode and etch edit mode. When in etch edit and selecting done after a trace has been routed, the Find filter does indeed retain the settings
I gave it. This is what I was after 

So it is interesting though not really obvious that you would have to set find for each mode in advance. You have me wondering now if those find
settings get retained on a config file or are they on a database by database basis ?

If by a database retention only then a little macro should be an ez fix, Or save out a brd as a template for new designs.

Rick had pointed out about using the tab key too as a method to cycle the find objects. I had configured the data tips earlier and it is all working very well.
I really like how Allegro is handling etch, it is extremely fluid.

To automate things a bit I configured two strokes, One for adding clines and one to delete them. This thing is just working great and it is fast too.
I don't even have to touch a menu for those items now... it is pretty cool. I was looking for a way to include the "toggle" option so it would remain
checked always while routing, that mode just seems better to me than the unchecked default, anyway I incorporated that into the stroke command
and Success ! Yay !.

I guess the secret if you will is in the prep.

Thanks for the help and a really good tip on this, thanks to Rick too. 

All the best Paul.

For delete, I might be inclined to add the following to my env file

funckey d "prepopup; pop dyn_option_select @:@Delete"

when in the design you hover over a cline, segment, text, shape, via and use the "d" key. No mouse involved.

Toggle I might do something like:

alias t2 set toggle on
alias t1 set toggle off
funckey t 'settoggle CMD t1 t2;$CMD'

Then, using the t key, you can enable or disable the toggle command.

Rik, indeed that works well and also allows one to tab key select based on the find option before deleting.
You can also do a window select as well and take out everything in one go.

I used to use funckey d  "delete; pick_to_grid -cursor; done" but have replaced it with yours.

To help with routing and in particular for on the fly routing width changes I added in to the env file

funckey x "prepopup ; pop dyn_option_select 'Options@:@Line width@:@New...' ;setwindow form.new_item"

Seems to work good.

Right now I have a function that just combines the toggle with adding a cline but will give your suggestion a try out.

funckey w  "add connect; toggle; etch length"

In 17.2 I noticed cadence has extended the UI menus so that a user can assign their own options via a right click Icon.
It is kind of handy and can save a trip to the main menus. Only thing is it is based on available commands as far
as I can see. It would be cool if there was something like having custom macros assignable to physical Icons in the UI.
My thinking is to do this now you kind of have to go the Skill road.

I may try combine your good example of toggle with something like the cursors. It would be neat to be able to toggle
through all of them just using one key without having to go to user preferences.

Rik, indeed that works well and also allows one to tab key select based on the find option before deleting.
You can also do a window select as well and take out everything in one go.

I used to use funckey d  "delete; pick_to_grid -cursor; done" but have replaced it with yours.

To help with routing and in particular for on the fly routing width changes I added in to the env file

funckey x "prepopup ; pop dyn_option_select 'Options@:@Line width@:@New...' ;setwindow form.new_item"

Seems to work good.

Right now I have a function that just combines the toggle with adding a cline but will give your suggestion a try out.

funckey w  "add connect; toggle; etch length"

In 17.2 I noticed cadence has extended the UI menus so that a user can assign their own options via a right click Icon.
It is kind of handy and can save a trip to the main menus. Only thing is it is based on available commands as far
as I can see. It would be cool if there was something like having custom macros assignable to physical Icons in the UI.
My thinking is to do this now you kind of have to go the Skill road.

I may try combine your good example of toggle with something like the cursors. It would be neat to be able to toggle
through all of them just using one key without having to go to user preferences.