Hi list,
I have this weird problem that testing my application sometimes I open up a
frame, and it doesn't appear in front, but in the back of an application. So
it is not visible because it is behind the main screen from where I have
opened it.
Has anyone had this problem also?
It occurs with wxPython 2.4.2.4 Python 2.3 on a Slackware 10 distribution.
Cheers,
Dick
Dick Kniep wrote:
Hi list,
I have this weird problem that testing my application sometimes I open up a frame, and it doesn't appear in front, but in the back of an application. So it is not visible because it is behind the main screen from where I have opened it.
Has anyone had this problem also?
I havn't seen it.
It occurs with wxPython 2.4.2.4 Python 2.3 on a Slackware 10 distribution.
It may depend on the Window Manager you are running since it is responsible for the placement and stacking of top-level windows.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
Robin Dunn <robin@alldunn.com> writes:
Dick Kniep wrote:
Hi list,
I have this weird problem that testing my application sometimes I
open up a frame, and it doesn't appear in front, but in the back of
an application. So it is not visible because it is behind the main
screen from where I have opened it.
Has anyone had this problem also?I havn't seen it.
It occurs with wxPython 2.4.2.4 Python 2.3 on a Slackware 10
distribution.It may depend on the Window Manager you are running since it is
responsible for the placement and stacking of top-level windows.
I've seen it happening on Windows 98.
I don't know exactly what makes it do that, but sometimes the window
comes in the front and other times it comes in the back. Maybe I am
pressing and holding the button a little more or generating some other
event that makes the focus comes to the old window...
It happened a few times (lets say something like 0.5% of the times) and
specially with an overloaded machine.
--
Godoy. <godoy@ieee.org>
Weird thing is, it happens consistently with pgadmin3, which is wxWindows (and
maybe wxPython) based on a Suse 9.1 machine, where the dialog to create a
column ALWAYS appears in the back of the window where the table is
maintained.
Cheers,
D. Kniep
On Thursday 30 September 2004 04:13, Jorge Godoy wrote:
Robin Dunn <robin@alldunn.com> writes:
> Dick Kniep wrote:
>> Hi list,
>> I have this weird problem that testing my application sometimes I
>> open up a frame, and it doesn't appear in front, but in the back of
>> an application. So it is not visible because it is behind the main
>> screen from where I have opened it.
>> Has anyone had this problem also?
>
> I havn't seen it.
>
>> It occurs with wxPython 2.4.2.4 Python 2.3 on a Slackware 10
>> distribution.
>
> It may depend on the Window Manager you are running since it is
> responsible for the placement and stacking of top-level windows.I've seen it happening on Windows 98.
Dick Kniep <dick.kniep@lindix.nl> writes:
Weird thing is, it happens consistently with pgadmin3, which is
wxWindows (and maybe wxPython) based on a Suse 9.1 machine, where the
dialog to create a column ALWAYS appears in the back of the window
where the table is maintained.
Hmmm... Both "wxDialog"s and "wxFrame"s have an option
"wxSTAY_ON_TOP". Dialogs still have an option to be Modal or not.
These can interfere with the behaviour.
Also you didn't say -- I didn't saw you saying, to be more honest --
what window manager you're using. It can be the guilty for that...
Be seeing you,
--
Godoy. <godoy@ieee.org>
Hi list,
Dick Kniep <dick.kniep@lindix.nl> writes:
> Weird thing is, it happens consistently with pgadmin3, which is
> wxWindows (and maybe wxPython) based on a Suse 9.1 machine, where the
> dialog to create a column ALWAYS appears in the back of the window
> where the table is maintained.Hmmm... Both "wxDialog"s and "wxFrame"s have an option
"wxSTAY_ON_TOP". Dialogs still have an option to be Modal or not.
Possibly, I installed standard from rpm, so there is no fiddling from my side
in the code. Could be a pgadmin error then?
These can interfere with the behaviour.
Also you didn't say -- I didn't saw you saying, to be more honest --
what window manager you're using. It can be the guilty for that...
Kde 3.2.2
Cheers
On Thursday 30 September 2004 18:54, Jorge Godoy wrote:
AHA!
I just noticed that it happens when the following sequence of events occurs:
1. Main screen is opened
2. secondary screen is opened (on top of the main screen) correct!
3. Click in the main screen (so secondary screen disappears) correct!
4. Open ANOTHER tertiary screen, which should again appear on top of the
mainscreen. It doesn't but appears in the back!
This is MY application and I definitely did NOT specify "stay on top" (which
is also proven by the fact that the secondary screen appears nicely on top.
Hope this clarifies it.
Cheers,
Dick
Dick Kniep wrote:
AHA!
I just noticed that it happens when the following sequence of events occurs:
1. Main screen is opened
2. secondary screen is opened (on top of the main screen) correct!
3. Click in the main screen (so secondary screen disappears) correct!
4. Open ANOTHER tertiary screen, which should again appear on top of the mainscreen. It doesn't but appears in the back!This is MY application and I definitely did NOT specify "stay on top" (which is also proven by the fact that the secondary screen appears nicely on top.
I assume by "new screen" you mean a wx.Frame, right? Are the second and thrid frames children of the first one?
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
Dick Kniep wrote:
> AHA!
>
> I just noticed that it happens when the following sequence of events
> occurs:
>
> 1. Main screen is opened
> 2. secondary screen is opened (on top of the main screen) correct!
> 3. Click in the main screen (so secondary screen disappears) correct!
> 4. Open ANOTHER tertiary screen, which should again appear on top of the
> mainscreen. It doesn't but appears in the back!
>
> This is MY application and I definitely did NOT specify "stay on top"
> (which is also proven by the fact that the secondary screen appears
> nicely on top.I assume by "new screen" you mean a wx.Frame, right? Are the second and
thrid frames children of the first one?
The third screen is a child of the main screen. So structure is:
--------- ------------
Main>---------+---------| Child 1 |
--------- | ------------
>
> -----------
+----------| Child 2 |
On Wednesday 06 October 2004 01:18, Robin Dunn wrote:
-----------
So start main screen OK
Start Child 1 on top of main screen OK
Click in Main outside Child 1, Child 1 disappears OK
Start Child 2 on top of main screen NOT OK, appears in the back of the
mainscreen
Cheers,
Dick