Hi.
I’m currently rewriting my fvwm-config and trying to get two FvwmIconMan running. What I want is one IconMan to show all but the iconified windows and the other to show ONLY the iconified windows. The config look like this:
Style FvwmIconMan NoTitle, Sticky, WindowListSkip, BorderWidth 0, HandleWidth 0
DestroyModuleConfig FvwmIconMan: *
*FvwmIconMan: NumManagers 2
*FvwmIconMan: FocusAndSelectButton down
*FvwmIconMan: FocusButton down
*FvwmIconMan: IconButton down
*FvwmIconMan: PlainButton down
*FvwmIconMan: SelectButton down
*FvwmIconMan: Action Mouse 0 N sendcommand Nop
*FvwmIconMan: Colorset 8
*FvwmIconMan: FocusAndSelectColorset 9
*FvwmIconMan: FocusColorset 9
*FvwmIconMan: ReliefThickness 1
*FvwmIconMan: Font $[FontShadow]
*FvwmIconMan: Resolution global
*FvwmIconMan: DrawIcons Always
*FvwmIconMan: FollowFocus True
*FvwmIconMan: UseWinList True
*FvwmIconMan: Sort name
*FvwmIconMan: 1 Title "IconManSideBar"
*FvwmIconMan: 1 IconName "FvwmIconMan: Iconified"
*FvwmIconMan: 1 ManagerGeometry 1x1
*FvwmIconMan: 1 ButtonGeometry 24x24
*FvwmIconMan: 1 ShowOnlyIcons True
*FvwmIconMan: 2 Title "IconManTaskBar"
*FvwmIconMan: 2 IconName "FvwmIconMan: TaskBar"
*FvwmIconMan: 2 ManagerGeometry 1x1
*FvwmIconMan: 2 ButtonGeometry 24x24
*FvwmIconMan: 2 ShowNoIcons True
+ I Exec xsri --geometry=1152x864 $[WallpaperPath]/$[Wallpaper]
+ I Module FvwmAuto 300 raise
+ I Module FvwmPager 0 0
+ I Module FvwmButtons
+ I Module FvwmButtons FvwmBar
+ I Module FvwmIconMan
The odd thing is that only the first IconMan (FvwmIconMan: 1 …) is working regardless of which one (“IconManTaskBar” or “IconManSideBar”) is configured as manager number 1. The other is just showing the title, nothing else. Restarting fvwm does not help.
I read something about transient windows could perhaps lock the IconMan, but adding
I think it would be better to just create two aliases for the two FvwmIconMans as now FvwmButtons will try to swallow both of them as they’ll have the same title which might be causing the strangeness you see.
However, I don’t know if it is the correct way of solving the problem. The man page for FvwmIconMan states that it needs to know how many instances there is running. I understand this as my first attempt is the right way to do it. The problem then seems to be the Show and DontShow lists associated with each instance of the manager. Since I dindn’t manage to find the patterns for:
*FvwmIconMan: 1 Show [OnlyIconified]
...
*FvwmIconMan: 2 DontShow [OnlyIconified]
...
or equvalent patterns, I’ll stick with current solution.
(I’m rather late in joining this thread, so I apologise.)
That’s not quite true – one instance of FvwmIconMan doesn’t care about the other instance, or other instances (depending on how many you have running.) Indeed, the concept of aliasing a module is just so – so that you’re able to have more than one instance.
Back before module aliasing was possible in FVWM, you used to have to manually symlink a new module name to the main FvwmMODULE file on the disk. Thankfully that’s no longer the case.
Basically, if you use alising (as people have tried to show) then the two managers are independant of each other. However, you can (and this is the only example of a module where it applies) configure FvwmiconMan under one roof, still using more than one manager. Here’s a half-baked example:
*FvwmIconMan: NumManagers 2
*FvwmIconMan: Resolution page
[..]
*FvwmIconMan: 1 Title "rxvt windows"
*FvwmIconMan: 2 Title "all windows"
Which disposes of the need for aliases in this example. By and large, aliasing is the way to go, though.
