I have changed the name of the vector and site pannels in nviz
to better reflect what they are doing, so now we have:
vector lines are viewed through Vector lines pannel
vector points are viewed through Vector points pannel
vector polygons are loaded through Vector lines but nothing gets displayed
(am I missing something?)
there is still a minor problem that if user
tries to display vector point data through vector lines pannel
(e.g. forgets that the file is points only)
nothing gets loaded - there should probably be a message "this is a point file,
use Vector points pannel" but I don't know how to add it
Eventually all vector data viewing could be merged under one pannel but
that is for later releases (unless somebody wants to do it now)
If somebody knows how to remove the mkdspf pannel without breaking anything,
it would be a great help.
And finally - we just got rid of all the messages produced by nviz
(thanks to Bob) to make sure that user does not miss any warnings given at the start
of the program but now
GRASS_INFO_PERCENT: xx writes each new % on new line, so the user sees just endless
lines of this - can the message be written on the same line as before?
This is causing problems in v.surf.rst too.
thanks, and letme know if the change in Pannels does not work,
Helena
On Sun, Dec 12, 2004 at 09:34:59PM -0500, Helena wrote:
...
And finally - we just got rid of all the messages produced by nviz
(thanks to Bob) to make sure that user does not miss any warnings given at
the start
of the program but now
GRASS_INFO_PERCENT: xx writes each new % on new line, so the user sees just
endless
lines of this - can the message be written on the same line as before?
This is causing problems in v.surf.rst too.
I assume that
g.gisenv set=GRASS_MESSAGE_FORMAT=gui
will toggle the message format.
I have recently modified the init script to set GRASS_MESSAGE_FORMAT
according to user selection of working in text or GUI mode.
Not sure if it works correctly (but I think so).
GRASS_MESSAGE_FORMAT is documented at:
g.manual variables &
Hope this helps
Markus
Markus Neteler wrote:
On Sun, Dec 12, 2004 at 09:34:59PM -0500, Helena wrote:
...
And finally - we just got rid of all the messages produced by nviz
(thanks to Bob) to make sure that user does not miss any warnings given at the start
of the program but now
GRASS_INFO_PERCENT: xx writes each new % on new line, so the user sees just endless
lines of this - can the message be written on the same line as before?
This is causing problems in v.surf.rst too.
I assume that
g.gisenv set=GRASS_MESSAGE_FORMAT=gui
will toggle the message format.
I have recently modified the init script to set GRASS_MESSAGE_FORMAT
according to user selection of working in text or GUI mode.
Not sure if it works correctly (but I think so).
GRASS_MESSAGE_FORMAT is documented at:
g.manual variables &
GRASS_MESSAGE_FORMAT should NOT be set in init script, it should only be set if a module is run from GUI, which is capable to handle GUI output format, i.e. currently ONLY the autogenerated GUI.
GRASS_MESSAGE_FORMAT is enviroment variable, not GRASS variable.
Radim
On Mon, Dec 13, 2004 at 11:25:38AM +0100, Radim Blazek wrote:
Markus Neteler wrote:
>On Sun, Dec 12, 2004 at 09:34:59PM -0500, Helena wrote:
>...
>
>>And finally - we just got rid of all the messages produced by nviz
>>(thanks to Bob) to make sure that user does not miss any warnings given
>>at the start
>>of the program but now
>>GRASS_INFO_PERCENT: xx writes each new % on new line, so the user sees
>>just endless
>>lines of this - can the message be written on the same line as before?
>>This is causing problems in v.surf.rst too.
>
>
>I assume that
>
> g.gisenv set=GRASS_MESSAGE_FORMAT=gui
Sorry, that's nonsense.
export GRASS_MESSAGE_FORMAT=gui
would be right.
>
>will toggle the message format.
>I have recently modified the init script to set GRASS_MESSAGE_FORMAT
>according to user selection of working in text or GUI mode.
>Not sure if it works correctly (but I think so).
>
>GRASS_MESSAGE_FORMAT is documented at:
> g.manual variables &
Here it's documented correctly.
In case of errors on that page please correct them.
Also I would like to request developers to add new variables
there.
GRASS_MESSAGE_FORMAT should NOT be set in init script, it should only be
set if a module is run from GUI, which is capable to handle GUI output
format, i.e. currently ONLY the autogenerated GUI.
OK, removed. I had added it to avoid the same problems as of Helena.
How to avoid this output of GRASS_INFO_PERCENT: xx?
GRASS_MESSAGE_FORMAT is enviroment variable, not GRASS variable.
Sure, sorry for the confusion.
Markus
Markus Neteler wrote:
How to avoid this output of GRASS_INFO_PERCENT: xx?
I am not sure where it comes from, is GRASS_INFO_PERCENT se to something? From shell or d.m? If not, it could be bug in G_percent.
Radim
On Mon, Dec 13, 2004 at 12:55:12PM +0100, Radim Blazek wrote:
Markus Neteler wrote:
>How to avoid this output of GRASS_INFO_PERCENT: xx?
I am not sure where it comes from, is GRASS_INFO_PERCENT se to
something? From shell or d.m? If not, it could be bug in G_percent.
It happens in d.m.
Markus
Markus Neteler wrote:
> >How to avoid this output of GRASS_INFO_PERCENT: xx?
>
> I am not sure where it comes from, is GRASS_INFO_PERCENT se to
> something? From shell or d.m? If not, it could be bug in G_percent.
It happens in d.m.
Currently, lib/gis/gui.tcl executes:
set env(GRASS_MESSAGE_FORMAT) gui
at the top level.
It should be set for commands which are run via run_cmd (e.g. via
d.m's execute procedure) and unset for commands which are run through
the spawn, run and term procedures.
--
Glynn Clements <glynn@gclements.plus.com>