> On Nov. 7, 2013, 12:19 a.m., Teemu Rytilahti wrote:
> > I'm not actually sure whether is okay to force focus after any key is being
> > released...
>
> Christoph Feck wrote:
> Bug 319935 is probably the same issue, and also contains a patch at
> comment #1 for the "onReleased" function,
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/113697/
---
(Updated Nov. 7, 2013, 12:27 a.m.)
Review request for Plasma.
Bugs: 3147
> On Nov. 7, 2013, 12:19 a.m., Teemu Rytilahti wrote:
> > I'm not actually sure whether is okay to force focus after any key is being
> > released...
Bug 319935 is probably the same issue, and also contains a patch at comment #1
for the "onReleased" function, so it seems there is no other way
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/113697/#review43193
---
I'm not actually sure whether is okay to force focus after any
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/113697/
---
Review request for Plasma.
Bugs: 314720, 316084 and 324821
http://bugs
On Wednesday 06 November 2013 09:34:23 Martin Klapetek wrote:
> On Wed, Nov 6, 2013 at 7:00 AM, Martin Gräßlin wrote:
> > And what about the event filter on the root window to ensure that the
> > splash
> >
> > screen stays on top of the stack? Maybe that was missing in KSplashQML,
> >
> > but
On Wed, Nov 6, 2013 at 7:00 AM, Martin Gräßlin wrote:
> And what about the event filter on the root window to ensure that the
> splash
> screen stays on top of the stack? Maybe that was missing in KSplashQML,
> but
> KSplashX clearly has that.
>
There's
setFlags(
Qt::FramelessWindo
