FVWM: Announcement: NsCDE 2.3
Hi, >From this release, FVWM3 is the "main driver", altrough, FVWM 2 compatibility >is maintained. After some 11 months, Not so Common Desktop Environment (NsCDE) 2.3 is finally released. In this release, there are as usual many fixes and improvements, as well as some new features. Below is the list of most important works done for this new release. - Font and Color Style Manager: reload new themes without FVWM restart - Qt6 integration support - Optional Picom X Compositor internal support - Thunderbird 102+ CSS theme integration support - Firefox up to 114+ CSS theme integration support - Font and Color Style Manager reshape, add integrations as separate dialog - (De)Iconify X11 freeze glitch fvwm workaround - Front Panel initial placement fix instead of workaround - Fix GWM FvwmScript segfault on exit - More missing icons in XDG icon theme - Handle gsettings org.gnome.desktop.interface color-scheme - Xscreensaver 6.X support - Add detailed X resources for xcalc and some old Athena based apps - Tuning X resources for more old apps - Font and Color Style Manager: remember widget integration options - GTK3 theme fixes: treat nasty header bar as toolbar - Initial setup: add detailed integration questions, Qt6 support - Front Panel clock: triangle hour and minute hands to match original - GWMPager as popup on workspace change in no-page mode - Fixed some easy-to-make keyboard shortcuts accidental calls - Firefox and Thunderbird user.js additions for nice initial look & feel - Thunderbird HTML compose window toolbar fix - Docs update, many portability fixes, misc fixes, some typo fixes - Portability and test phase fixes -- Hegel3DReloaded, NsCDE
Re: FVWM: NsCDE 2.0 released
On Wednesday, December 29th, 2021 at 9:00 PM, Bob Crochelt wrote: > Hi Miroslav: > Thanks for this. Is there a package that can be installed without compiling > on Fedora 31? > Bob Crochelt Hi Bob, Unfortunately, Fedora has pretty much rapid release cycle. 31 is pretty much old now. I have made F34 and Suse RPMs in github release assets among deb and arch package on my NsCDE testing virtual machines. Supporting Debian is easier, it works out of the box on Ubuntu VM too, which I rarely boot. What I have heard, but not tested yet, Fedora 35 even broke X11 utils and libs in a bunch of 1-file packages so the spec file for RPM that I have made and ifdef-ed to rpm-build on redhatoids and Suse in the same time will probably break on F35 without new ifdefs in build and runtime dependencies. This below is a bad practice, but this one should not break anything: you can probably install it with "rpm -ivh --nodeps --force NsCDE-2.0.fc34.x86_64.rpm [1]. NsCDE really does not have much binary parts: if the "fpclock", "colorpicker" and (if using FVWM 2.X) "XOverrideFontCursor.so" are not binary compatible, you can replace them by the old binaries from NsCDE 1.X series. They are unchanged. You can find them all in /usr/lib64/NsCDE/Linux_x86_64/ after installation. [1] If you are sure you are not missing some Python 3 packages and really needed things which should be available even in very old distors. -- Miroslav
FVWM: Announcement: NsCDE 1.2 release
Hello all, Just to inform, new NsCDE release is out. More older and more retro than ever. :-) NsCDE 1.2 release notes === This is a bugfix release of NsCDE without major new features or changes. For a time this will probably be long term release until new cycle of planned changes and works begins. Lot of fixes which emerged from usage and from GitHub issue reports, also there are some optimizations and polishing on many places. >From the ChangeLog: * Fix Resize from Maximized states to get proper menus * Ensure configure_window event to put de-maximized window into state 8 * Fix StartsOnScreen when repositioning windows * FilePicker: handle directories with spaces * Update insanely old and wrong installation instructions in docs * Expansion of monitor.current of GlobalPager for FVWM3 fix * Set state 8 to true on max to grow helper to avoid confusion from event * Fix ENTRY typo for subpanels * Docs update, fix paths, add notices * Properly handle gtk dark theme flag based on palette 4th colour foreground * Use FvwmCommand again for fvwm and fvwm3, rewrite nscde_fvwmclnt as shell wrapper * Properly handle acpi actions on Linux systems with fake/inactive systemd * Correct padding for active and checked gtk3 buttons (thanks leoctrl) * Remove unnecessary and damaging delete/close/destroy of all windows on quit session * LD_PRELOAD only for FvwmScript on unpatched fvwm 2.X * Fix nscde_setup setting already existing gtk configs * Carefully wrap and call shell interpreter in Sandbox mode * Optimize fallback maximize state for configure_window event * Add pre-compiled convinient help binaries for aarch64 and armv7l * Specify appropriate action for subpanel button 1 3rd mouse click * Front Panel right click localization fixes * Reorganize common WSM button right click options * Front Panel New launcher instructions on click * Fix gtk3 hardcoded red border in widgets.css
Re: FVWM: FvwmCommand docs
Hi, On Friday, December 25, 2020 7:25 PM, Dan Espen wrote: > I recently installed Fvwm3 for the first time. > > I let it install into /usr/local (the default) where I already had > Fvwm2. > > First thing I noticed is that it replaced the FvwmCommand binary. > So, while under Fvwm3 I tried to use FvwmCommand. > > I get the message: > > Cannot find FvwmMFL socket None. > Please start FvwmMFL module from your fvwm configuration. > > So, I put this in my .fvwm2rc: > > AddToFunc StartFunction I Module FvwmMFL > > and took out: > > AddToFunc StartFunction I Module FvwmCommandS > > restarted fvwm3 and got the same message. For a first start with FvwmMFL, you should ensure that FVWMMFL_SOCKET is known to FvwmMFL module, FvwmCommand and fvwm3. Maybe it is better to logout and log in to X session with a new configuration. > So, then I looked at the FvwmMFL man page, no help. > Then I looked for the FvwmCommand man page, it's missing. Yes, FvwmCommand is a legacy wrapper in fvwm3 and has one part of the options FvwmCommand had in fvwm2. It's man page is missing presently. For a time, see getopt loop at the end of the code currently. > What I would like to see are instructions on how to make FvwmCommand > work and ideally instructions on how to set up my Fvwm config file > to have FvwmCommand work with either fvwm2 or fvwm3. > Also I'd like some guidance on the best way to have a setup that works > with both Fvwm versions. It looks like I need to put one of the Fvwm > versions somewhere other than /usr/local since there are conflicts. Some golden catch-all configuration for StartFunction should look like: + I Test (!EnvMatch FVWM_IS_FVWM3 1) Module FvwmCommandS + I Test (EnvMatch FVWM_IS_FVWM3 1) Module FvwmMFL Optionally, I'm also using this as a out-of-func code at the begining of configuration: Test (EnvMatch FVWM_IS_FVWM3 1) SetEnv FVWM3_LOGFILE $[FVWM_USERDIR]/tmp/fvwm.log Test (EnvMatch FVWM_IS_FVWM3 1) SetEnv FVWMMFL_SOCKET $[FVWM_USERDIR]/tmp/fvwm_mfl.sock Logging can be enabled with USR2 signal to the fvwm3 process. As you noticed, it is also good idea to put different major versions of FVWM in different places, not to overlap with files. I usually use "--prefix=/opt/fvwm3" while configuring fvwm3 for compilation. > It looks like FvwmMFL does a lot more than FvwmCommandS does, but > if FvwmMFL was named FvwmCommandS, the transition would be transparent. > I think. Could be a symlink ... in a way similar as FvwmTile and FvwmCascade are pointing to FvwmRearrange. Indeed. -- Hegel3DReloaded
FVWM: Announcement: NsCDE release 1.1
Hi all, I'm announcing first real release of NsCDE (1.1) after 2 years! It can be fetched from here: https://github.com/NsCDE/NsCDE/releases/download/1.1/NsCDE-1.1.tar.gz FAQ: https://github.com/NsCDE/NsCDE/wiki/NsCDE---Frequently-Asked-Questions-(FAQ) NsCDE 1.1 release notes === This is the first "real" release, after 2 years of development. Release focuses on this major points: - Better wallpaper handling in Backdrop Style Manager - FVWM3 used by default when found (if not overriden by explicit environment) - Keybindings has been further logically reorganized - Manual Tiling support with Meta+Alt+R - Documentation update - Portability: NetBSD, OpenIndiana, OpenBSD, DragonFly BSD 1. New features - Wallpapers can now be centered, tiled or aspect-stretched in the Backdrop Style Manager - Windows of the current page can be tiled with Meta+Alt+R, and resized in semi-automatic zoom in and zoom out mode with Meta+F4 and Shift+Meta+F4 - NsCDE has been tested, tuned and fixed to run on NetBSD, OpenIndiana, OpenBSD, and DragonFly BSD. With Linux and FreeBSD support, this covers pretty much all of active free, open and semi-free UNIX and Linux systems - Key bindings are ordered to use Meta, Alt, Meta+Alt, Menu, Escape and Tab in conditions where appropriate, hintful and logical. For example, Menu key based keybindings are for actions about menus. Window movement iconification, size, closing, repositioning actions are bounded to F buttons with similar actions on the same F button, but with Alt or Meta as the modifier 2. Bug fixes - See ChangeLog or "git log" for detailed working list of fixes. Generally most of the fixes are working same-day fixes, but there was some old findings. 3. Removed / discontinued - NsCDE-photos git repo is discontinued and will be removed in the future. With NsCDE there are now coming four file size optimized PNG examples. All other wallpapers, if wanted instead of backdrops, should be provided by the user in $FVWM_USERDIR/photos manually, or imported with "Add ..." button from Backdrop Style Manager 4. Misc - Two years ago, NsCDE has started as consolidation of chaotic private set of fvwm configurations and scripts. Spontaneously, this emerged as something which can be shared by others, and in march of 2019 uploaded as project on GitHub. Since then, lot of features and fixes appeared and active development has beed made on betas, and then long never ending row of release candindates up to rc28. This is now the first release. Since most of the release candidates were really 1.0 already. The first real release will take version 1.1. After it, 1.2 will emerge and so on ...
FVWM: Announcement: NsCDE 1.0rc28
Hi all, I’m announcing new release candidate for NsCDE - rc28. Hopefully the last before non-rc release. :-) This should finally happen at the end of the year, two years after initial development started. NsCDE 1.0rc28 can be downloaded by cloning master from https://github.com/NsCDE/NsCDE.git or by downloading the tarball here: https://github.com/NsCDE/NsCDE/releases/download/1.0rc28/NsCDE-1.0rc28.tar.gz Release notes are below ... NsCDE 1.0rc28 (pre)release notes This pre-release focuses on 5 major points: - FVWM3 support - Menus and keybinding ergonomic reworked for usability as well as CDE similarity where applicable and useful - Front Panel color 8 and colored WSM options support, which covers a wide range of CDE variants on old UNIX systems - Reworked OccupyWorkspace/Page dialog for extended usability - General polishing and fixing for release 1.1 which should happen in the middle of december 2020 on the 2th anniversary of starting work on NsCDE 1. New features - Color Style Manager in "Number Of Colors ..." dialog now offers two new (sub)options: to use color 8 of the palette for icon background on Front Panel and interior Icon background as on some versions of CDE on HP-UX and AIX. Further, some versions of UNIX systems had Workspace Manager in the color 6 of the palette, which is also offered as an option in NsCDE now. Both of this features are available only in 8-colors mode, not in 4-colors. Because of necessary internal changes, (Colorset 23 addition) $FVWM_USERDIR/NsCDE-Colorset.conf must be rebuilt. After upgrade, Color Style Manager and popup message with that info will appear on screen after upgrade from pre-1.0rc28 and (re)start of FVWM. Select existing or any other color scheme to get Front Panel properly colored again. - Icons can now be focused and browsed with up/down arrows on the one page with Meta+Alt+i. Pressing Meta+Alt+i selects back last non-iconic window on the current workspace/page. - Smooth use with FVWM3 as much as this can be, during this still "young" phase of FVWM3. On system with both FVWM2 and FVWM3 installed, FVWM2 will still be used by default, but this can be overriden by putting FVWM_BIN variable in startup or login profile to point to main FVWM2 or FVWM3 binary. - Occupy Workspace and Occupy Page dialogs has been merged into one app. When called as "Occupy Workspace" initial behaviour and list is workspaces, and when called as "Occupy Page" initially list of pages will be shown. By pressing workspace or page radio button, or space key shortcut, mode of operation will switch from pages to workspaces and vice versa. In short, it is enough to call Occupy to select workspace and page in one move. - Window Operations Menu can be now called with Meta+Alt+Space or Meta+Alt+m. - CDE Alt+ArrowUp and Alt+ArrowDown raise/lower overlapping windows support. - Flipping windows on the current workspace/page with Ctrl+Menu and Ctrl+ISO_Level3_Shift - Icon placement now in pixels matches CDE placement of iconified windows. - Menus are now logical and consolidated. Specially Window Operations Menu. There are no dead or non-usable options presented. Dynamic menus are used. This is now tuned also for the Front Panel and Subpanels menus. - It should be possible now to work with keyboard without touching mouse in the most cases. - New logo based on brutalism achitecture style and patterns, which nicely fits general CDE and NsCDE experience. - nscde_setup wizard now supports localization. - Select Area screenshot option 2. Bug fixes - See ChangeLog or "git log" for detailed working list of fixes. Generally most of the fixes are working same-day fixes, but there was some old findings. 3. Removed / discontinued - Removed old logo, removed some faulty and wrong backdrops and the rest consolidated. Removed duplicate and very similar palettes from some old non-standard CDE palettes collection. - OccupyWorkspace and OccupyPage dialogs are replaced with unified Occupy dialog. 4. Misc - Backdrops were consolidated, named logically from their ad hoc choosen names, palettes were also consolidated with duplicates and almost duplicates removed. - New TallSkyDark and TallSkyLight backdrops for moden big displays. Diethering of course remains. - First mouse button click on the root window now gives root menu, not double click. Double click will give Window Options menu. -- Hegel3DReloaded
Re: COVID-19: Hope everyone's well
On Saturday, 21. March 2020 22:06, Dominique Michel wrote: > Le Sat, 21 Mar 2020 15:20:06 +, > Thomas Adam tho...@fvwm.org a écrit : > > > Hi everyone. > > Just emailing to check that everyone's OK and not suffering too much > > at the moment. I know different countries are largely doing the same > > things as one another -- and I'm working from home for the > > foreseeable. > > Western politicians are sick. From here: > https://www.worldometers.info/coronavirus/?fbclid=IwAR1ge4wDYvw_la-z2L2PTb8Rg0AIUC8tGNgvq668jSGyHhApStSXIMBJLuo > > these statistics shows only the identified cases. > Total c. Death p. Recovered p. Active c. Cases/1Mo pop > Switzerland 6,746 79 15 6,652 779 > Italy 53,578 4825 6072 42,681 886 > China 81,008 81,008 71,740 71,740 56 > > In Switzerland, even the biggest hospitals have no rapid tests like in > China. If you are not between life and death, they just send you home > with no diagnostic, with not even a protection mask, but with the > consign to come back if things are going worst for you. I know that > because we have two cases at home. They are better now and keeping > improving. They will be fine. I am fine too. As much of us, I just > get barking during 2 weeks with a few sporadic and fugitive instants of > fatigue, but I am just fine now. > > That statistic show than, if you are sick enough to get into the > hospital, you have more risks to die than to survive in Switzerland. > Even Italy is doing a much better job. > > Politics are sick peoples. They last but not least message was "It > is time to loan money to the banks. If you cannot afford to pay > back into the future, the Confederation (our taxes!!!) will assume that > debt and pay the bank." After decades of eugenics economical policies > against the public sector, that virus is turning their system into > physical eugenics. That virus will maybe be the one that will put the > Swiss system on its knees. We will see. > > > I really do hope no one's suffering and feeling unwell. Let's keep > > in touch, please. > > For now, is it spring and the weather is just fine. We are working and > having a good time in the garden, the kitchen is full of food and > we will more die of eating than of that virus. > > I hope everyone of you and your families will be fine! > Dominique Best wishes to all FVWM developers from Hegel3DReloaded (NsCDE, Miroslav ...) from Zagreb. To add insult to injury, my town experianced large earthquake early this morning - biggest from y1880. Until yesterday, situation with corona was pretty much under control, but now we have contradicting instructions: "stay at home" vs. "get out from houses" specially old center of the town. I'm on the south in new steel-secured new building, but my parents are in center. I will probably have to get them at my place for a couple of days and take care of them. They are near 80, so this is additional risc in this sureal pandemic times. Thomas, expect delays in cooperation with debugging fvwm3 this days. :-) Additionaly, I'm working my IT jobs from home, things seemed as tight but good plan for overcoming pandemic times, but now will be even more difficult. We need a good Window Manager for post-apocaliptic times. And FVWM is the best! -- Miroslav (Hegel3DReloade, NsCDE)
Re: FVWM: FVWM3: RandR support ready for testing
On Saturday, 4. January 2020 16:29, Thomas Adam wrote: > What I'm hoping for right now is the bare-bones functionality of: > > - Correct screen detection (that is, correct number of physical screens) -- > this is currently printed to STDERR when FVWM3 starts up, so check there; Works. > - Commands such as MoveToScreen with a valid RandR monitor name works; Works. > - The 'Screen ' conditional works for All/Any/Current, etc I don't know how to test it. I have tried in FvwmConsole "All (Screen DP1) Iconify", but stderr says: [fvwm][CreateConditionMask]: <> Use comma instead of whitespace to separate conditions > - Monitors can be added/removed/changed, and FVWM3 shouldn't need a restart > to > pick up on any changes; If new monitor is added either before X login or with "xrandr --output eDP1 --mode 1920x1080 --primary --output DP1 --mode 2560x1440 --right-of eDP1 --noprimary" Half of the X apps windows opened on the new DP1 screen (okular, mate-terminal, xpdf, FvwmScripts) does not have focus (I'm using SloppyFocus policy). Gvim for example has the focus. Fvwm's "Restart" command solves this. Sometimes (before Restart), if I move mouse pointer outside unfocused window and then back in but only to the titlebar, it gets focus, but loses it when I proceed with mouse pointer from titlebar into the windows. Typing with keyboard on new nonprimary display is not posible in most of the X apps prior to Restart. Is this something known or should I open issue on github? > - FvwmIdent should report which monitor a specific window is on correctly Works. ... one of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs. -- Robert Firth
Re: FVWM: Style ... SkipMapping
On Monday, 18. November 2019 17:22, Dr Rainer Woitok wrote: > Greetings, > > On Saturday, 2019-11-16 16:42:01 +, Hegel3DReloaded wrote: > > > ... > > You need to leave this page. > > Well, when I'm there, I'll have to leave this page. But I don't want to > get there in the first place. That's why I used the "SkipMapping" style > which I THOUGHT would prevent exactly this. > > >Since this is probably in the InitFunction, then simply: > > > > No, as could be clearly seen, it's not in the "InitFunction" but rather > in a shell script named "firefox-start-up.sh" which contains the command > "nohup firefox > /dev/null 2>&1 &". > > But perhaps that's the cause? Does "SkipMapping" only work for applic- > ations started from within the "fvwm" configuration file? Could anyone > shed some light on this? If it is running on the same $DISPLAY, it should behave exactly the same no matter if started from FvwmButtons, shell script or database trigger which puts job in RabbitMQ ... Your problem appeared trivial to me, but I have tried this in a test environment and found VERY interesting behaviour: Firefox is desparately trying to get in focus and under the mouse when started. It goes to the desk and page we told it, SkipMapping works, but window program is jumping back to you like a stray dog for a peace of meat. It is fast, so you cannot see it without serious throttling of the CPU and GPU. I have tried couple other applications, but none of them exercises this behaviour. Tried even with InitialMapCommand style - with that, we have more freedom for experimenting. This doesn't work (Firefox gets back): Style Firefox InitialMapCommand MoveToPage 1 1 This works as a workaround: Style Firefox InitialMapCommand Schedule 500 MoveToPage 1 1 This: Style Firefox StartsOnPage 0 1 1, SkipMapping, InitialMapCommand Schedule 500 MoveToPage 1 1 will produce the following funny scenario: - Firefox appears on X server - Immediately mapped by FVWM on page 1 1 - It gets back to you like a dog - ~ 0.5 seconds later, FVWM will kick it back where it belongs. :) I remember couple years ago, when 2-3 seconds after mapping Firefox moves cca 1cm above top edge of the screen. It was the cat and mouse game between Firefox and FVWM ... FVWM wins ... most of the time. > > Why not something like this in InitFunction or SessionInitFunction? > > > > - I Exec exec firefox > > - I Wait Firefox > > - I Next (Firefox) MoveToPage 0 1 > > From the "fvwm" manpage I gather that "Wait ..." "causes execution of a > function to pause until a new window matching ... appears". > > That's exactly what I want NOT to do! I do NOT want to watch Firefox > waiting for the WiFi to become ready and then to reload all its tabs! I > want to enter commands into my terminal window in another page instead! I think you don't understand. It will last only up to the point when Firefox window appears on the screen, after that, it will be moved from the way, and can load it's tabs next two days if it wants. BTW, This is the other way to acomplish certain order on workspaces after login. It is preferred by me, so I didn't knew about Firefox agressive behaviour until now. > By the way: could you please explain the purpose of the "Next (Firefox)" > clause after using "Wait Firefox" to wait until the window has mapped? > Why not just use a plain "MoveToPage 0 1" here? Because MoveToPage X Y will most probably be executed before Firefox appears. In short, your best change is InitialMapCommand with Schedule X hack. Maybe not 500, maybe it can be 200 or 50 ... practice. ... one of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs. -- Robert Firth
Re: FVWM: Style ... SkipMapping
On Saturday, 16. November 2019 15:20, Dr Rainer Woitok wrote: > Greetings, > > maybe I totally misinterpret the "fvwm" manpage ... > > 1. What I want: > During the login process on my laptop I want to fire up Firefox using > a page different from the default page where my terminal window is > opened. This way I can start entering commands without having to > wait for Firefox loading all its tabs. > > 2. What I do: > > $ grep -C2 Firefox ~/.fvwm/config > > Always position a "firefox" window on page "0 0 1": > > > > > Style Firefox FixedPPosition > Style Firefox PositionPlacement 0p $[WINDOW_TOP]p > Style Firefox StartsOnPage 0 0 1 > > == > > $ grep -iC2 firefox firefox-start-up.sh > > Finally start "firefox" in its own page without going there: > > = > > FvwmCommand 'Style Firefox SkipMapping' > nohup firefox > /dev/null 2>&1 & > > 3. What happens: > Firefox is starting in its own page, but this page is also the one > shown on the screen rather than the page containing my terminal wind- > ow. You need to leave this page. Since this is probably in the InitFunction, then simply: + I GoToPage 0 0 (for example, you want firefox on 0 1, and terminal is waiting for you on 0 0). Why not something like this in InitFunction or SessionInitFunction? + I Exec exec firefox + I Wait Firefox + I Next (Firefox) MoveToPage 0 1 It will only flash for a part of the second and go away from your terminal. -- ... one of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs. -- Robert Firth
Re: Patch proposal for FvwmButtons with two new options
On Monday, 29. April 2019 7:10, Thomas Adam wrote: > Where's your patch? I have never achieved to remember attaching what I refer to. Sorry. :-( Here it is. > I can't say I see the need for what you're describing as 'WindowName'. But I > might be persuaded otherwise with an example of what you're trying to do. Simply put, if I have FvwmButtons popup subpanel with title "Applications" everything is ok: I can refer to it with "*Applications:" in configuration, but if I want title "My Applications" then this doesn't work obviously. > That said, FVWM2 is in maintenance mode, and as such, I'd be extremely > reluctant to shoehorn in more features like this. :-\ -- ... one of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs. -- Robert Firth FvwmButtons_sunkraise_windowname_unified.patch Description: Binary data
Patch proposal for FvwmButtons with two new options
Hello all, I have been using and abusing FVWM for a 14-15 year now. I have made it long ago to look like CDE, and recently had a chance to rewrite this all as some kind of heavyweight theme and wrapper around fvwm. Called it NsCDE (Not so Common Desktop Environment). ( https://github.com/NsCDE/NsCDE.git ) Yes, many say this is sick, but I like it and I have discovered there are much more lunatics like me in wild, so I'm not alone. :-) But for some things to look smooth and more like original I had to alter code of the FvwmButtons. I have added two options: WindowName and second argument for arrow indicator on triangle which says if triangle will look pressed or depressed (indicator 12 in|out). Default is out and it can be ommited for backward config compatibility. WindowName is when I want transient FvwmButtons panel to have title bar with title that contains spaces and symbols which cannot be part of the alias to FvwmButtons module in configuration. I'm not much a programmer. Specially not for C, but I have a text editor and a good will. I'm attaching a patch proposal in the hope it will be considered and eventualy merged if it is not really bad. Edited also manpage. Sorry for my horrible english ... ... one of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs. -- Robert Firth
Opinion about patch for two new small functionalities in FvwmButtons
Hello all, I have been using and abusing FVWM for a 14-15 year now. I have made it long ago to look like CDE, and recently had a chance to rewrite this all as some kind of heavyweight theme and wrapper around fvwm. Called it NsCDE (Not so Common Desktop Environment). Yes, many say this is sick, but I like it and I have discovered there are much more lunatics like me in wild, so I'm not alone. :-) But for some things to look smooth and more like original I had to alter code of the FvwmButtons. I have added two options: WindowName and second argument for arrow indicator on triangle which says if triangle will look pressed or depressed (indicator 12 in|out). Default is out and it can be ommited for backward config compatibility. WindowName is when I want transient FvwmButtons panel to have title bar with title that contains spaces and symbols which cannot be part of the alias to FvwmButtons module in configuration. I'm not much a programmer. Specially not for C, but I have a text editor and a good will. I'm attaching a patch proposal in the hope it will be considered and eventualy merged if it is not really bad. Edited also manpage. Sorry for horrible english ... ... main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs. -- Robert Firth FvwmButtons_sunkraise_windowname_unified.patch Description: Binary data
