Martin, et al.
Something has messed the location wizard. Formatting is problematic so that you can't get the pull downs for utm zone. I'm not sure what else is happening, but wanted to get this out there ASAP because of the immanent 6.4 release.
Michael
Michael
On Mon, Mar 9, 2009 at 10:05 PM, Michael Barton <michael.barton@asu.edu> wrote:
Martin, et al.
Something has messed the location wizard. Formatting is problematic so that
you can't get the pull downs for utm zone.
In which subdialog is that precisely? Just for easier testing...
Markus
I'm not sure what else is
happening, but wanted to get this out there ASAP because of the immanent 6.4
release.Michael
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Choosing coordinates. Page after I pick UTM. The pulldown for zone is misformatted and crammed at the top, and inaccessible.
2nd problem. Using EPSG code, after picking the code, there is a popup that asks which projection to use. It is supposed to have the number, followed by a description. Only the number is showing and not the description. So there is no way to tell which number to pick.
3rd problem (not location wizard).
Also, the multifile import dialogs don't work on the Mac. Just discovered that too.
This is because the wx.StaticBox is defined (in __dolayout) AFTER the contents of the static box. wx.StaticBox MUST be defined BEFORE any of its contents, or no controls work inside on the Mac. Because this is currently in a separate method called after everything else in the dialog, it has to be reconfigured. I might be able to work on it tonight.
This probably is affecting the Location Wizard too, but I can't get far enough to find out.
I didn't know that any recent changes had left these inoperable as I have not had to create a location in awhile or had to import a dxf file.
Michael
On Mar 9, 2009, at 2:18 PM, Markus Neteler wrote:
Michael
On Mon, Mar 9, 2009 at 10:05 PM, Michael Barton <michael.barton@asu.edu> wrote:
Martin, et al.
Something has messed the location wizard. Formatting is problematic so that
you can't get the pull downs for utm zone.In which subdialog is that precisely? Just for easier testing...
Markus
I'm not sure what else is
happening, but wanted to get this out there ASAP because of the immanent 6.4
release.Michael
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
grass-dev Info Page
I've got the dxf import (and other multi imports too I hope) fixed and will commit soon. Have to finish importing the dxf files first.
Michael
______________________________
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
Tempe, AZ 85287-2402
USA
voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton
On Mar 9, 2009, at 2:18 PM, Markus Neteler wrote:
Michael
On Mon, Mar 9, 2009 at 10:05 PM, Michael Barton <michael.barton@asu.edu> wrote:
Martin, et al.
Something has messed the location wizard. Formatting is problematic so that
you can't get the pull downs for utm zone.In which subdialog is that precisely? Just for easier testing...
Markus
I'm not sure what else is
happening, but wanted to get this out there ASAP because of the immanent 6.4
release.Michael
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
grass-dev Info Page
This is now fixed so that the controls are functional for Mac in develbranch_6 r36293, and backported to releasebranch and trunk.
Michael
On Mar 9, 2009, at 2:18 PM, Markus Neteler wrote:
Michael
On Mon, Mar 9, 2009 at 10:05 PM, Michael Barton <michael.barton@asu.edu> wrote:
Martin, et al.
Something has messed the location wizard. Formatting is problematic so that
you can't get the pull downs for utm zone.In which subdialog is that precisely? Just for easier testing...
Markus
I'm not sure what else is
happening, but wanted to get this out there ASAP because of the immanent 6.4
release.Michael
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
grass-dev Info Page
Hello all,
related to the location wizard, perhaps what follows does not deal with
any sort of bug but my misuse of the location creation process :
If you need to create from scratch a new gisdabe, located elsewhere than
the current one, the location wizard first writes your new location
directory in the /current/ gisdbase instead of the new one you've just
set. Then when you define a new mapset or want to start from within
PERMANENT, the application fails, with this message :
Starting GRASS ...
Traceback (most recent call last):
File "/usr/local/grass-6.4.0svn/etc/wxpython/gis_set.py", line
401, in OnWizard
self.lblocations.SetSelection(self.listOfLocations.index(gWizard.location))
ValueError: list.index(x): x not in list
Traceback (most recent call last):
File "/usr/local/grass-6.4.0svn/etc/wxpython/gis_set.py", line
686, in OnStart
"set=LOCATION_NAME=%s" %
self.listOfLocations[self.lblocations.GetSelection()]])
IndexError: list index out of range
(tested recently on grass6.4.0 (rev 36255))
Am I doing somenthing wrong ?
Formerly with tcltk it would work (so when in this case, I start from
tcltk...)
Yours,
Vincent.
Le lundi 09 mars 2009 à 14:40 -0700, Michael Barton a écrit :
Choosing coordinates. Page after I pick UTM. The pulldown for zone is
misformatted and crammed at the top, and inaccessible.2nd problem. Using EPSG code, after picking the code, there is a popup
that asks which projection to use. It is supposed to have the number,
followed by a description. Only the number is showing and not the
description. So there is no way to tell which number to pick.3rd problem (not location wizard).
Also, the multifile import dialogs don't work on the Mac. Just
discovered that too.This is because the wx.StaticBox is defined (in __dolayout) AFTER the
contents of the static box. wx.StaticBox MUST be defined BEFORE any of
its contents, or no controls work inside on the Mac. Because this is
currently in a separate method called after everything else in the
dialog, it has to be reconfigured. I might be able to work on it
tonight.This probably is affecting the Location Wizard too, but I can't get
far enough to find out.I didn't know that any recent changes had left these inoperable as I
have not had to create a location in awhile or had to import a dxf file.Michael
On Mar 9, 2009, at 2:18 PM, Markus Neteler wrote:
> Michael
>
> On Mon, Mar 9, 2009 at 10:05 PM, Michael Barton <michael.barton@asu.edu
> > wrote:
>> Martin, et al.
>>
>> Something has messed the location wizard. Formatting is problematic
>> so that
>> you can't get the pull downs for utm zone.
>
> In which subdialog is that precisely? Just for easier testing...
>
> Markus
>
>> I'm not sure what else is
>> happening, but wanted to get this out there ASAP because of the
>> immanent 6.4
>> release.
>>
>> Michael
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-dev
>>_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Hi,
2009/3/10 Vincent Bain <bain@toraval.fr>:
related to the location wizard, perhaps what follows does not deal with
any sort of bug but my misuse of the location creation process :If you need to create from scratch a new gisdabe, located elsewhere than
the current one, the location wizard first writes your new location
directory in the /current/ gisdbase instead of the new one you've just
set. Then when you define a new mapset or want to start from within
PERMANENT, the application fails, with this message :
seems to work for me.
1. Create new directory for gisdbase (e.g. $HOME/grassdata1) - mkdir
2. Choose gisdbase
3. Run location wizard
4. New location created in $HOME/grassdata1
?
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
1. Create new directory for gisdbase (e.g. $HOME/grassdata1) - mkdir
2. Choose gisdbase
3. Run location wizard
4. New location created in $HOME/grassdata1?
Martin,
What do you mean by "2. Choose gisdbase ?" only enter the path to newly
created directory ? it is what I do (see attachment).
On this example, depressing the finish button creates the "Lambert2e"
directory in the previous Gisdbase (/home/vincent/elsewhereonmydisk),
not in /home/vincent/Bureau/test.
Hi,
2009/3/10 Vincent Bain <bain@toraval.fr>:
1. Create new directory for gisdbase (e.g. $HOME/grassdata1) - mkdir
2. Choose gisdbase
3. Run location wizard
4. New location created in $HOME/grassdata1
What do you mean by "2. Choose gisdbase ?" only enter the path to newly
created directory ? it is what I do (see attachment).
type & *ENTER* (just type is not enough)
or
use "Browse" button
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
Hi,
2009/3/10 Vincent Bain <bain@toraval.fr>:
On this example, depressing the finish button creates the "Lambert2e"
directory in the previous Gisdbase (/home/vincent/elsewhereonmydisk),
not in /home/vincent/Bureau/test.
strange, it works for me (i.e. location is created on the right
place). Which version of GRASS?
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
Le mardi 10 mars 2009 à 15:15 +0100, Martin Landa a écrit :
Hi,
2009/3/10 Vincent Bain <bain@toraval.fr>:
>> 1. Create new directory for gisdbase (e.g. $HOME/grassdata1) - mkdir
>> 2. Choose gisdbase
>> 3. Run location wizard
>> 4. New location created in $HOME/grassdata1> What do you mean by "2. Choose gisdbase ?" only enter the path to newly
> created directory ? it is what I do (see attachment).type & *ENTER* (just type is not enough)
or
use "Browse" button
Unfortunately it's all the same...
Again -- to convice myself I don't do things so wrong 
-- it works
through tcltk GUI.
Vincent
Martin