[GRASS5] [bug #2936] (grass) d.barscale doesn't work

>> GRASS 6.0.cvs:~ > d.barscale -m

..

>> unable to open panel No such file or directory

..

> Are you sure that "unable to open panel No such file or directory"
> is exact? I can't find that error message.

Yes, it is an EXACT copy/paste from the terminal output.

The only "unable to open panel" I could find was in
display/drivers/XDRIVER/XDRIVER24/Panel.c, but that is always "unable to open
panel file".
?

> does running:
> g.tempfile pid=$$
> seem to work correctly?

After running g.tempfile pid=$$ I get:
/home/grassdata/caves92/PERMANENT/.tmp/localhost/3219.0
Is that what it should be?

Yes, I wanted to check if your temporary directory was writeable.
Seems to be ok.

Do you see the same problem if you try from a newly created location & mapset?

Hamish

-------------------------------------------- Managed by Request Tracker

From: "Harmish Bowman via RT" <grass-bugs@intevation.de>

>> GRASS 6.0.cvs:~ > d.barscale -m

..

>> unable to open panel No such file or directory

..

> Are you sure that "unable to open panel No such file or directory"
> is exact? I can't find that error message.

Yes, it is an EXACT copy/paste from the terminal output.

The only "unable to open panel" I could find was in
display/drivers/XDRIVER/XDRIVER24/Panel.c, but that is always "unable to open
panel file".
?

Forgive me Hamish, you are right. It should be "unable to open panel file: No such file or directory" like you say.

My finger had to slip when coping/pasting then.

> does running:
> g.tempfile pid=$$
> seem to work correctly?

After running g.tempfile pid=$$ I get:
/home/grassdata/caves92/PERMANENT/.tmp/localhost/3219.0
Is that what it should be?

Yes, I wanted to check if your temporary directory was writeable.
Seems to be ok.

Do you see the same problem if you try from a newly created location & mapset?

Yes - but only if creating a new location from EPSG code! And this way I found the reson that d.barscale doesn't work: the PROJ_INFO file syntax is different when a location is set up via the Grass interface and when automatically generated from EPSG code. See this:

Via Grass set up:

unit: meter
units: meters
meters: 1.0

Automatic, from EPSG 2180:

unit: metre
units: metres
meter: 1

After replacing the automatic one with the Grass one d.barscale works fine.

Could there be any more commands which don't like the EPSG-generated PROJ_INFO files?

Maciek