[gembud] Solution - "How to change the default pixel size of an NMAP2 window?"

  • To: "gembud@xxxxxxxxxxxxxxxx" <gembud@xxxxxxxxxxxxxxxx>
  • Subject: [gembud] Solution - "How to change the default pixel size of an NMAP2 window?"
  • From: "Manousos, Peter C" <pmanousos@xxxxxxxxxxxxxxxxxxx>
  • Date: Fri, 2 Aug 2019 14:11:59 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=firstenergycorp.com;dmarc=pass action=none header.from=firstenergycorp.com;dkim=pass header.d=firstenergycorp.com;arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6HVeBpvQXUrE+8WXtmEeNuJ9KuLKYDNd+mF2dSAYnVs=; b=CAV020dY/yvQDfGvLgVM5QTmNJyvMpo+mXcQnTFIbGWy5izJ9ymO46PhUTojnH7/od5W8HyOfROxHY3jw9AEs6Jw1UX97jR+16dBGMl+KkqEDy8pOWR6CHh1rIJ07wpyFovaNwIgySyH9P0RG6d1xs8Zv6wDX3cLIoVymZEzHp+Y4xws1pDOGfcxMidM9rz2bisKVDAwnr+yzyj2vCgp4gbu265bKeSNNffC+0DFoayBQm9Fx6Mvld0KUimdemfOEO60PD/jCSGELdh+fhPeCa5DhYtnbahiTCq3UG/ULL+l1vjTVdQRftiXLpTxYRS2uAbKb03lK81G6pZ5w7xTGA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RI/aZOOwUPj//SIXbp0nMJBZbozXXrV3Hr+lSYpNosVLkjnzBh4hbOuwck8o16pyIfpdnO0eRFY2YIlxvCNKXJwJEX6r6BHQq3PyDGqWDUfA5QJ9gZ4Bq5BFpNAcaX67spN7pWEhBzLrLB/iPrGXNkv8zt0NJdXB5Nm4lauNgXSfa98Wm9d31lIGvZ2S6CUSD08TlDzpFEnFilNNhLEyyWl4MmjhQj4c72qMggTRXOJewW8O0ggapua/TrTeXTd34QBgHkegyRz29ROjsrSiFfM4XiSJLqKTANHq5NjH1H0Pnk9S75x30sGaiirqYA7ujXeqauvEMWHTOp48wnzK/g==
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=pmanousos@xxxxxxxxxxxxxxxxxxx;
  • Ironport-sdr: X41n6k+G9e9q+dW1ctJkFOQ1dOyBz5DOM1Z7p1b3RWVTe6ZfhiWEsapS06ciZVHTctLt/k8OYj GQ5Y2Qb9rnhw==
Thanks to Steve Chiswell for the tip.

  1.  Brute force method - before launching nmap2 edit 
$GEMPAK/NAWIPS/resource/Nawips and change the values of Nmap*mainw_canvas.width 
and height to your preferred dimensions

  1.  Because this edit will henceforth impact ALL instances of nmap2 that are 
launched, if you want just your own instance(s) of nmap2's dimensions modified 
without impacting anyone else who launches nmap2 on your system, here is a 

  1.  One time: cp -r $GEMPAK/NAWIPS/resource $GEMPAK/NAWIPS/resource.temp  
(resource.temp can be whatever name you want, I just named it as such for 
obvious reasons in this example)
  2.  One time: edit $GEMPAK/NAWIPS/resource.temp/Nawips and change the values 
of Nmap*mainw_canvas.width and height to your preferred dimensions
  3.  Any time: prior to launching nmap2,  set your env variable 
XUSERFILESEARCHPATH to /pathtogempak/NAWIPS/resource.temp/%N   (you can reset 
back to /pathtogempak/NAWIPS/resource/%N whenever you wish to flip back to 
default dimensions)

LMK if you have any questions, and again thanks to Steve for the tip.


From: Manousos, Peter C
Sent: Thursday, August 01, 2019 3:59 PM
To: gembud@xxxxxxxxxxxxxxxx
Subject: How to change the default pixel size of an NMAP2 window?

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 

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


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.
  • 2019 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the gembud archives: