Processing Ajax...

Close Dialog


Close Dialog

Close Dialog

Close Dialog

User Image
6 discussion posts
Im loving the triggers features of DF, its probably my favourite and most used feature.

Can we possibly have 'Is Not' options for matched conditions.

So I can have it only run if the monitor profile is anythign but X Profile.

Also Could we have 'Not matched' as an option in Monitor Profile, so then I can create triggers which onyl run if the monitor profile is nto matched, and ones that run if it is matched (regardless of which profile it matches to)
and also conditions that run it it doesnt match a specific profile.

Multiple selections would be handy too for this, SO I can say if monitor profile is X or Y, or is not X orr Y, or is X or unmatched. Etc ETc. it would be much more pwoerful for deciding which of my gui applications (docks and stuff) run or close in which conditions.

Another thing that would be handy is an easy way in the gui to just run a batch file (shown or hidden as an option) Or call a REST API (hidden). I appreciate these are scriptable but it would make it much more user friendly.
Jun 3, 2023  • #1
Owen Muhlethaler (BFS)'s profile on
I've added this to our feature request list. We don't guarantee that feature requests will be implemented, or offer timelines on possible implementation. We'll be sure to let you know if we do add it to our planned features in a future version.

For the Window Text and Window class conditions, you can add a minus symbol infront of your entry, and it will turn it into a "Does not contain:" match.

Jun 5, 2023  • #2
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(-)  Login to Vote(-)