Re: [Lazarus] Always on top: Object Inspector and Message Window

2017-02-19 Thread Ondrej Pokorny via Lazarus
On 19.02.2017 18:02, Bart via Lazarus wrote: On 2/19/17, kapibara via Lazarus wrote: I am also using XFCE, but on Debian 9 Please open a bugreport about it. Mention the revision that caused this for you. Don't forget to mention you use XFCE, it may be significant. No need, the issue has bee

Re: [Lazarus] Always on top: Object Inspector and Message Window

2017-02-19 Thread C Western via Lazarus
On 19/02/17 17:02, Bart via Lazarus wrote: On 2/19/17, kapibara via Lazarus wrote: I am also using XFCE, but on Debian 9 Please open a bugreport about it. Mention the revision that caused this for you. Don't forget to mention you use XFCE, it may be significant. Bart I added my comment to

Re: [Lazarus] Always on top: Object Inspector and Message Window

2017-02-19 Thread Bart via Lazarus
On 2/19/17, kapibara via Lazarus wrote: > I am also using XFCE, but on Debian 9 Please open a bugreport about it. Mention the revision that caused this for you. Don't forget to mention you use XFCE, it may be significant. Bart -- ___ Lazarus mailing

Re: [Lazarus] Always on top: Object Inspector and Message Window

2017-02-19 Thread kapibara via Lazarus
I am also using XFCE, but on Debian 9 On 02/19/2017 11:18 AM, C Western via Lazarus wrote: On 18/02/17 02:17, Kapibara Pas via Lazarus wrote: Bart, rev. 53831 introduced the bug. http://bugs.freepascal.org/view.php?id=13051 I uploaded a patch for each affected file and added a note. I can c

Re: [Lazarus] Always on top: Object Inspector and Message Window

2017-02-19 Thread C Western via Lazarus
On 18/02/17 02:17, Kapibara Pas via Lazarus wrote: Bart, rev. 53831 introduced the bug. http://bugs.freepascal.org/view.php?id=13051 I uploaded a patch for each affected file and added a note. I can confirm that I am seeing this bug (messages window always on top), and that the applying gtk2_

Re: [Lazarus] Always on top: Object Inspector and Message Window

2017-02-17 Thread Alexey via Lazarus
Uploaded my tiny fix , there too On 18.02.2017 05:17, Kapibara Pas via Lazarus wrote: I uploaded a patch for each affected file and added a note. -- Regards, Alexey -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org http://lists.lazarus-ide

Re: [Lazarus] Always on top: Object Inspector and Message Window

2017-02-17 Thread Kapibara Pas via Lazarus
Bart, rev. 53831 introduced the bug. http://bugs.freepascal.org/view.php?id=13051 I uploaded a patch for each affected file and added a note. lcl/interfaces/gtk2/gtk2wsforms.pp lcl/interfaces/gtk2/gtk2globals.pp Index: gtk2wsforms.pp ==

Re: [Lazarus] Always on top: Object Inspector and Message Window

2017-02-17 Thread Bart via Lazarus
On 2/17/17, Kapibara Pas via Lazarus wrote: > Could prolly track it down, but already > spent a weeks share of time with the "Iron curtain bug". ;-) Please bisect the guilty revision! Bart -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org htt

Re: [Lazarus] Always on top: Object Inspector and Message Window

2017-02-17 Thread Kapibara Pas via Lazarus
t window and Lazarus has to be restarted. Linux GTK2. kapibara -Original Message- From: Juha Manninen via Lazarus To: Lazarus mailing list Cc: Juha Manninen Sent: Fri, Feb 17, 2017 2:10 pm Subject: Re: [Lazarus] Always on top: Object Inspector and Message Window On Fri, F

Re: [Lazarus] Always on top: Object Inspector and Message Window

2017-02-17 Thread Juha Manninen via Lazarus
On Fri, Feb 17, 2017 at 2:17 PM, Kapibara Pas via Lazarus wrote: > In Lazarus trunk, the message window and object inspector is alwas on top > and hides everything thats behind it. It also hides the code completion > window (ctrl+space) so you cant read some of it. See screenshot. This > happened

[Lazarus] Always on top: Object Inspector and Message Window

2017-02-17 Thread Kapibara Pas via Lazarus
In Lazarus trunk, the message window and object inspector is alwas on top and hides everything thats behind it. It also hides the code completion window (ctrl+space) so you cant read some of it. See screenshot. This happened 1-2 months ago. I was about to report this in the bugtracker when I