Opened 13 years ago
Closed 13 years ago
#1473 closed defect (worksforme)
wxgui fails to set computational region from display extent
Reported by: | marisn | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | wxGUI | Version: | svn-trunk |
Keywords: | Cc: | ||
CPU: | Unspecified | Platform: | Unspecified |
Change History (3)
by , 13 years ago
Attachment: | set_comp_ext.png added |
---|
comment:1 by , 13 years ago
I've had just a quick look at it and the problem could be in render.AlignResolution
, but I'm not sure what it is exactly doing, see the doc string:
"""!Sets display extents to even multiple of current resolution defined in WIND file from SW corner. This must be done manually as using the -a flag can produce incorrect extents. """
The differences in your screenshot are really big, I can see only small differences when I try to reproduce the problem myself. Maybe it could be related to projection?
Anna
comment:2 by , 13 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Either it has been fixed by accident or it depends on some other settings. Can not reproduce it anymore with r49125
Note:
See TracTickets
for help on using tickets.
Compare numbers at output pane and map display after using "set computational region from display extent" function