FVWM: Any idea how to bind menus to the mouse on the desktop?

2016-06-11 Thread Paul King
Hello, Far from a newbie, I downloaded the latest source for FVWM, compiled it and ran it in Cygwin. I appear to have lost the mouse button menus on the root desktop.(I just have the "Builtin Menu" for the left button. No other root menus). I still have the same config scripts as for 2.5.x. It

Re: FVWM: Any idea how to bind menus to the mouse on the desktop?

2016-06-11 Thread Thomas Adam
On Sat, Jun 11, 2016 at 12:18:43PM -0400, Paul King wrote: > Hello, > > Far from a newbie, I downloaded the latest source for FVWM, compiled it and > ran > it in Cygwin. I appear to have lost the mouse button menus on the root Which version of fvwm? > desktop.(I just have the "Builtin Menu" f

Re: FVWM: Ideas for a new configration file

2016-06-11 Thread Thomas Funk
On 06/10/2016 03:06 PM, Thomas Adam wrote: Hello all, As some of you may be aware, the master branch in git now has code which not only removes a lot of older modules, but also removes any mechanism for having a default configuration. There was a previous discussion on having a new default conf

Re: FVWM: Any idea how to bind menus to the mouse on the desktop?

2016-06-11 Thread Paul King
.fvwm2rc is attached. Paul On 11 Jun 2016 at 23:26, Thomas Adam wrote: > On Sat, Jun 11, 2016 at 12:18:43PM -0400, Paul King wrote: > > Hello, > > > > Far from a newbie, I downloaded the latest source for FVWM, compiled it and > > ran > > it in Cygwin. I appear to have lost the mouse button m

Re: FVWM: Any idea how to bind menus to the mouse on the desktop?

2016-06-11 Thread Paul King
On 11 Jun 2016 at 23:26, Thomas Adam wrote: > On Sat, Jun 11, 2016 at 12:18:43PM -0400, Paul King wrote: > > Hello, > > > > Far from a newbie, I downloaded the latest source for FVWM, compiled it and > > ran > > it in Cygwin. I appear to have lost the mouse button menus on the root > > Which

FVWM: Is there a mechanism to get the screen coordinates

2016-06-11 Thread Donald R Laster Jr
I am using a shell script to open xterms in a 24x4 virtual screen/viewport environment and discovered that the --geometry option appears to run into a problem with the value of the window placement exceeds 32767: 133x33+29760+1576 (the 29760 number's position) I was using an enviro