FVWM: Any idea how to bind menus to the mouse on the desktop?
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 appears as though the mice are not configured in the same way anymore. Can someone tell me where the configuration for root window menus for the mouse is done unde the current version? I have the start menu, although I am not exactly thrilled about that menu either, as I seem to have lost some of my sub-menus. Paul King
Re: FVWM: Any idea how to bind menus to the mouse on the desktop?
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" for the left button. No other root > menus). I still have the same config scripts as for 2.5.x. It appears as > though > the mice are not configured in the same way anymore. Can someone tell me > where > the configuration for root window menus for the mouse is done unde the > current > version? None of that has changed, so it's likely something else. > I have the start menu, although I am not exactly thrilled about that menu > either, as I seem to have lost some of my sub-menus. Can you send through your config, please? I can't tell anything about your set up otherwise. -- Thomas Adam
Re: FVWM: Ideas for a new configration file
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 configuration file here: http://thread.gmane.org/gmane.comp.window-managers.fvwm.general/6611/focus=7214 I recommend reading it first as it does seem to contain a lot of useful information. I'd like to hear proposals from people about the sorts of things that might be useful, as well as how we can use this new configuration file to guide new users. The point that I made in my original email in the aforementioned thread still stands: this configuration file has to be a tutorial for users. After reading the discussion about a new default configuration file and that one on the forums [0] I'll try to collect the main points and attach my thoughts: It should be minimal, but functional * not depending on *any* external dependencies that do not come with FVWM itself. => No excludes? xload, xclock, ...? * New FvwmButtons -- swallowing things like: - FvwmIconMan - FvwmScript (maybe a clock?) - FvwmPager => I liked the old one [3] (on the right bottom) but that one Nick drawn here [4] (at the end of the post) looks also interesting * The config file should be documented heavily -- as an example to look towards for new users. => I like the commenting Nick did [2] - perhaps with links to the Fvwm documentation (which increase the maintenance on the other hand). It should look "modern" --- * The colour scheme needs to be changed. The existing default one is horrible. * Don't look like MWM by default * Change the window decors a bit -- maybe use colorset gradients * Using vector buttons for the titlebar buttons => There was a thread started on the list [1] where people discussed what is wanted from a "modern" theme: - 3 pixel window borders - 1 pixel borders for modules - Commenting the config is very important ... and much more but unfortunatelly the suggestions done in ietherpad are lost. Perhaps pebcack or someone else has written it down somewhere ... The idea with a banner which tells the user to click everywhere to open the RootMenu is pretty nice! Best Regards, Thomas Btw ... Thomas, do you have already the latest tarball of Nicks and your work? It would be very interesting to have a look at it :-) [0] http://www.fvwmforums.org/phpBB3/viewtopic.php?f=40&t=205&sid=77e5e5c2b1727d2ed26675290fbd27e1 [1] http://thread.gmane.org/gmane.comp.window-managers.fvwm.devel/4901 [2] http://www.fvwmforums.org/phpBB3/viewtopic.php?p=1085&sid=9769496f2e3e5bbce284604c521cb0ea#p1085 [3] http://jerome.harckmans.be/wp-content/uploads/2009/04/fvwm_default.png [4] http://www.fvwmforums.org/phpBB3/viewtopic.php?p=1343#p1343 -- -- "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." -- Albert Einstein
Re: FVWM: Any idea how to bind menus to the mouse on the desktop?
.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 menus on the root > > Which version of fvwm? > > > 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 appears as > > though > > the mice are not configured in the same way anymore. Can someone tell me > > where > > the configuration for root window menus for the mouse is done unde the > > current > > version? > > None of that has changed, so it's likely something else. > > > I have the start menu, although I am not exactly thrilled about that menu > > either, as I seem to have lost some of my sub-menus. > > Can you send through your config, please? I can't tell anything about your > set up otherwise. > > -- Thomas Adam -- Enclosure number 1 #-# # # Sample-95: .fvwm2rc example configuration file for a more or less Windows95 #look and feel # # The suggested way to install this configuration file is to (re)move # any .fvwm2rc file you have in ~/.fvwm or ~ and run fvwm without any # startup file. # # Then, run the "Setup 95 Script" from the root menu. This creates # and installs the following configuration files: .fvwm2rc, bindings, # decorations, functions, globalfeel, menus, modules, startup, styles, # iconstyles. # If perl is not installed on your machine (my god), only one file is # installed: .fvwm2rc (and this configuration should work). Some instructions # are given below for a first editing of this file. Maybe the first thing # to do in this case is to segment this file. For that, you can move the # parts of this file between the marks "#SEG foo" and "#SEG xyz" into a # file foo and add "Read foo" to this file (until the "#SEG END" mark). # # You do need the fvwm_icons distribution installed in the fvwm image path. # If they are installed in another directory use the ImagePath command # below or set this directory via the Setup95 Script. # # For the sound effects to work you need the fvwm_sounds distribution # installed and an .au player. The Setup95 Script allows you to set the # installation directory of this distribution as your sound player (if not, # manually edit the *FvwmEvent commands). Note that if you use rplay, the # rplayd daemon must be run. # # The Setup95 Script asks you to choose between two looks, one is close # to Windows and the other one is close to a "classical" fvwm look. # For switching from the windows look to the fvwm one by hand, comment the # x lines that follow the #WIN x lines and uncomment the x lines that # follow the #FVWM x lines. # # There is an option for machines with a "low X server (comment #FAST and # uncomment #SLOW). You may have to use some intermediate values (Base # Configuration can help and if you "rebuild Sample-95" .FvwmBaseConfig # may over write the effect of this option). See also the BackingStore and # SaveUnder style. # # I've tried to use very common apps (like Gimp or Netscape) so that this # configuration file is as universal as possible. For menus, the Setup 95 # Script starts with a big menu. Comment the menu entries that correspond # to applications not in your path. Moreover, the Setup95 Script asks you # to set your preferred terminal, editor and file manager (#PREF). However, # you surely need to edit the menu definitions and the BarButtons # configuration to get your preferred applications. # # I have a laptop so I have added one laptop option. If you answer yes # to the Setup95 question: "do you have a laptop?" you will have xapm # in your BarButtons. To get it by hand, just uncomment the line that # follows #LAPTOP. # # GNOME and KDE menus: fvwm has a perl script that can build GNOME and # KDE menus: fvwm-menu-desktop (man fvwm-menu-desktop for details). If GNOME # and/or KDE are installed in your machine, Setup95 will ask you which menus # you want to add to your Programs sub menus (G_SM_G/F means FvwmGtk/fvwm # gnome system menu, G_SM_G/F means FvwmGtk/fvwm gnome user menu, G_RHM_G/F # means gnome redhat menu, G_M_G means that we need to start FvwmGtk, K_SM # means kde system menu and K_UM means kde user menu. You may have to edit # the line G_*M_* to set your GNOME install directory (Setup95 try to # find it)). KDE (mini-)Icon Styles and KDE ImagePath (#K_M) are provided # if you select one of the KDE menus. For GNOME, (mini-)Icon Styles are # provided if you have the panel installed (#G_ST) and the image path is # set if you ask for FvwmGtk menus (#G_M_G). # # GNOME session: This configuration can be used under gnome-session. In # this case almost no modules are started (for a first installation). # However, you may u
Re: FVWM: Any idea how to bind menus to the mouse on the desktop?
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 version of fvwm? $ fvwm --version fvwm 2.6.6 compiled on Jun 11 2016 at 05:43:41 with support for: ReadLine, XPM, PNG, SVG, Shape, XShm, SM, Bidi text, Xinerama, XRender, XCursor, XFT, NLS > > > 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 appears as > > though > > the mice are not configured in the same way anymore. Can someone tell me > > where > > the configuration for root window menus for the mouse is done unde the > > current > > version? > > None of that has changed, so it's likely something else. > > > I have the start menu, although I am not exactly thrilled about that menu > > either, as I seem to have lost some of my sub-menus. > > Can you send through your config, please? I can't tell anything about your > set up otherwise. I will send them to you off-list. I noted some file corruption which I later fixed under vim. Also, I used FvwmCommand to debug those files. They appear to have no issues when in FvwmCommand, I invoke commands such as Read modules, Read bindings, and so on. I take it you just want .fvwm2rc > > -- Thomas Adam
FVWM: Is there a mechanism to get the screen coordinates
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 environment that has double monitors configured via xrandr. I have modified the script to be able to use the X command option: -xrm "*Page:x y z" (example: -xrm "*Page:0 21 1") I would like the script to be able to determine the coordinates of the virtual screen the script is being run within. Thus if the script is being run in the virtual screen/viewport 10 (horizontal) at 2 (vertical) it could determine the location it is at and make any position adjustments desired. So far I have not found any way that would allow this. Sincerely, Donald R Laster Jr.
