[GRASSLIST:7125] mac os x binaries and i.points

Hi list,

everytime I try to run i.points, it runs fines up to the point that it asks for keyboard input. Then in the i.points window the text is garbage, so I cant read the instructions.

The same goes even if I have X11 as my graphic enviroment. I tried to bypass the problem by starting in text mode, but it stills open a window for i.points (I mean the command window, and not the map window).

Is this a known issue?

My system is Mac OS X 10.4

Thanks

Kostas Theofilis

everytime I try to run i.points, it runs fines up to the point that
it asks for keyboard input. Then in the i.points window the text is
garbage, so I cant read the instructions.

The same goes even if I have X11 as my graphic enviroment. I tried to
bypass the problem by starting in text mode, but it stills open a
window for i.points (I mean the command window, and not the map
window).

Is this a known issue?

You are using the 6.1-cvs development version, correct? I broke this a
while back and have been meaning to fix/revert the change. It's fine in
the 6.0.x line.

Solution: don't use the GUI.
To start, from the shell prompt run "i.points groupname".

Issue: I changed the module to use G_parser() & make it into a normal
GRASS module.

Temporary fix (not done yet): revert G_parser() code, add parser like
code to read arguements from the command line if given.

Outstanding issue: How to deal with interactive modules which require
keyboard input. Spawning xterms from the GUI is not a good long term
solution.

Hamish

On Mon, 13 Jun 2005, Hamish wrote:

Outstanding issue: How to deal with interactive modules which require
keyboard input. Spawning xterms from the GUI is not a good long term
solution.

A new libary, something similar to Vask would be a good idea. Modules requiring interactive I/O could call it at a level abstracted from whether the user was running GRASS in command-line or GUI mode---this new library
would use whatever method was appropriate to present output to and get input
from the user.

(When I first heard of / saw the Form library I thought perhaps this is what it does, but I was mistaken.)

Paul