You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
32 lines
1.3 KiB
32 lines
1.3 KiB
//Auto-generated by kalyptus. DO NOT EDIT.
|
|
package org.kde.koala;
|
|
|
|
import org.kde.qt.QMetaObject;
|
|
import org.kde.qt.QtSupport;
|
|
import org.kde.qt.QObject;
|
|
import org.kde.qt.QPopupMenu;
|
|
import org.kde.qt.QIconSet;
|
|
import org.kde.qt.QWidget;
|
|
|
|
public interface KActionSignals {
|
|
/**
|
|
Emitted when this action is activated
|
|
@short Emitted when this action is activated
|
|
*/
|
|
void activated();
|
|
/**
|
|
This signal allows to know the reason why an action was activated:
|
|
whether it was due to a toolbar button, popupmenu, keyboard accel, or programmatically.
|
|
In the first two cases, it also allows to know which mouse button was
|
|
used (Left or Middle), and whether keyboard modifiers were pressed (e.g. CTRL).
|
|
Note that this signal is emitted before the normal activated() signal.
|
|
Yes, BOTH signals are always emitted, so that connecting to activated() still works.
|
|
Applications which care about reason and state can either ignore the activated()
|
|
signal for a given action and react to this one instead, or store the
|
|
reason and state until the activated() signal is emitted.
|
|
@short This signal allows to know the reason why an action was activated: whether it was due to a toolbar button, popupmenu, keyboard accel, or programmatically.
|
|
*/
|
|
void activated(int reason, int state);
|
|
void enabled(boolean arg1);
|
|
}
|