Re: FVWM: Placement of QT5 app

2017-09-29 Thread Tom Horsley
On Fri, 29 Sep 2017 01:30:08 +0100 Dominik Vogt wrote: > On Thu, Sep 28, 2017 at 07:18:08PM -0400, Tom Horsley wrote: > > I see calibre windows gradually drift up and left > > every time I start calibre because the code is > > trying to save its geometry and getting it wrong. > > Try either >

Re: FVWM: Placement of QT5 app

2017-09-29 Thread Dominik Vogt
On Fri, Sep 29, 2017 at 08:38:01AM -0400, Tom Horsley wrote: > On Fri, 29 Sep 2017 01:30:08 +0100 > Dominik Vogt wrote: > > On Thu, Sep 28, 2017 at 07:18:08PM -0400, Tom Horsley wrote: > > > I see calibre windows gradually drift up and left > > > every time I start calibre because the code is > > >

Re: FVWM: Placement of QT5 app

2017-09-29 Thread Tom Horsley
On Fri, 29 Sep 2017 14:00:10 +0100 Dominik Vogt wrote: > These two styles are meant exactly for this situation. One of > them should work unless the program guesses the border width and > title height wrong. Is it 10x1 pixels? I'm fairly certain the program doesn't make the slightest attempt to

Re: FVWM: Placement of QT5 app

2017-09-29 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am Fr den 29. Sep 2017 um 14:00 schrieb Dominik Vogt: > > > Try either > > > > > > Style ... UseGravity > > > > > > or > > > > > > Style ... IgnoreGravity > > > > > > where "..." is a style name matching the offending window only. That

Re: FVWM: Placement of QT5 app

2017-09-29 Thread Dominik Vogt
On Fri, Sep 29, 2017 at 09:39:05AM -0400, Tom Horsley wrote: > On Fri, 29 Sep 2017 14:00:10 +0100 > Dominik Vogt wrote: > > > These two styles are meant exactly for this situation. One of > > them should work unless the program guesses the border width and > > title height wrong. Is it 10x1 pixe

Re: FVWM: Placement of QT5 app

2017-09-29 Thread Tom Horsley
On Fri, 29 Sep 2017 14:57:42 +0100 Dominik Vogt wrote: > And you have really tried out both styles (separately) and made > sure that they are applied to the window, and both do not work? Well I had a long time ago, but I just tried to test this again and it looks like calibre may have been fixed