From 9c9412b30c54468adc9e506cc76c5d113fbf5056 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Fri, 1 Feb 2013 15:14:03 -0600 Subject: Rename a number of classes to enhance compatibility with KDE4 --- kopete/plugins/nowlistening/DESIGN | 2 +- kopete/plugins/nowlistening/nowlisteningguiclient.cpp | 2 +- kopete/plugins/nowlistening/nowlisteningguiclient.h | 4 ++-- kopete/plugins/nowlistening/nowlisteningprefs.ui | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) (limited to 'kopete/plugins/nowlistening') diff --git a/kopete/plugins/nowlistening/DESIGN b/kopete/plugins/nowlistening/DESIGN index d2be5d5f..1cfb105b 100644 --- a/kopete/plugins/nowlistening/DESIGN +++ b/kopete/plugins/nowlistening/DESIGN @@ -36,7 +36,7 @@ How contact specific plugin data works Each metacontact has a method pluginData(KopetePlugin *). This takes a pointer to a plugin, and returns a QStringList containing the metacontact's data for that plugin. A corresponding setPluginData() method changes this. Who is responsible for making sure this data persists? What about custom actions? -KopetePlugin::custom[Chat|ContextMenuActions] both return a set of KActions that the plugin wants to have added to the UI. Looking at contactnotes, it seems that this set is recreated every time thses methods are called and they change the state of the plugin (currentContact). Is this so that the context menu is generated individually for each MC, so that the method that is called when the men item is clicked know which MC it applies to? +KopetePlugin::custom[Chat|ContextMenuActions] both return a set of TDEActions that the plugin wants to have added to the UI. Looking at contactnotes, it seems that this set is recreated every time thses methods are called and they change the state of the plugin (currentContact). Is this so that the context menu is generated individually for each MC, so that the method that is called when the men item is clicked know which MC it applies to? Choosing whether to advertise to all contacts We can either advertise periodically to (some) contacts, or we could just add an Action to advertise what we're currently listening to. diff --git a/kopete/plugins/nowlistening/nowlisteningguiclient.cpp b/kopete/plugins/nowlistening/nowlisteningguiclient.cpp index c5e47ef0..29f03175 100644 --- a/kopete/plugins/nowlistening/nowlisteningguiclient.cpp +++ b/kopete/plugins/nowlistening/nowlisteningguiclient.cpp @@ -34,7 +34,7 @@ NowListeningGUIClient::NowListeningGUIClient( Kopete::ChatSession *parent, NowLi { connect(plugin, TQT_SIGNAL(readyForUnload()), TQT_SLOT(slotPluginUnloaded())); m_msgManager = parent; - m_action = new KAction( i18n( "Send Media Info" ), 0, this, + m_action = new TDEAction( i18n( "Send Media Info" ), 0, this, TQT_SLOT( slotAdvertToCurrentChat() ), actionCollection(), "actionSendAdvert" ); setXMLFile("nowlisteningchatui.rc"); } diff --git a/kopete/plugins/nowlistening/nowlisteningguiclient.h b/kopete/plugins/nowlistening/nowlisteningguiclient.h index f4c4b47f..95642ede 100644 --- a/kopete/plugins/nowlistening/nowlisteningguiclient.h +++ b/kopete/plugins/nowlistening/nowlisteningguiclient.h @@ -24,7 +24,7 @@ #include #include -class KAction; +class TDEAction; class NowListeningPlugin; namespace Kopete { @@ -46,7 +46,7 @@ protected slots: private: Kopete::ChatSession* m_msgManager; - KAction* m_action; + TDEAction* m_action; }; #endif diff --git a/kopete/plugins/nowlistening/nowlisteningprefs.ui b/kopete/plugins/nowlistening/nowlisteningprefs.ui index 125ff80b..ff3307e9 100644 --- a/kopete/plugins/nowlistening/nowlisteningprefs.ui +++ b/kopete/plugins/nowlistening/nowlisteningprefs.ui @@ -295,7 +295,7 @@ in place of your status message. Use &specified media player - + kcfg_SelectedMediaPlayer -- cgit v1.2.1