NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Greetings - am attempting unsuccessfully to launch NMAP2 with different pixel dimensions than its default using window manager (example: nmap2 -- -geometry 1600x1200+0+0) and get Seg fault/core dumped. I can locate the nmap2 window using this method say 100 pixels over and down (example: nmap2 -- -geometry +100+100), but no luck with resizing. After numerous greps through the $GEMTBL dir and searching on GEMBUD and google to see if this is configurable (and many trial/error iterations) still no luck. Anyone know if there is a table that dictates the default size (dimensions) nmap2 opens or a way to modify its size without manually doing so with the mouse? For what its worth, a screen capture of the nmap2 window reveals it opens at a default dimension of 1166x1012 pixels. And btw get a core dump when I do a nmap2 -- -geometry 1166x1012 Pete ------------------------------------------------------------------------------ The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
gembud
archives: