Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
If i quit EventGhost and trigger it, EventGhost just starts. That proves the path to the exe is correct. If Event ghost is running already and i trigger the command ...
I triggert events by command lines for former versions of EventGhost (4.x) sucessfully.
Example: "C:\Program Files (x86)\EventGhost\eventghost.exe" -e Keyboard.LShift+F2 for a macro called "Volume Up" wich is triggered by the event "Keyboard.LShift+F2".
I had already been in contact with the author of gphotoshow pro.
Hes snet me the hint with the hard taskkill. He is aware of the problem, but had no better solution.
I had already been in contact with the author of gphotoshow pro.
Hes snet me the hint with the hard taskkill. He is aware of the problem, but had no better solution.
I use Windows 10 x64. The only way to stop a screensaver i found up to now is a hard taskkill. Example: taskkill /im gphoto~2.scr /t /f (for gphotoshow pro here). With that method, the screensaver is not able to store some values (wich pictures were shown in this case). I thied triggering keyboard ...