I would find it very useful to be able to have Logos4 send additional commands out to the COM API, to control or trigger acts in an external application.
Rather than change to the other application, and submit commands there, it would in some cases be better to stay within Logos4, and have the other application stay in the background, or maybe not even have a UI during normal use.
The current Logos4 Command Box makes attempts to match just about anything to something it knows. In general, this seems to work well, so any new function would need to play well with the current operations.
I don't think there is any practical way that any current command should be sent out the API, because Logos4 already does one of: (1) Does the command it knows, or (2) peforms a search operation.
The new feature would need to start with some kind of marker, maybe supplied by the external application, followed by the contents of the rest of the command. In such a case, Logos4 should not do anything with it directly, other than send it out on a new Event.
An example might be:
The external application does a call to LogosApplication.RegisterCommandPrefix("Playaudio")
In Logos4, the user types "Playaudio something whatever" in the Command Box
Logos4 "knows" this is an external command, so does NOT perform a search, but instead fires the COM API with the text entered.
The application gets the new COM API Event LogosApplication.UserCommand(Command as Object[String]).
The application takes some action, as it seems fit.
Such a command can then be dragged to an Icon on the Toolbar, or stored to the Favorites Panel.
Thankyou for considering this request.
P.S. This model of operation would allow external solutions to a number of the feature-requests users are making, but where there is no clues that a solution is being planned or due soon.
