DisplayFusion RSS: Triggers accepting junctions as Process Filename

RE: Triggers accepting junctions as Process Filename

Binary Fortress Software — Fri, 04 Oct 2019 19:04:45 GMT

Excellent, glad to hear it!

RE: Triggers accepting junctions as Process Filename

Binary Fortress Software — Fri, 04 Oct 2019 18:51:44 GMT

just perfect as usual

RE: Triggers accepting junctions as Process Filename

Binary Fortress Software — Fri, 04 Oct 2019 17:30:21 GMT

You can use wildcards in the Trigger rule, so if the full path is something like this:

C:\MobaxTerm11.0\MobaXterm.exe

, you can just put

*MobaXterm.exe

in the Process Filename and it will match that EXE, regardless of what folder it's in.

Hope that helps!

Triggers accepting junctions as Process Filename

Binary Fortress Software — Thu, 03 Oct 2019 10:41:50 GMT

Hello,
Would be useful if the triggers could be defined using junctions as "process filename".
I understand that technically this would imply a résolution of the process pointed at by the junction prior to checking if it matches with a running process.
For applications that I upgrade frequently and have several triggers defined (ie Mobaxterm for instance), I need to update the triggers each time I install a new release (new folder Mobaxterm12.1, previous one was Mobaxterm11.0 for instance so "Process Filename" changes). I would prefer to create once a windows junction (ie Mobaxterm junction pointing to the latest version Mobaxterm12.1) and when I upgrade I change my junction without touching the definition of triggers inside DisplayFusion.
Best Regards,
Manuel