Re: detection if applet is running

2011-10-29 Thread Andriy Rysin
On 10/29/2011 06:38 AM, Aaron J. Seigo wrote: On Saturday, October 29, 2011 12:18:00 Ruurd Pels wrote: On Friday 28 October 2011 12:46:38 Andriy Rysin wrote: Yes, but I can get the keyboard layouts from x11 directly (that's what applets and systray is doing), that'll be more efficient and would

Re: Qt 4.8 QUrl.toLocalFile behavior change, impacts to KUrl (and friends)

2011-10-29 Thread Milian Wolff
On Saturday 29 October 2011 09:25:03 Thiago Macieira wrote: > On Saturday, 29 de October de 2011 04:38:00 Milian Wolff wrote: > > 1) When does it manifest? Apparently when using QUrl("...") directly, if > > I'm not mistaken. But what if we use KUrl? > > You're correct: this problem manifests when

Review Request: make KFileWidget keep current extension if possible

2011-10-29 Thread Martin Koller
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/102986/ --- Review request for kdelibs. Description --- In trying to fix mentione

Re: detection if applet is running

2011-10-29 Thread Aaron J. Seigo
On Saturday, October 29, 2011 12:18:00 Ruurd Pels wrote: > On Friday 28 October 2011 12:46:38 Andriy Rysin wrote: > > Yes, but I can get the keyboard layouts from x11 directly (that's what > > applets and systray is doing), that'll be more efficient and would not > > require dbus or even kded daemo

Re: detection if applet is running

2011-10-29 Thread Ruurd Pels
On Friday 28 October 2011 12:46:38 Andriy Rysin wrote: > Yes, but I can get the keyboard layouts from x11 directly (that's what > applets and systray is doing), that'll be more efficient and would not > require dbus or even kded daemon running I think it would be preferred to use KDE functionalit

Re: Qt 4.8 QUrl.toLocalFile behavior change, impacts to KUrl (and friends)

2011-10-29 Thread Thiago Macieira
On Saturday, 29 de October de 2011 04:38:00 Milian Wolff wrote: > 1) When does it manifest? Apparently when using QUrl("...") directly, if I'm > not mistaken. But what if we use KUrl? You're correct: this problem manifests when you use QUrl's constructor directly, assuming it will understand a lo