The export to high-resolution PPM in nviz is broken. Exported images
either alternate between good and garbage pieces, or it gets to a point
and the rest of the image is garbage. I currently have no repository to
post data and images, but I can email to anyone who wants to take a
look.
I also noticed my PBUFFERS and PIXBUF changes were backed out again.
The way it is configured now will have the least amount of success for
the majority of users. Video acceleration should be an option, not the
rule. What GRASS_NO_GLX_PBUFFERS and GRASS_NO_GLX_PIXMAP environment
vars do should be default behavior. If there is a better argument for
the current code, I'd like to know.
--
Brad Douglas <rez touchofmadness com> KB8UYR/6
Address: 37.493,-121.924 / WGS84 National Map Corps #TNMC-3785
The export to high-resolution PPM in nviz is broken.
AFAICT, it has *always* been broken, in the sense that getting it to
work has always involved an element of luck.
Exported images
either alternate between good and garbage pieces, or it gets to a point
and the rest of the image is garbage. I currently have no repository to
post data and images, but I can email to anyone who wants to take a
look.
I also noticed my PBUFFERS and PIXBUF changes were backed out again.
The way it is configured now will have the least amount of success for
the majority of users.
OTOH, the current setup results in the code getting a lot more testing
than would be the case if users had to enable pBuffers/Pixmaps
manually. As the behaviour is likely to vary significantly between
systems, depending upon the graphics hardware, drivers, and X version,
this isn't something that can be solved "in house"; we *need* user
feedback on this.
Video acceleration should be an option, not the rule.
Use of pBuffers/Pixmaps isn't about "acceleration", it's about
"off-screen" rendering. The image is rendered for the purpose of being
saved to a file, rather than displayed to the user.
The option to render directly to the window is intended as a fall-back
for OpenGL implementations which don't provide any other rendering
targets, and has enough problems of its own. If pBuffers/Pixmaps work
on a given system, they should be more reliable than rendering to the
window.
The export to high-resolution PPM in nviz is broken. Exported images
either alternate between good and garbage pieces, or it gets to a
point and the rest of the image is garbage.
I currently have no repository to post data and images, but I can
email to anyone who wants to take a look.
The new gforge bug tracker will take image uploads.
flickr.com is another place to post them.
With the current grass 6.3-cvs I get this error when I try the menu item:
Error: no files matched glob pattern "*"
no files matched glob pattern "*"
no files matched glob pattern "*"
while executing
"glob -directory $cur_dir *"
(procedure "refresh_file_browser" line 10)
invoked from within
"refresh_file_browser $w"
(procedure "create_file_browser" line 91)
invoked from within
"create_file_browser .file_browser 1"
invoked from within
".top.menu.file.m.img invoke active"
("uplevel" body line 1)
invoked from within
"uplevel #0 [list $w invoke active]"
(procedure "tkMenuInvoke" line 47)
invoked from within
"tkMenuInvoke .top.menu.file.m.img 1
"
(command bound to event)
after clicking [Ok] I get a file browser, but it doesn't build and image.
For me it works fine with GRASS 6.2.1 on my Debian/Sarge & 32bit Pentium4.