Opened 10 years ago

Closed 9 years ago

Last modified 9 years ago

#2680 closed defect (fixed)

d.mon: input file has incorrect dimensions

Reported by: annakrat Owned by: martinl
Priority: normal Milestone: 7.2.0
Component: Display Version: svn-trunk
Keywords: d.mon Cc: grass-dev@…
CPU: Unspecified Platform: Unspecified

Description

I found two related problems with current d.mon.

  1. When I resize the d.mon window, and run a d.* command, I get error:
ERROR: Cairo: input file has incorrect dimensions: expected: 640x480 got:
       861x480
  1. On Windows, this is even more interesting. I open wx0 monitor, run for example d.rast, so far good, but the second d command fails (but the window is still the same as when it opened):
ERROR: Cairo: input file has incorrect dimensions: expected: 640x480 got:
       656x519

These dimensions in the error are the same when running d.mon with or without -x.

Tested on r65288 on Linux and r65276 build on Windows.

Change History (6)

comment:1 by martinl, 10 years ago

Cc: grass-dev@… added
Milestone: 7.0.17.1.0
Owner: changed from grass-dev@… to martinl
Status: newassigned

in reply to:  description ; comment:2 by martinl, 10 years ago

Replying to annakrat:

  1. When I resize the d.mon window, and run a d.* command, I get error:
> ERROR: Cairo: input file has incorrect dimensions: expected: 640x480 got:
>        861x480

this issue should be fixed in r65303.

  1. On Windows, this is even more interesting. I open wx0 monitor, run for example d.rast, so far good, but the second d command fails (but the window is still the same as when it opened):

Let's wait for next build if it helps.

in reply to:  2 comment:3 by martinl, 10 years ago

Replying to martinl:

this issue should be fixed in r65303.

  1. On Windows, this is even more interesting. I open wx0 monitor, run for example d.rast, so far good, but the second d command fails (but the window is still the same as when it opened):

Let's wait for next build if it helps.

It seems to fix both issue.

comment:4 by annakrat, 10 years ago

Thanks for quick response, I am not able to test now, feel free to close it.

comment:5 by martinl, 9 years ago

Resolution: fixed
Status: assignedclosed

I took liberty to close the ticket, feel free to close if needed.

comment:6 by neteler, 9 years ago

Milestone: 7.1.07.2.0

Milestone renamed

Note: See TracTickets for help on using tickets.