Great, so this can be done. SendToModule needs to be delayed. I couldn’t get it to work in hideBar.sys but in SimpleButton/simpleB.sys that has the app icons.
This is a temporary solution with Schedule. In the forum, somewhere it was mentioned a better way. Add this at the end of simpleB.sys.
To keep things simple, I made it in one file as per manpage example.
# To include the panel in a button
*FvwmButtons: (Panel(down, delay 0, steps 16) \
SubPanel "Module FvwmButtons SubPanel")
# To define the panel as an instance of
# FvwmButtons with a different name:
*SubPanel: (Icon my_lock.xpm, Action Exec xlock)
*SubPanel: (Icon my_move.xpm, Action Move)
Panels are more designed to be shown temporally when opened. If you want a more permanent button, don’t put it in a Panel, instead just have it in its own FvwmButtons or just position it where you want. You could make a button that could hide/show this window. This would probably be a better approach than trying to make Panels work for this.
That’s a long time ago. Maybe no one thought of using Panel command for icon panels and large-size pagers. Quickly giving more space.
Other hide/show configs may become too complex.
At least, not to use Schedule for the PressButton… it is “sluggish” though I have a fast machine (Schedule 500). My friend has Schedule 2000. Any other alternative solution, or fix it?
Again, this is not what the FvwmButtons panel’s were designed for, hence you are having to do some additional messing with timings to get them to start open. Maybe FvwmButtons could be updated to deal with this, but in the end all it is doing is showing/hiding a second FvwmButtons window.
Other options are not that complex to just create FvwmButtons (which you have done already) and just hide/show it as desired from button clicks, etc. I would go this route vs messing with Schedule and timings to try to make Panels do something they are not currently designed for. The effect would be the same and in the end easier to control since you don’t have to mess with Schedule timings.
Since you don’t seem to listen to reason, you should at a minimum add the Schedule to the StartFunction so it is more reliable and always runs after the configuration is finished being read.