Re: General window manager question

2013-12-04 Thread Kevin Krammer
On Wednesday, 2013-12-04, 18:33:51, Damian Ivanov wrote: > Hi all, > > By default no application can cover the plasma panel, on resizing or > on maximizing the applications resize so that they do not cover the > panel. > Where is this set? It is not a Qt Window flag. It must be set by the > window

Re: General window manager question

2013-12-04 Thread Damian Ivanov
Thanks :) 2013/12/4 Thomas Lübking : > On Mittwoch, 4. Dezember 2013 17:33:51 CEST, Damian Ivanov wrote: >> >> Hi all, >> >> By default no application can cover the plasma panel, on resizing or >> on maximizing the applications resize so that they do not cover the >> panel. >> Where is this set? >

Re: General window manager question

2013-12-04 Thread Thomas Lübking
On Mittwoch, 4. Dezember 2013 17:33:51 CEST, Damian Ivanov wrote: Hi all, By default no application can cover the plasma panel, on resizing or on maximizing the applications resize so that they do not cover the panel. Where is this set? KWindowSystem::set*Strut(.) functions, see http://api.kde

General window manager question

2013-12-04 Thread Damian Ivanov
Hi all, By default no application can cover the plasma panel, on resizing or on maximizing the applications resize so that they do not cover the panel. Where is this set? It is not a Qt Window flag. It must be set by the window manager, but how comes that this works with any started panel program

Re: Problem with KCompTreeNode on Windows (or: destruction order of static objects?)

2013-12-04 Thread Milian Wolff
On Wednesday 04 December 2013 16:01:03 Frank Reininghaus wrote: > Hi, > > 2013/11/30 Kevin Funk: > > Hey guys, > > > > My recent attempts to make KDevelop shine on Windows revealed some odd > > behaviour inside kdelibs. > > > > I need some help in order to find the right approach to fix an at le

Re: Problem with KCompTreeNode on Windows (or: destruction order of static objects?)

2013-12-04 Thread Frank Reininghaus
Hi, 2013/11/30 Kevin Funk: > Hey guys, > > My recent attempts to make KDevelop shine on Windows revealed some odd > behaviour inside kdelibs. > > I need some help in order to find the right approach to fix an at least 3 year > old bug [1] ultimately caused by the use of a static member object in t

Re: X-KDE-PluginInfo-EnabledByDefault doesn't work?

2013-12-04 Thread Sebastian Kügler
On Tuesday, December 03, 2013 17:43:26 Kai Uwe Broulik wrote: > Problem with all of this is that most distributions provide their own > default layout which hardly gets updated and so new stuff like print > manager, apper, screen, ktp, etc are often not on by default. Especially > new apper has no