On 14/11/11 21:53, Glynn Clements wrote:
Sören Gebbert wrote:
The next point is to have a separate vector digitizing process for the
wxGUI digitizer. How should this work? Using RPC to have access to the
vector library in wx C++ code? Implementing special editing modules
... which make vector
Hi,
2011/11/12 Glynn Clements gl...@gclements.plus.com:
Even if the exit()-on-fatal-error issue magically disappeared, the
memory management issues (i.e. don't bother tracking allocations which
don't matter for a typical module) won't. Nor will the fact that
try ... except won't catch a
Hi,
2011/11/12 Wenzeslaus wenzesl...@gmail.com:
I know that this solution doesn't follow the idea of calling modules
(and not using library directly), but now it seems to be much easier
to do this change than rewrite parts of wxGUI which uses ctypes.
I am afraid that rewriting such wxGUI
Hi Martin,
2011/11/17 Martin Landa landa.mar...@gmail.com:
Hi,
2011/11/12 Glynn Clements gl...@gclements.plus.com:
Even if the exit()-on-fatal-error issue magically disappeared, the
memory management issues (i.e. don't bother tracking allocations which
don't matter for a typical module)
Hi,
2011/11/17 Sören Gebbert soerengebb...@googlemail.com:
grass.lib.* exists for module-style scripts, not for persistent
applications.
that's right, but we just shouldn't forbid to use GRASS libraries for
such applications (for which the GRASS libraries were not designed).
This is not
Hi,
2011/11/14 Glynn Clements gl...@gclements.plus.com:
Except .. that's going to need some support, as you can't use setjmp()
directly from Python (the jmp_buf becomes invalid once you return from
the function which called setjmp()). We would need something like:
static jmp_buf jbuf;
Hello,
I compiled an own python script together with
the source of GRASS 6.5SVN on Mac OSX and on Windows.
The script source (with make and description.html) was
place in the same directory of the source etc.
In both cases no errors occured while compiling.
I can easily start my script on my Mac
#1493: wxgui About GRASS fails with UnicodeDecodeError
-+--
Reporter: marisn | Owner: grass-dev@…
Type: defect | Status: new
Priority: minor|
Martin Landa wrote:
I know that this solution doesn't follow the idea of calling modules
(and not using library directly), but now it seems to be much easier
to do this change than rewrite parts of wxGUI which uses ctypes.
I am afraid that rewriting such wxGUI components with the number
Martin Landa wrote:
If a function calls G_fatal_error(), it isn't expecting it to return.
If it does return, the usual result will be that the caller attempts
to use invalid data; a crash isn't likely to be far off.
A typical example of G_fatal_error() usage is:
FILE *fp =
Sören Gebbert wrote:
IMHO the main wxGUI should not make use of library functions which
call G_fata_error() directly, it should use grass modules or start
Python processes which call grass library functions. These processes
can make use of Glynns Python longjmp approach to pass meaningful
Moritz Lennert wrote:
No. Just make the digitiser a separate process which imports
grass.lib.vector etc. If it crashes, you just lose the digitiser
rather than losing the entire GUI.
Jumping in out of no where here, but I would like to understand the
fundamental issue here: would
#1494: wish: v.in.ogr add possibility to use existing attribute column as
category
value, including with -t option
-+--
Reporter: mlennert | Owner: grass-dev@…
Type: enhancement |
Sören wrote:
I think r.univar is a good example. Extended
stats are computed only when specified, because
of its additional computation effort and memory
usage. The output is added automatically to shell
style output in case -g is specified.
I much prefer the present way for v.info (in
Hamish wrote:
simple, clean, consistent, and doesn't stop others
from working the way they want to work.
well, maybe consistent for all sets/perspectives is
the part we're working on right now. :-)
Hamish
___
grass-dev mailing list
IMHO, having the digitizer and 3D in the same display as the 2D display is an
elegant way to view the same spatial data in different ways while saving screen
real estate. Regularly, when I show this, people are impressed about GRASS's
usability from the GUI and command line, and generally want
16 matches
Mail list logo
