Packages of Commands
When Qubit Master starts, it loads the basic (shared, common, default)
package of commands Commands.qml. This file cannot be circumvented or unloaded.
Each user is also assigned their own package of commands Username.qml
which is automatically loaded whenever that user becomes active. This add-on package can
be unloaded and any other package can be loaded in its place (even other user's packages).
This mobility of the second package allows for creation of application
specific packages of commands. Since there are both key-pressing and mouse-clicking
commands, any command that is on the menu or the toolbar of an application that follows
Microsoft guidelines can be easily executed by Qubit Master.
Once one such (application specific) package is constructed it needs to be
loaded every time user works in that application. This could be done by hand.
Or, Package Localization feature can be used. It
works similarly to the Command Localization feature but
instead of activating individual commands it loads add-on packages. The connection between
the window title (keyword) and the package (file name) is specified in the Package
Localization Rules dialog which is accessed from the File menu (File->Localization...):
For Package Localization to actually function two things are necessary:
File->Active Loading menu item must be checked
There should be some entries in the dialog above.
Difference in the behavior of Package Localization as opposed to Command
Localization is that when the specified window looses focus, the package is unloaded after
a user-specified delay (and not immediately as is the case with individual commands).
Example:
A package of commands specialized for Internet Explorer 5.x can be
created. It would contain "Save Page" group command which would be a sequence of
commands as follows:
<Alt+F> - opens the File menu
<KeyIn(a)> - selects Save As...
from the menu
<WaitFor(save web page,500,Say(Problem saving
this web page...))> - waits for a Save As dialog; if the dialog does not
show up after 5 seconds the user is informed that there was a problem saving the page
<Press Save> - presses the Save
button
The package would also contain "Save Image" command which would
be:
<Right()> - right clicks at the current
cursor position, opening the image's context menu
<KeyIn(s)> - selects Save Picture
As... menu item
<WaitFor(save picture,500,Say(Problem saving
this image...))> - waits for a Save Picture dialog; if the dialog does not
show up after 5 seconds the user is informed that there was a problem saving the picture
<Press Save> - presses the Save
button
