I was running winGRASS 7.0.0
I don’t know what I did but; now when I launch the GUI I get no monitor and a command console message saying:
Invalid map size 142,0
Invalid map size 142,0
I installed winGRASS 7.0.3 and launched the GUI and I get the same message.
I can get a monitor to open using d.mon start=wx0 in a command layer but when I do that the layer manager stops responding. When I close the monitor (with the x) and go back to the command console there is the following message:
Invalid map size 142,0
Invalid map size 142,0
ERROR: Rendering failed. Details: Error reading PPM file
I can ‘work around’ this with the “Start new map display” button and closing display 1 - but this is a bit annoying and will require me to redo all my workspace files.
Marvin Eng
Anna:
Your solution worked fine for the offending workspace file (*.gxw).
It had
display name=“Display 1” . . . . dim=“-32000,-32000,160,39”
I changed that to 300 all round and I am now able to use that gxw with display 1.
However, I seem to have broken something more basic. No matter how I start the GRASS GUI (in demolocation or a newly created location or any of my other locations) I get the same “Invalid map size” message and there is no monitor.
Is there another ‘workspace file’ for the start up of GRASS that I should be looking for to edit?
marvin
···
On Tue, Mar 15, 2016 at 11:12 AM, Anna Petrášová <kratochanna@gmail.com> wrote:
Hi,
On Tue, Mar 15, 2016 at 1:28 PM, Marvin Eng <knot.tyer@gmail.com> wrote:
I was running winGRASS 7.0.0
I don’t know what I did but; now when I launch the GUI I get no monitor and a command console message saying:
Invalid map size 142,0
Invalid map size 142,0
I installed winGRASS 7.0.3 and launched the GUI and I get the same message.
I can get a monitor to open using d.mon start=wx0 in a command layer but when I do that the layer manager stops responding. When I close the monitor (with the x) and go back to the command console there is the following message:
Invalid map size 142,0
Invalid map size 142,0
ERROR: Rendering failed. Details: Error reading PPM file
I can ‘work around’ this with the “Start new map display” button and closing display 1 - but this is a bit annoying and will require me to redo all my workspace files.
I’ve seen this happening before. Open your workspace in a text editor and look what you have in tag display, attribute dim. You might have some exceptionally large values there. This seems to appear only on Windows when you save your workspace while the map window is minimized. You can edit this value and put some normal value in there (like 300), save it and try to reload it again.
Anna
Marvin Eng
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
On Tue, Mar 15, 2016 at 4:05 PM, Marvin Eng <knot.tyer@gmail.com> wrote:
Anna:
Your solution worked fine for the offending workspace file (*.gxw).
It had
display name="Display 1" . . . . dim="-32000,-32000,160,39"
I changed that to 300 all round and I am now able to use that gxw with
display 1.
However, I seem to have broken something more basic. No matter how I start
the GRASS GUI (in demolocation or a newly created location or any of my
other locations) I get the same "Invalid map size" message and there is no
monitor.
Is there another 'workspace file' for the start up of GRASS that I should
be looking for to edit?
I think it might be in your settings. Open the workspace which works for
you now and go to GUI settings, check (or leave checked) Save current
window layout as default in general tab and make sure you don't have any
GRASS window minimized and then Save. Try to launch GRASS and it should
work again. I fixed some of these things quite recently, I would have to
check all the use cases again to see if it persists in the recent version.
Anna
marvin
On Tue, Mar 15, 2016 at 11:12 AM, Anna Petrášová <kratochanna@gmail.com>
wrote:
Hi,
On Tue, Mar 15, 2016 at 1:28 PM, Marvin Eng <knot.tyer@gmail.com> wrote:
I was running winGRASS 7.0.0
I don't know what I did but; now when I launch the GUI I get no monitor
and a command console message saying:
Invalid map size 142,0
Invalid map size 142,0
I installed winGRASS 7.0.3 and launched the GUI and I get the same
message.
I can get a monitor to open using d.mon start=wx0 in a command layer but
when I do that the layer manager stops responding. When I close the monitor
(with the x) and go back to the command console there is the following
message:
Invalid map size 142,0
Invalid map size 142,0
ERROR: Rendering failed. Details: Error reading PPM file
I can 'work around' this with the "Start new map display" button and
closing display 1 - but this is a bit annoying and will require me to redo
all my workspace files.
I've seen this happening before. Open your workspace in a text editor and
look what you have in tag display, attribute dim. You might have some
exceptionally large values there. This seems to appear only on Windows when
you save your workspace while the map window is minimized. You can edit
this value and put some normal value in there (like 300), save it and try
to reload it again.
Anna
Marvin Eng
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
Anna
Thank you again. That worked.
The “Save current window layout as default” box was checked - but I hit the save button at the bottom of the page and now the GUI opens an monitor when it starts up.
p.s. in winGRASS 7.0.3 the “GUI Settings” are accessed through the last selection in the “Settings” menu which is labeled “Preferences” (although the window that this selection opens is called “GUI Settings”
marvin
···
On Tue, Mar 15, 2016 at 1:20 PM, Anna Petrášová <kratochanna@gmail.com> wrote:
On Tue, Mar 15, 2016 at 4:05 PM, Marvin Eng <knot.tyer@gmail.com> wrote:
Anna:
Your solution worked fine for the offending workspace file (*.gxw).
It had
display name=“Display 1” . . . . dim=“-32000,-32000,160,39”
I changed that to 300 all round and I am now able to use that gxw with display 1.
However, I seem to have broken something more basic. No matter how I start the GRASS GUI (in demolocation or a newly created location or any of my other locations) I get the same “Invalid map size” message and there is no monitor.
Is there another ‘workspace file’ for the start up of GRASS that I should be looking for to edit?
I think it might be in your settings. Open the workspace which works for you now and go to GUI settings, check (or leave checked) Save current window layout as default in general tab and make sure you don’t have any GRASS window minimized and then Save. Try to launch GRASS and it should work again. I fixed some of these things quite recently, I would have to check all the use cases again to see if it persists in the recent version.
Anna
marvin
On Tue, Mar 15, 2016 at 11:12 AM, Anna Petrášová <kratochanna@gmail.com> wrote:
Hi,
On Tue, Mar 15, 2016 at 1:28 PM, Marvin Eng <knot.tyer@gmail.com> wrote:
I was running winGRASS 7.0.0
I don’t know what I did but; now when I launch the GUI I get no monitor and a command console message saying:
Invalid map size 142,0
Invalid map size 142,0
I installed winGRASS 7.0.3 and launched the GUI and I get the same message.
I can get a monitor to open using d.mon start=wx0 in a command layer but when I do that the layer manager stops responding. When I close the monitor (with the x) and go back to the command console there is the following message:
Invalid map size 142,0
Invalid map size 142,0
ERROR: Rendering failed. Details: Error reading PPM file
I can ‘work around’ this with the “Start new map display” button and closing display 1 - but this is a bit annoying and will require me to redo all my workspace files.
I’ve seen this happening before. Open your workspace in a text editor and look what you have in tag display, attribute dim. You might have some exceptionally large values there. This seems to appear only on Windows when you save your workspace while the map window is minimized. You can edit this value and put some normal value in there (like 300), save it and try to reload it again.
Anna
Marvin Eng
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
On Tue, Mar 15, 2016 at 9:20 PM, Anna Petrášová <kratochanna@gmail.com> wrote:
On Tue, Mar 15, 2016 at 4:05 PM, Marvin Eng <knot.tyer@gmail.com> wrote:
Anna:
Your solution worked fine for the offending workspace file (*.gxw).
It had
display name="Display 1" . . . . dim="-32000,-32000,160,39"
I changed that to 300 all round and I am now able to use that gxw with
display 1.
However, I seem to have broken something more basic. No matter how I start
the GRASS GUI (in demolocation or a newly created location or any of my
other locations) I get the same "Invalid map size" message and there is no
monitor.
Is there another 'workspace file' for the start up of GRASS that I should
be looking for to edit?
I think it might be in your settings. Open the workspace which works for you
now and go to GUI settings, check (or leave checked) Save current window
layout as default in general tab and make sure you don't have any GRASS
window minimized and then Save. Try to launch GRASS and it should work
again. I fixed some of these things quite recently, I would have to check
all the use cases again to see if it persists in the recent version.
Anna
marvin
On Tue, Mar 15, 2016 at 11:12 AM, Anna Petrášová <kratochanna@gmail.com>
wrote:
Hi,
On Tue, Mar 15, 2016 at 1:28 PM, Marvin Eng <knot.tyer@gmail.com> wrote:
I was running winGRASS 7.0.0
I don't know what I did but; now when I launch the GUI I get no monitor
and a command console message saying:
Invalid map size 142,0
Invalid map size 142,0
I installed winGRASS 7.0.3 and launched the GUI and I get the same
message.
I can get a monitor to open using d.mon start=wx0 in a command layer but
when I do that the layer manager stops responding. When I close the monitor
(with the x) and go back to the command console there is the following
message:
Invalid map size 142,0
Invalid map size 142,0
ERROR: Rendering failed. Details: Error reading PPM file
Most probably it was the zero in the map size: there is nothing to
render if rows and/or columns are zero. If this is true (easy to
test), a more informative message would help.
I can 'work around' this with the "Start new map display" button and
closing display 1 - but this is a bit annoying and will require me to redo
all my workspace files.
I've seen this happening before. Open your workspace in a text editor and
look what you have in tag display, attribute dim. You might have some
exceptionally large values there. This seems to appear only on Windows when
you save your workspace while the map window is minimized. You can edit this
value and put some normal value in there (like 300), save it and try to
reload it again.
Anna
Marvin Eng
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user