On Fri, May 27, 2011 at 2:09 PM, Brian Helm <bthe...@gmail.com> wrote: > Hmm... so how does "BorderlessMaximizedWindows=true" in kwinrc get acted on? Internally - the key is read and applied on maximization. Sorry, actually nobody took care of your question after martins post and apparently claws doesn't like gmail smtp too much....
Your code does not work for fundamentally false implementation, because this QWidget *activeWidget = QWidget::find(m_activeWindow); looks for a WinID in a (usually) different process. You'll have top operate on the X11 window, ie. only KWindowSystem::activeWindow() (all other code there to determine the correct window is superflous) and then have to use the KWindowSystem routines as well to alter it's state (activation etc.) YOU CAN NOT MAKE USE OF QWIDGET FOR GENERAL WINDOWS THAT DON'T BELONG TO YOUR APPLICATION! "Unfortunately there's no KWindowSystem function to set motif hints, because the support actually more or less *was* legacy from the beginning on (and inofficial - the Motif hints have always been "proprietary" a MWM feature) and for that reason there will probably not be one ever, so you'll have to use XChangeProperty directly (and trust me: on the motif hints that's no fun even if you know to safely operate on XChangeProperty, be careful to not break things...) :-( I guess you want to do some Unity clone: simply read/set/reset the kwin config key from your plasmoid and trigger a kwin config reload via dbus then. You should also document (tell your users) that you do so in case anything goes wrong ;-) May the force be with you, Thomas >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
