One of these objects holds a list of all the commands your app can perform, and despatches these commands when needed. More...
|Creates an ApplicationCommandManager. More...|
|Clears the current list of all commands. More...|
|void||registerCommand (const ApplicationCommandInfo &newCommand)|
|Adds a command to the list of registered commands. More...|
|void||registerAllCommandsForTarget (ApplicationCommandTarget *target)|
|Adds all the commands that this target publishes to the manager's list. More...|
|void||removeCommand (CommandID commandID)|
|Removes the command with a specified ID. More...|
|This should be called to tell the manager that one of its registered commands may have changed its active status. More...|
|int||getNumCommands () const noexcept|
|Returns the number of commands that have been registered. More...|
|const ApplicationCommandInfo *||getCommandForIndex (int index) const noexcept|
|Returns the details about one of the registered commands. More...|
|const ApplicationCommandInfo *||getCommandForID (CommandID commandID) const noexcept|
|Returns the details about a given command ID. More...|
|String||getNameOfCommand (CommandID commandID) const noexcept|
|Returns the name field for a command. More...|
|String||getDescriptionOfCommand (CommandID commandID) const noexcept|
|Returns the description field for a command. More...|
|StringArray||getCommandCategories () const|
|Returns the list of categories. More...|
|Array< CommandID >||getCommandsInCategory (const String &categoryName) const|
|Returns a list of all the command UIDs in a particular category. More...|
|KeyPressMappingSet *||getKeyMappings () const noexcept|
|Returns the manager's internal set of key mappings. More...|
|bool||invokeDirectly (CommandID commandID, bool asynchronously)|
|Invokes the given command directly, sending it to the default target. More...|
|bool||invoke (const ApplicationCommandTarget::InvocationInfo &invocationInfo, bool asynchronously)|
|Sends a command to the default target. More...|
|virtual ApplicationCommandTarget *||getFirstCommandTarget (CommandID commandID)|
|Chooses the ApplicationCommandTarget to which a command should be sent. More...|
|void||setFirstCommandTarget (ApplicationCommandTarget *newTarget) noexcept|
|Sets a target to be returned by getFirstCommandTarget(). More...|
|ApplicationCommandTarget *||getTargetForCommand (CommandID commandID, ApplicationCommandInfo &upToDateInfo)|
|Tries to find the best target to use to perform a given command. More...|
|void||addListener (ApplicationCommandManagerListener *listener)|
|Registers a listener that will be called when various events occur. More...|
|void||removeListener (ApplicationCommandManagerListener *listener)|
|Deregisters a previously-added listener. More...|
|static ApplicationCommandTarget *||findDefaultComponentTarget ()|
|Looks for a suitable command target based on which Components have the keyboard focus. More...|
|static ApplicationCommandTarget *||findTargetForComponent (Component *)|
|Examines this component and all its parents in turn, looking for the first one which is an ApplicationCommandTarget. More...|
One of these objects holds a list of all the commands your app can perform, and despatches these commands when needed.
Application commands are a good way to trigger actions in your app, e.g. "Quit", "Copy", "Paste", etc. Menus, buttons and keypresses can all be given commands to invoke automatically, which means you don't have to handle the result of a menu or button click manually. Commands are despatched to ApplicationCommandTarget objects which can choose which events they want to handle.
This architecture also allows for nested ApplicationCommandTargets, so that for example you could have two different objects, one inside the other, both of which can respond to a "delete" command. Depending on which one has focus, the command will be sent to the appropriate place, regardless of whether it was triggered by a menu, keypress or some other method.
To set up your app to use commands, you'll need to do the following:
- Create a global ApplicationCommandManager to hold the list of all possible commands. (This will also manage a set of key-mappings for them).
- Make some of your UI components (or other objects) inherit from ApplicationCommandTarget. This allows the object to provide a list of commands that it can perform, and to handle them.
- Register each type of command using ApplicationCommandManager::registerAllCommandsForTarget(), or ApplicationCommandManager::registerCommand().
- If you want key-presses to trigger your commands, use the ApplicationCommandManager::getKeyMappings() method to access the key-mapper object, which you will need to register as a key-listener in whatever top-level component you're using. See the KeyPressMappingSet class for more help about setting this up.
- Use methods such as PopupMenu::addCommandItem() or Button::setCommandToTrigger() to cause these commands to be invoked automatically.
- Commands can be invoked directly by your code using ApplicationCommandManager::invokeDirectly().
When a command is invoked, the ApplicationCommandManager will try to choose the best ApplicationCommandTarget to receive the specified command. To do this it will use the current keyboard focus to see which component might be interested, and will search the component hierarchy for those that also implement the ApplicationCommandTarget interface. If an ApplicationCommandTarget isn't interested in the command that is being invoked, then the next one in line will be tried (see the ApplicationCommandTarget::getNextCommandTarget() method), and so on until ApplicationCommandTarget::getNextCommandTarget() returns nullptr. At this point if the command still hasn't been performed, it will be passed to the current JUCEApplication object (which is itself an ApplicationCommandTarget).
To exert some custom control over which ApplicationCommandTarget is chosen to invoke a command, you can override the ApplicationCommandManager::getFirstCommandTarget() method and choose the object yourself.
Constructor & Destructor Documentation
Creates an ApplicationCommandManager.
Once created, you'll need to register all your app's commands with it, using ApplicationCommandManager::registerAllCommandsForTarget() or ApplicationCommandManager::registerCommand().
Make sure that you don't delete this if pointers to it are still being used by objects such as PopupMenus or Buttons.
Member Function Documentation
Clears the current list of all commands.
Note that this will also clear the contents of the KeyPressMappingSet.
|void ApplicationCommandManager::registerCommand||(||const ApplicationCommandInfo &||newCommand||)|
Adds a command to the list of registered commands.
- See also
|void ApplicationCommandManager::registerAllCommandsForTarget||(||ApplicationCommandTarget *||target||)|
Adds all the commands that this target publishes to the manager's list.
This will use ApplicationCommandTarget::getAllCommands() and ApplicationCommandTarget::getCommandInfo() to get details about all the commands that this target can do, and will call registerCommand() to add each one to the manger's list.
- See also
Removes the command with a specified ID.
Note that this will also remove any key mappings that are mapped to the command.
This should be called to tell the manager that one of its registered commands may have changed its active status.
Because the command manager only finds out whether a command is active or inactive by querying the current ApplicationCommandTarget, this is used to tell it that things may have changed. It allows things like buttons to update their enablement, etc.
This method will cause an asynchronous call to ApplicationCommandManagerListener::applicationCommandListChanged() for any registered listeners.
Returns the number of commands that have been registered.
- See also
Returns the details about one of the registered commands.
The index is between 0 and (getNumCommands() - 1).
Returns the details about a given command ID.
This will search the list of registered commands for one with the given command ID number, and return its associated info. If no matching command is found, this will return nullptr.
Returns the name field for a command.
An empty string is returned if no command with this ID has been registered.
- See also
Returns the description field for a command.
An empty string is returned if no command with this ID has been registered. If the command has no description, this will return its short name field instead.
- See also
|Array<CommandID> ApplicationCommandManager::getCommandsInCategory||(||const String &||categoryName||)||const|
Returns a list of all the command UIDs in a particular category.
- See also
Invokes the given command directly, sending it to the default target.
This is just an easy way to call invoke() without having to fill out the InvocationInfo structure.
|bool ApplicationCommandManager::invoke||(||const ApplicationCommandTarget::InvocationInfo &||invocationInfo,|
Sends a command to the default target.
This will choose a target using getFirstCommandTarget(), and send the specified command to it using the ApplicationCommandTarget::invoke() method. This means that if the first target can't handle the command, it will be passed on to targets further down the chain (see ApplicationCommandTarget::invoke() for more info).
invocationInfo this must be correctly filled-in, describing the context for the invocation. asynchronously if false, the command will be performed before this method returns. If true, a message will be posted so that the command will be performed later on the message thread, and this method will return immediately.
- See also
Chooses the ApplicationCommandTarget to which a command should be sent.
Whenever the manager needs to know which target a command should be sent to, it calls this method to determine the first one to try.
If you need to make sure all commands go via your own custom target, then you can either use setFirstCommandTarget() to specify a single target, or override this method if you need more complex logic to choose one.
It may return nullptr if no targets are available.
Tries to find the best target to use to perform a given command.
This will call getFirstCommandTarget() to find the preferred target, and will check whether that target can handle the given command. If it can't, then it'll use ApplicationCommandTarget::getNextCommandTarget() to find the next one to try, and so on until no more are available.
If no targets are found that can perform the command, this method will return nullptr.
If a target is found, then it will get the target to fill-in the upToDateInfo structure with the latest info about that command, so that the caller can see whether the command is disabled, ticked, etc.
|void ApplicationCommandManager::addListener||(||ApplicationCommandManagerListener *||listener||)|
Registers a listener that will be called when various events occur.
|void ApplicationCommandManager::removeListener||(||ApplicationCommandManagerListener *||listener||)|
Deregisters a previously-added listener.
Looks for a suitable command target based on which Components have the keyboard focus.
This is used by the default implementation of ApplicationCommandTarget::getFirstCommandTarget(), but is exposed here in case it's useful.
The documentation for this class was generated from the following file: