Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There are generally only a few "acceptable" solutions to problems like this:</p> <p><strong>Simulate user input</strong></p> <p>Programatically send keystrokes and mouse clicks</p> <ul> <li>Pros: Compatible with most GUI programs you can think of</li> <li>Cons: Kludgy, not good at handling any kind of unexpected behavior (i.e. error dialogs). Have to know which windows you're expecting to communicate with ahead of time. Dialogs change from one version to the next, so your program often stops working with new releases.</li> </ul> <p><strong>Program API</strong></p> <p>Communicate directly with the program using calls that it natively understands (play, stop, etc).</p> <ul> <li>Pros: Much easier programming experience, cleaner and fewer bugs than simulating input</li> <li>Cons: Very few applications actually expose an API. And for those that do, you're limited to the functionality supported by the API (which may not include everything the program is capable of).</li> </ul> <p><strong>Scripts</strong></p> <p>Some programs allow scripting languages (VBScript for example)</p> <ul> <li>Pros: Same pros as API</li> <li>Cons: Have to somehow programatically get the program to open the script, which may or may not be easy depending on the program.</li> </ul> <p>As for those programs specifically I can't comment. I don't know if they expose any kind of API. I imagine some of them might (media player for example I would think has some of this). Don't quote me on that though. I hope this helps.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload