RE: [GRASS-dev] winGRASS: 'layer manager' window hidden by 'mapdisplay' windows

Do you know which version of Python and wxPython you are using? It sounds like a wxPython bug. But maybe there is something we can do about it.

Michael
______________________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ 85287-2402
USA

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: http://csdc.asu.edu, http://shesc.asu.edu
    http://www.public.asu.edu/~cmbarton

On Jan 19, 2010, at 1:16 PM, grass-dev-request@lists.osgeo.org wrote:

Message: 2
Date: Tue, 19 Jan 2010 18:44:19 +0100
From: Jan To?ovsk? <j.tosovsky@tiscali.cz>
Subject: RE: [GRASS-dev] winGRASS: 'layer manager' window hidden by
       'mapdisplay' windows
To: <grass-dev@lists.osgeo.org>
Message-ID: <002a01ca992f$09410850$af8d664e@hanz>
Content-Type: text/plain; charset="iso-8859-2"

would it be possible to invert the stacking order of the 'layer
manager' window
and the 'map display' windows? Currently (XP, current

6.4.SVN), when the wxGUI

opens, the layer manager window is in the background.
To get it to the front requires several attempts in the menu bar (or
repositioning
of the 'map display' windows on the screen).

Markus

I've seen this on a couple of students' older laptops and
assumed it was an age/laptop related item. The stacking order
actually is set as you suggested, and on my Mac, the layer
manager always starts on top and in the center; the first map
display is to the upper left and under the layer manager.
There may be a way to force this even more explicitly, but I
don't understand why it is is getting reversed on some XP systems.

I can also confirm it on my Win XP. I've just been considering to report it
:wink:
The most irritating thing is improper activation of the layer manager via
menu bar, if map display is activated. You must click three times on the bar
to get the layer manager active. If Windows task bar is clicked for the
first time, a layer manager can be seen in foreground for a while, but it is
immediately covered with the map. The second click minimizes the layer
manager to the bar and third one restores it. In the latter case the layer
manager finally stays in foreground. If the map is now activated by clicking
on the menu bar, reactivating of layer manager is Ok. But if the map window
is activated clicking into the map or window title bar, events are again
captured somehow (and you need 3 clicks to the menu bar to activate the
layer manager). So I suspect mainly some map window mouse handlers.
I've recorder short video, but it is not very clear:
http://screencast.com/t/NjU1OTQwMD

Jan

On Wed, Jan 20, 2010 at 12:11 AM, Michael Barton <michael.barton@asu.edu> wrote:

Do you know which version of Python and wxPython you are using? It sounds
like a wxPython bug. But maybe there is something we can do about it.

We were using:
Python version 2.5.2
wxPython version 2.8.9.1

(compiled on English XP; installed on Japanese XP)

Markus

I'm meeting with some students to do advanced GRASS tomorrow and will see whether this affects all win boxes or only a few. That is the first thing to identify. You are using very up to date python and wxpython, so I hope that is not the problem.

Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax: 480-965-7671 SHESC), 480-727-0709 (CSDC)
www: www.public.asu.edu/~cmbarton, http://csdc.asu.edu

On Jan 19, 2010, at 7:31 PM, Markus Neteler wrote:

On Wed, Jan 20, 2010 at 12:11 AM, Michael Barton <michael.barton@asu.edu> wrote:

Do you know which version of Python and wxPython you are using? It sounds
like a wxPython bug. But maybe there is something we can do about it.

We were using:
Python version 2.5.2
wxPython version 2.8.9.1

(compiled on English XP; installed on Japanese XP)

Markus

Michael Barton wrote:

Do you know which version of Python and wxPython you are using? It
sounds like a wxPython bug. But maybe there is something we can do about
it.

I don't think that it's a bug as such, just that you don't have
precise guarantees as to the order in which some things happen.

You may be able to solve the issue by adding an idle handler, and
moving the layer manager to the top the first time that it triggers.

Alternatively, wait for the first EVT_PAINT event on the display
window, and move the layer manager to the top at that point. EVT_PAINT
shouldn't occur until the window has been realised.

--
Glynn Clements <glynn@gclements.plus.com>