[GRASS-dev] New installation for wxPython GUI

[Moritz Lennert]

Michael Barton wrote:
> Moritz,
> 
> I'll respond to your posts in sequence so it makes a bit more sense.
> 
> See below.
> 
> Michael
> __________________________________________
> Michael Barton, Professor of Anthropology
> School of Human Evolution & Social Change
> Center for Social Dynamics and Complexity
> Arizona State University
> 
> phone: 480-965-6213
> fax: 480-965-7671
> www: http://www.public.asu.edu/~cmbarton
> 
> 
>> From: Moritz Lennert <mlennert at club.worldonline.be>
>> Date: Wed, 09 Aug 2006 11:28:01 +0200
>> To: Michael Barton <michael.barton at asu.edu>
>> Cc: Yann Chemin <ychemin at gmail.com>, Trevor Wiens <twiens at interbaun.com>,
>> David Finlayson <david.p.finlayson at gmail.com>, Jachym Cepicky
>> <jachym.cepicky at centrum.cz>, Grass Developers List <grass-dev at grass.itc.it>
>> Subject: Re: [GRASS-dev] New installation for wxPython GUI
>>
>> Michael,
>>
>> Michael Barton wrote:
>>> I figured out how to run gism.py from outside the directory where it lives.
>>> So now we can run it from a script on the GRASS command line without
>>> changing directories.
>> great !
>>
>> A few issues (using python 2.4.3 and wxpython 2.6.3.3 - installed on
>> Debian from rpms using alien - so there might be some problems with that
>> - I'll compile from source when I find the time):
> 
> Let me know what happens. One of my grad students compiled from source
> yesterday. He still has some issues but not all that you have below.
> 
>> - the display does not automatically redraw when I drag another window
>> over it. I have to click the display map button.
> 
> I have absolutely no problem along these lines. There might be a way to
> force this, but it sounds like either a problematic version of a bug in the
> Debian compile.

Ok, I guess I have to recompile wxpython (and maybe wx ?) from scratch 
to be sure.
Is Debian the only distribution which isn't up to date ? If not then we 
should think about this since asking users to recompile wxpython might 
not be a good way to get them to use the GUI...

>> - I still have the panning problem. What it seems to be is that the
>> program does not release the mouse, so even if the mouse is outside the
>> window it still continues to pan. The only solution still is to switch
>> to another workspace and back. Then the map is gone, but the mouse is
>> usable again.
> 
> My student had the same problem. I think I've fixed it. Try the newest
> version of mapdisp.py on my website.

Now panning works as expected (even though ...), but it still does not 
release the mouse. When I click outside of the map display window and 
drag it is as if the cursor were still on top the map display and the 
map gets panned... As before I have to switch workspaces to get access 
to the mouse again.

> 
>> - When I launch a command I get the correct command window, but any
>> subsequent command launched will give me the same window (i.e.
>> containing the options of the first command launched) except for the
>> title which correctly indicates the name of the command launched. Seems
>> like there needs to be some reinitialisation done.
> 
> This doesn't happen to me at all. I have no idea...


Maybe a version or compilation problem... ?

 >>> - the display does not automatically redraw when I drag another window
 >>> over it. I have to click the display map button.
 >> Adding a simple self.ReDraw(event=None) at the end of def onFocus(self,
 >> event) in mapdisp.py at least displays the map automatically when I
 >> refocus on the map display.
 >>
 >
 > This may be fixed.

no

 > But if not don't use ReDraw. This causes GRASS to
 > completely re-render the map. Try one of the following:
 >
 > add a...
 > self.mapPanel.Refresh()
 > ...instead of a ReDraw call to onFocus
 >
 > If this doesn't work,  add...
 > img = self.getImg()
 > self.draw(img)
 > ...This will redraw the existing image without causing GRASS to re-render
 > it.

The second one works.

Moritz