#include <kaction.h>
Inheritance diagram for KAction:

Public Slots | |
| virtual void | setText (const QString &text) |
| virtual bool | setShortcut (const KShortcut &) |
| virtual void | setWhatsThis (const QString &text) |
| virtual void | setToolTip (const QString &) |
| virtual void | setIconSet (const QIconSet &iconSet) |
| virtual void | setEnabled (bool enable) |
| virtual void | setShortcutConfigurable (bool) |
| virtual void | activate () |
Public Methods | |
| KAction (const QString &text, const KShortcut &cut, const QObject *receiver, const char *slot, KActionCollection *parent, const char *name) | |
| KAction (const QString &text, const QIconSet &pix, const KShortcut &cut, const QObject *receiver, const char *slot, KActionCollection *parent, const char *name) | |
| KAction (const QString &text, const QString &pix, const KShortcut &cut, const QObject *receiver, const char *slot, KActionCollection *parent, const char *name) | |
| KAction (const KGuiItem &item, const KShortcut &cut, const QObject *receiver, const char *slot, KActionCollection *parent, const char *name) | |
| KAction (const QString &text, const KShortcut &cut=KShortcut(), QObject *parent=0, const char *name=0) | |
| KAction (const QString &text, const KShortcut &cut, const QObject *receiver, const char *slot, QObject *parent, const char *name=0) | |
| KAction (const QString &text, const QIconSet &pix, const KShortcut &cut=KShortcut(), QObject *parent=0, const char *name=0) | |
| KAction (const QString &text, const QString &pix, const KShortcut &cut=KShortcut(), QObject *parent=0, const char *name=0) | |
| KAction (const QString &text, const QIconSet &pix, const KShortcut &cut, const QObject *receiver, const char *slot, QObject *parent, const char *name=0) | |
| KAction (const QString &text, const QString &pix, const KShortcut &cut, const QObject *receiver, const char *slot, QObject *parent, const char *name=0) | |
| KAction (QObject *parent=0, const char *name=0) | |
| virtual | ~KAction () |
| virtual int | plug (QWidget *w, int index=-1) |
| virtual void | plugAccel (KAccel *accel, bool configurable=true) |
| virtual void | unplug (QWidget *w) |
| virtual void | unplugAccel () |
| virtual bool | isPlugged () const |
| bool | isPlugged (const QWidget *container) const |
| virtual bool | isPlugged (const QWidget *container, int id) const |
| virtual bool | isPlugged (const QWidget *container, const QWidget *_representative) const |
| uint | kaccelCount () const |
| |
| virtual QString | text () const |
| virtual const KShortcut & | shortcut () const |
| virtual const KShortcut & | shortcutDefault () const |
| virtual bool | isEnabled () const |
| virtual bool | isShortcutConfigurable () const |
| virtual QString | whatsThis () const |
| virtual QString | toolTip () const |
| virtual QIconSet | iconSet (KIcon::Group group, int size=0) const |
| int | accel () const |
| void | setAccel (int key) |
| void | setStatusText (const QString &text) |
| int | menuId (int i) |
The KAction class (and derived and super classes) provides a way to easily encapsulate a "real" user-selected action or event in your program.
For instance, a user may want to paste the contents of the clipboard or scroll down a document or quit the application. These are all actions -- events that the user causes to happen. The KAction class allows the developer to deal with these actions in an easy and intuitive manner.
Specifically, the KAction class encapsulated the various attributes to an event/action. For instance, an action might have an icon that goes along with it (a clipboard for a "paste" action or scissors for a "cut" action). The action might have some text to describe the action. It will certainly have a method or function that actually executes the action! All these attributes are contained within the KAction object.
The advantage of dealing with Actions is that you can manipulate the Action without regard to the GUI representation of it. For instance, in the "normal" way of dealing with actions like "cut", you would manually insert a item for Cut into a menu and a button into a toolbar. If you want to disable the cut action for a moment (maybe nothing is selected), you woud have to hunt down the pointer to the menu item and the toolbar button and disable both individually. Setting the menu item and toolbar item up uses very similar code - but has to be done twice!
With the Action concept, you simply "plug" the Action into whatever GUI element you want. The KAction class will then take care of correctly defining the menu item (with icons, accelerators, text, etc) or toolbar button.. or whatever. From then on, if you manipulate the Action at all, the effect will propogate through all GUI representations of it. Back to the "cut" example: if you want to disable the Cut Action, you would simply do 'cutAction->setEnabled(false)' and the menuitem and button would instantly be disabled!
This is the biggest advantage to the Action concept -- there is a one-to-one relationship between the "real" action and all GUI representations of it.
KAction emits the activated() signal if the user activated the corresponding GUI element ( menu item, toolbar button, etc. )
If you are in the situation of wanting to map the activated() signal of multiple action objects to one slot, with a special argument bound to each action, then you might consider using QSignalMapper . A tiny example:
QSignalMapper *desktopNumberMapper = new QSignalMapper( this );
connect( desktopNumberMapper, SIGNAL( mapped( int ) ),
this, SLOT( moveWindowToDesktop( int ) ) );
for ( uint i = 0; i < numberOfDesktops; ++i ) {
KAction *desktopAction = new KAction( i18n( "Move Window To Desktop i" ).arg( i ), ... );
connect( desktopAction, SIGNAL( activated() ), desktopNumberMapper, SLOT( map() ) );
desktopNumberMapper->setMapping( desktopAction, i );
}
@sect General Usage:
The steps to using actions are roughly as follows
Here is an example of enabling a "New [document]" action
KAction *newAct = new KAction(i18n("&New"), "filenew",
KStdAccel::shortcut(KStdAccel::New),
this, SLOT(fileNew()),
actionCollection(), "new");
This line creates our action. It says that wherever this action is displayed, it will use "&New" as the text, the standard icon, and the standard shortcut. It further says that whenever this action is invoked, it will use the fileNew() slot to execute it.
QPopupMenu *file = new QPopupMenu; newAct->plug(file);That just inserted the action into the File menu. The point is, it's not important in which menu it is: all manipulation of the item is done through the newAct object.
newAct->plug(toolBar());And this inserted the Action into the main toolbar as a button.
That's it!
If you want to disable that action sometime later, you can do so with
newAct->setEnabled(false)and both the menuitem in File and the toolbar button will instantly be disabled.
Note: if you are using a "standard" action like "new", "paste", "quit", or any other action described in the KDE UI Standards, please use the methods in the KStdAction class rather than defining your own.
@sect Usage Within the XML Framework:
If you are using KAction within the context of the XML menu and toolbar building framework, then there are a few tiny changes. The first is that you must insert your new action into an action collection. The action collection (a KActionCollection) is, logically enough, a central collection of all of the actions defined in your application. The XML UI framework code in KXMLGUI classes needs access to this collection in order to build up the GUI (it's how the builder code knows which actions are valid and which aren't).
Also, if you use the XML builder framework, then you do not ever have to plug your actions into containers manually. The framework does that for you.
Definition at line 191 of file kaction.h.
|
||||||||||||||||||||||||||||
|
Constructs an action with text, potential keyboard shortcut, and a SLOT to call when this action is invoked by the user.
If you do not want or have a keyboard shortcut, set the This is the most common KAction used when you do not have a corresponding icon (note that it won't appear in the current version of the "Edit ToolBar" dialog, because an action needs an icon to be plugged in a toolbar...).
|
|
||||||||||||||||||||||||||||||||
|
Constructs an action with text, icon, potential keyboard shortcut, and a SLOT to call when this action is invoked by the user.
If you do not want or have a keyboard shortcut, set the
This is the other common KAction used. Use it when you
|
|
||||||||||||||||||||||||||||||||
|
Constructs an action with text, icon, potential keyboard shortcut, and a SLOT to call when this action is invoked by the user. The icon is loaded on demand later based on where it is plugged in.
If you do not want or have a keyboard shortcut, set the
This is the other common KAction used. Use it when you
|
|
||||||||||||||||||||||||||||
|
The same as the above constructor, but with a KGuiItem providing the text and icon.
|
|
||||||||||||||||||||
|
@obsolete |
|
||||||||||||||||||||||||||||
|
@obsolete |
|
||||||||||||||||||||||||
|
@obsolete |
|
||||||||||||||||||||||||
|
@obsolete |
|
||||||||||||||||||||||||||||||||
|
@obsolete |
|
||||||||||||||||||||||||||||||||
|
@obsolete |
|
||||||||||||
|
@obsolete |
|
|
Standard destructor |
|
|
|
|
|
Emulate user's interaction programmatically, by activating the action. The implementation simply emits activated(). |
|
||||||||||||
|
Get the QIconSet from which the icons used to display this action will be chosen. |
|
|
Returns true if this action is enabled. |
|
||||||||||||
|
returns whether the action is plugged into the given container with the given, container specific, representative container widget item. |
|
||||||||||||
|
returns whether the action is plugged into the given container with the given, container specific, id (often menu or toolbar id ) . |
|
|
returns whether the action is plugged into the given container |
|
|
returns whether the action is plugged into any container widget or not.
|
|
|
Returns true if this action's shortcut is configurable. |
|
|
|
|
||||||||||||
|
"Plug" or insert this action into a given widget. This will typically be a menu or a toolbar. From this point on, you will never need to directly manipulate the item in the menu or toolbar. You do all enabling/disabling/manipulation directly with your KAction object.
Reimplemented in KToggleAction, KSelectAction, KActionMenu, KToolBarPopupAction, KToggleToolBarAction, and KWidgetAction. |
|
||||||||||||
|
"Plug" or insert this action into a given KAccel. |
|
|
|
|
|
Enables or disables this action. All uses of this action (eg. in menus or toolbars) will be updated to reflect the state of the action. |
|
|
Sets the QIconSet from which the icons used to display this action will be chosen. |
|
|
Sets the keyboard shortcut associated with this action. |
|
|
Indicate whether the user may configure the action's shortcut. |
|
|
Definition at line 588 of file kaction.h. References setToolTip(), and text(). |
|
|
Sets the text associated with this action. The text is used for menu and toolbar labels etc. |
|
|
Sets the tooltip text for the action. This will be used as a tooltip for a toolbar button, as a statusbar help-text for a menu item, and it also appears in the toolbar editor, to describe the action. Referenced by setStatusText(). |
|
|
Sets the What's this text for the action. This text will be displayed when a widget that has been created by plugging this action into a container is clicked on in What's this mode. The What's this text can include QML markup as well as raw text. |
|
|
Get the keyboard shortcut associated with this action. |
|
|
Get the default shortcut for this action. |
|
|
Get the text associated with this action. Referenced by setStatusText(). |
|
|
Get the tooltip text for the action. |
|
|
"Unplug" or remove this action from a given widget. This will typically be a menu or a toolbar. This is rarely used in "normal" application. Typically, it would be used if your application has several views or modes, each with a completely different menu structure. If you simply want to disable an action for a given period, use setEnabled() instead.
Reimplemented in KWidgetAction. |
|
|
|
|
|
Get the What's this text for the action. |
1.2.18