Opened 11 years ago
Closed 11 years ago
#2068 closed defect (worksforme)
Saving the display as an image in wxGUI fails
Reported by: | laurimyllyvirta | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 6.4.4 |
Component: | wxGUI | Version: | 6.4.2 |
Keywords: | display | Cc: | |
CPU: | x86-32 | Platform: | MSWindows 7 |
Description (last modified by )
Thank you so much for an amazing piece of free software.
When trying to save the display as an image in wxGUI, I get the error below. No image file gets created. I have tried to vary the contents of the display, the dimensions of the image etc. but the result is consistently the same.
Traceback (most recent call last): File "C:\Program Files\GRASS 6.4.2\etc\wxpython\gui_modules\mapdisp.py", line 1159, in SaveToFile width, height) File "C:\Program Files\GRASS 6.4.2\etc\wxpython\gui_modules\mapdisp_window.py", line 575, in SaveToFile dc = wx.BufferedPaintDC(self, ibuffer) File "C:\Program Files\GRASS 6.4.2\Python27\lib\site- packages\wx-2.8-msw-unicode\wx\_gdi.py", line 4990, in __init__ _gdi_.BufferedPaintDC_swiginit(self,_gdi_.new_BufferedPaintD C(*args, **kwargs)) wx._core . PyAssertionError : C++ assertion "wxAssertFailure" failed at ..\..\src\msw\dcclient.cpp(219) in wxPaintDC::wxPaintDC(): wxPaintDC may be created only in EVT_PAINT handler!
Attachments (1)
Change History (5)
by , 11 years ago
Attachment: | Clipboard-1.png added |
---|
comment:1 by , 11 years ago
Component: | Default → wxGUI |
---|---|
Keywords: | display added |
Summary: | d.out.file fails → Saving the display as an image in wxGUI fails |
comment:2 by , 11 years ago
Description: | modified (diff) |
---|
comment:3 by , 11 years ago
Hi,
as a work-around, you might try the built-in Windows 7 screenshot tool,
http://windows.microsoft.com/en-US/windows7/products/features/snipping-tool
Hamish
comment:4 by , 11 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Sorry for missing the new stable release! I can confirm that updating to 6.4.3 fixed this issue for me. And thank you for the lightning speed responses.
If I remember, this was fixed at some point. Can you please try to update to GRASS 6.4.3 and test there? (6.4.3 is the current stable release, if you want to test this bug also for development/svn versions such as GRASS 7 you are welcome, but the update to 6.4.3 may solve your problem.)