Hi Daniele and Team,
I was in V1 version of Log4OM and successfully upgraded to V2 and happy with the features.
I have a question related to the AutoStart option in the Program Configuration UI. I have configured 3 external applications to start along with the Log4OM V2 and all are starting without any trouble, but when I am closing the Log4OM those applications remains as it and not getting closed. How to force the external applications to close when Log4OM closes? Does the plan "OnProfileOpen" works only when the application starts? Is there a possibility to create another plan like "OnProfileClose"?
/Br
VU3ESV
Clossing the External applications after the Log4OM V2
Re: Clossing the External applications after the Log4OM V2
It doesn't work for me either. I have setup my Hamlib in server mode by running rigctld in startup. It starts fine and takes all the arguments, but doesn't close on exit. I have filled the process name also as rigctld.exe (as in Task Manager) and checked Singleton and Kill.
Looks like it is not intended to close on exit. The process can only be started and based on the Singleton/Kill setting, the existing process may be terminated upon start up. Anyway this is also not working for me.
73
Bejoy
VU3BOJ
Looks like it is not intended to close on exit. The process can only be started and based on the Singleton/Kill setting, the existing process may be terminated upon start up. Anyway this is also not working for me.
73
Bejoy
VU3BOJ
Re: Clossing the External applications after the Log4OM V2
I have never been able to get applications to automatically close, once opened by the V2 Auto Start feature, no matter what I set in the Win Process name field. It has been reported to Daniele. I will remind him. Its also on the Mantis list.
Doug
W7DRM
Doug
W7DRM
Doug - NN7D
Gig Harbor, WA, USA
Gig Harbor, WA, USA