author | zecke <zecke> | 2004-05-10 21:08:55 (UTC) |
---|---|---|
committer | zecke <zecke> | 2004-05-10 21:08:55 (UTC) |
commit | 613e0a6b246d8dcfd808089b2b6a1dc0501732da (patch) (side-by-side diff) | |
tree | f08854dc0b7121777badeb6cef1007ae8c53a1e1 /libopie2 | |
parent | 0e1086dfe7238cbee8553828afaf32aae4cee70d (diff) | |
download | opie-613e0a6b246d8dcfd808089b2b6a1dc0501732da.zip opie-613e0a6b246d8dcfd808089b2b6a1dc0501732da.tar.gz opie-613e0a6b246d8dcfd808089b2b6a1dc0501732da.tar.bz2 |
Some virtuals which we discussed some time back...
-rw-r--r-- | libopie2/opiecore/okeyconfigmanager.h | 19 |
1 files changed, 11 insertions, 8 deletions
diff --git a/libopie2/opiecore/okeyconfigmanager.h b/libopie2/opiecore/okeyconfigmanager.h index b861675..d0a6247 100644 --- a/libopie2/opiecore/okeyconfigmanager.h +++ b/libopie2/opiecore/okeyconfigmanager.h @@ -127,41 +127,48 @@ private: * This is the Manager for KeyActions. * You can say from which config and group to read data, to grab the * keyboard to handle hardware keys, you can supply a blacklist of * keys which should not be used by allowed to be used. * You can even pass this manager to a Widget to do the configuration for you. * You need to add OKeyConfigItem for your keys and then issue a load() to * read the Key information. * You can either handle the QKeyEvent yourself and ask this class if it is * handled by your action and let give you the action. Or you can install * the event filter and get a signal. * You need to load and save yourself! * + * Again if you want to extend it and I missed a virtual, tell me so I can improve (zecke@handhelds.org) + * * @since 1.1.2 */ class OKeyConfigManager : public QObject { Q_OBJECT typedef QMap<int, OKeyConfigItem::List> OKeyMapConfigPrivate; public: + enum EventMask { + MaskPressed = 0x1, + MaskReleased = 0x2, + }; + OKeyConfigManager(Opie::Core::OConfig *conf = 0, const QString& group = QString::null, const OKeyPair::List &block = OKeyPair::List(), bool grabkeyboard = false, QObject * par = 0, const char* name = 0 ); - ~OKeyConfigManager(); + virtual ~OKeyConfigManager(); - void load(); - void save(); + virtual void load(); + virtual void save(); - OKeyConfigItem handleKeyEvent( QKeyEvent* ); + virtual OKeyConfigItem handleKeyEvent( QKeyEvent* ); int handleKeyEventId( QKeyEvent* ); void addKeyConfig( const OKeyConfigItem& ); void removeKeyConfig( const OKeyConfigItem& ); void clearKeyConfig(); void addToBlackList( const OKeyPair& ); void removeFromBlackList( const OKeyPair& ); void clearBlackList(); OKeyPair::List blackList()const; void handleWidget( QWidget* ); @@ -202,28 +209,24 @@ public: void addEventMask(uint aMask); /** * Clears the event mask flag aMask. * * @param aMask is one of OKeyConfigManager::EventMask * * @see eventMask(), testEventMask(), addEventMask(), setEventMask() */ void clearEventMask(uint aMask); OKeyConfigItem::List keyConfigList()const; - enum EventMask { - MaskPressed = 0x1, - MaskReleased = 0x2, - }; signals: /** * The Signals are triggered on KeyPress and KeyRelease! * You can check the isDown of the QKeyEvent * @see QKeyEvent */ void actionActivated( QWidget*, QKeyEvent*, const Opie::Core::OKeyConfigItem& ); /** * This Signal correspondents to the OKeyConfigItem slot * and object * |