Michael Barton wrote:
Currently, due to its history, GRASS has various ways of designating a
range of values.
In raster displays (d.rast) ranges are expressed as 'n-n';
for color tables, they are implied but not explicitly given;
for raster reclass maps (r.reclass), they are expressed as
On Tue, Aug 12, 2008 at 7:34 AM, Glynn Clements
[EMAIL PROTECTED] wrote:
Michael Barton wrote:
Glynn:
Added as r.colors.out.
In trunk? Backported to develbranch_6?
Trunk.
It may need a G_find_cell2() call to work in 6.4. In 7.x, any libgis
functions which deal with existing maps should
Michael Barton wrote:
That's all well and good, but how is the d.* command supposed to get
the data into the wxgui process if not through a file?
p = subprocess.Popen(['d.rast', 'map=myraster'], stdout=subprocess.PIPE)
data = p.stdout
A file will typically be quicker. With a pipe,
On 13/08/08 00:43, Glynn Clements wrote:
Moritz Lennert wrote:
Can you get the GUI to display the exact commands being used, and
check whether the problem exists when the command is run from the
shell?
Nope, everything runs fine from the shell, with e.g. the following command:
d.vect [EMAIL
Michael Barton wrote:
So I updated from trunk and compiled GRASS 7 again. Almost everything
compiled fine. When I went to start it, all went well for the startup
screen, but it crashed on loading the wxPython GUI with the following
error: Fatal Python error: Interpreter not initialized
#253: add a minimum distance threshold to v.distance
--+-
Reporter: mlennert | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: minor|
#256: r.colors enhancement
---+
Reporter: wegmann| Owner: grass-dev@lists.osgeo.org
Type: enhancement| Status: new
Priority: trivial|
#256: r.colors enhancement
--+-
Reporter: wegmann | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: trivial | Milestone: 6.4.0
On 12/08/08 19:14, Moritz Lennert wrote:
On 12/08/08 18:58, Michael Barton wrote:
Moritz,
I just tried out d.thematic.area from develbranch_6 (updated from svn
last night).
I did not commit my last changes to develbranch_6, but to trunk...
Don't have the time right now to find out how to do
Michael Barton pisze:
OK. I see Michael's points. One thing though:
Also, while the GRASS icons may seem large to some,
They are too large. Example: in digitizer half of the tools are not
visible unless you manually extend the window width. This hampers
usability. Is there a way to deal with
Hi,
2008/8/13 Maciej Sieczka [EMAIL PROTECTED]:
They are too large. Example: in digitizer half of the tools are not
visible unless you manually extend the window width. This hampers
usability. Is there a way to deal with that? Like automatically adjust
windows sizes to accomodate all the
Martin Landa pisze:
2008/8/13 Maciej Sieczka [EMAIL PROTECTED]:
They are too large. Example: in digitizer half of the tools are not
visible unless you manually extend the window width. This hampers
usability. Is there a way to deal with that? Like automatically adjust
windows sizes to
Hi,
2008/8/13 Maciej Sieczka [EMAIL PROTECTED]:
indirect way, you can store default windows position in the settings
file (see GUI Preferences dialog, General tab), which can be
override by workspace settings.
I'm not concerned about myself, but about users who will not even know
that some
Hi,
2008/8/13 Martin Landa [EMAIL PROTECTED]:
sure, well, I would still tend to use silk as default icon set. Icons
are not perfect and maybe less intuitive, but still the GUI looks
better.
default windows size is related to silk icon set. Anyway vdigit icons
are too big, maybe we could
Hi,
2008/8/13 Robert Szczepanek [EMAIL PROTECTED]:
[...]
Concerning icon file names.
At the moment there is a mixture:
1. [file-new.gif] - Creates new workspace file
2. [module-d_008.gif] - Add shaded relief map layer
3. [gui-zoom_out.gif] - Zoom out
Question to programmers.
Should I
Martin Landa-2 wrote:
2008/8/13 Martin Landa [EMAIL PROTECTED]:
sure, well, I would still tend to use silk as default icon set. Icons
are not perfect and maybe less intuitive, but still the GUI looks
better.
default windows size is related to silk icon set. Anyway vdigit icons
are
Hi,
2008/8/6 Martin Landa [EMAIL PROTECTED]:
[...]
original GRASS icons - gui/icons/grass ($GISDBASE/gui/icons/grass)
Silk icons - gui/icons/silk ($GISDBASE/gui/icons/silk)
done, in devbr6
http://trac.osgeo.org/grass/changeset/32741
Will be backported to trunk, let me know if you encounter
Hi,
2008/8/13 Robert Szczepanek [EMAIL PROTECTED]:
[...]
How many icons set are now on the table?
6.3 vs. 7
standard vs. wxPython
Or just standard GRASS icons and silk?
Just only original GRASS icons and silk (note that silk icons are used
only in wxPython GUI), see
On Aug 13, 2008, at 5:35 AM, Martin Landa wrote:
Hi,
2008/8/13 Martin Landa [EMAIL PROTECTED]:
sure, well, I would still tend to use silk as default icon set. Icons
are not perfect and maybe less intuitive, but still the GUI looks
better.
default windows size is related to silk icon set.
On Aug 13, 2008, at 12:52 AM, Glynn Clements wrote:
Michael Barton wrote:
So I updated from trunk and compiled GRASS 7 again. Almost everything
compiled fine. When I went to start it, all went well for the startup
screen, but it crashed on loading the wxPython GUI with the following
error:
On Aug 13, 2008, at 12:47 AM, Glynn Clements wrote:
Michael Barton wrote:
That's all well and good, but how is the d.* command supposed to get
the data into the wxgui process if not through a file?
p = subprocess.Popen(['d.rast', 'map=myraster'],
stdout=subprocess.PIPE)
data =
On Aug 13, 2008, at 2:33 AM, Moritz Lennert wrote:
On 12/08/08 19:14, Moritz Lennert wrote:
On 12/08/08 18:58, Michael Barton wrote:
Moritz,
I just tried out d.thematic.area from develbranch_6 (updated from
svn last night).
I did not commit my last changes to develbranch_6, but to
Moritz Lennert wrote:
Can you get the GUI to display the exact commands being used, and
check whether the problem exists when the command is run from the
shell?
Nope, everything runs fine from the shell, with e.g. the following command:
d.vect [EMAIL PROTECTED] color=0:0:0
#256: r.colors enhancement
--+-
Reporter: wegmann | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: trivial | Milestone: 6.4.0
#256: r.colors enhancement
--+-
Reporter: wegmann | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: trivial | Milestone: 6.4.0
2008/8/6 Martin Landa [EMAIL PROTECTED]:
[...]
gintro.gif - gui/images ($GISDBASE/etc/gui/images)
*.ico - gui/icons ($GISDBASE/gui/icons)
done,
http://trac.osgeo.org/grass/changeset/32743
Anyway lib/init need some more cleaning, especially tcl files...
BTW: are we going to drop Tcl/TK GUI
Maciej Sieczka wrote:
OK. I see Michael's points. One thing though:
Also, while the GRASS icons may seem large to some,
They are too large.
That depends upon your monitor resolution. Icons need to have
sufficient pixels and also need to be physically large enough on
screen. On a low
Hi,
2008/8/13 Glynn Clements [EMAIL PROTECTED]:
Example: in digitizer half of the tools are not
visible unless you manually extend the window width.
That's a bug (or maybe a limitation in wxPython, but I don't think
so). A window's minimum size should be sufficient for all of its
subwindows
On Aug 13, 2008, at 9:19 AM, Glynn Clements wrote:
Maciej Sieczka wrote:
OK. I see Michael's points. One thing though:
Also, while the GRASS icons may seem large to some,
They are too large.
That depends upon your monitor resolution. Icons need to have
sufficient pixels and also need
#64: ps.map: patch to set customized scalebar units
--+-
Reporter: alf | Owner: hamish
Type: enhancement | Status: assigned
Priority: minor| Milestone: 6.4.0
Unfortunately I cannot reproduce the compile errors, so I cannot be
of much help.
I added r.viewshed in grass_trunk/raster/. It compiles and works for
me. Looking forward to comments.
-Laura
On Aug 10, 2008, at 3:29 PM, Martin Landa wrote:
Hi,
2008/8/10 Paul Kelly [EMAIL PROTECTED]:
#253: add a minimum distance threshold to v.distance
--+-
Reporter: mlennert | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: closed
Priority: minor|
On Wed, 13 Aug 2008, Laura Toma wrote:
Unfortunately I cannot reproduce the compile errors, so I cannot be of much
help.
I wondered if you might be able to help with advice on the C++ headers.
From the compile errors it seems to me that the problem is a lack of a
definition for the strcpy()
I added r.viewshed in grass_trunk/raster/. It compiles and works
for me. Looking forward to comments.
Should it maybe go in grass-addons rather than trunk for now?
I could not get it to compile in the add-ons (probably i need to set
up some grass parameters, etc).My understanding
Hi all,
I appreciate the time anyone takes to respond to this one. I want to create an
online GIS database from which users can access, download, analyze, and submit
(after review) spatial data. I would like to use GRASS and a Unix based server
for all of this. Ideally, there would just be a
I added r.viewshed to grass-addons, and deleted it from the trunk.
-Laura
On Aug 13, 2008, at 4:47 PM, Paul Kelly wrote:
On Wed, 13 Aug 2008, Laura Toma wrote:
Unfortunately I cannot reproduce the compile errors, so I cannot
be of much help.
I wondered if you might be able to help
Martin Landa-2 wrote:
default windows size is related to silk icon set. Anyway vdigit icons
are too big, maybe we could downsize them to 24px.
Martin
Updated and resized, almost complete set of icons for vdigit is ready in png
format.
http://www.szczepanek.pl/icons.grass/v.0.1/
Michael Barton wrote:
So I updated from trunk and compiled GRASS 7 again. Almost everything
compiled fine. When I went to start it, all went well for the startup
screen, but it crashed on loading the wxPython GUI with the following
error: Fatal Python error: Interpreter not initialized
#256: r.colors enhancement
--+-
Reporter: wegmann | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: trivial | Milestone: 6.4.0
chris carleton wrote:
I appreciate the time anyone takes to respond to this one. I want to
create an online GIS database from which users can access,
download, analyze, and submit (after review) spatial data. I would
like to use GRASS and a Unix based server for all of this. Ideally,
there
Paul Kelly wrote:
Unfortunately I cannot reproduce the compile errors, so I cannot be of much
help.
I wondered if you might be able to help with advice on the C++ headers.
From the compile errors it seems to me that the problem is a lack of a
definition for the strcpy() function in
Michael Barton wrote:
OK. I see Michael's points. One thing though:
Also, while the GRASS icons may seem large to some,
They are too large.
That depends upon your monitor resolution. Icons need to have
sufficient pixels and also need to be physically large enough on
screen. On
42 matches
Mail list logo
