* Mikhael Goikhman
> With my suggestion you don't need to modify FvwmWindow structure.
>
> The suggested WindowNameFormat may be either a global command or a style
> option, but not a window context command like yours. Then this format
> string would be stored either globally or in style structure.
>
> visible_name contains the final name after expansion just like now.
Hm. Perhaps I've been unclear. I use this functionality to assign
every window a different title suffix, where the contents of this
suffix indicate which hotkey will bring focus to the window in
question. The hotkeys are assigned from a arbitrary range; at the
moment I'm using the letters A..Z, and Win-A will bring focus to the
window marked with the suffix [A]. This hotkey/enumerated id/suffix
_is_ a window context property, and I can't see how to make the final
visible_name contain this without storing it in the window context
somehow.
(Of course, the window id <-> hotkey mapping exists in the internal
state of the module providing this functionality as well, but as far
as I'm aware you can't do module callouts in string expansions. If
you can, then that would be a way to do this without adding stuff to
the window context.)
> There are other problems with your patch, [..]
No doubt there are, and I'll be happy to have a go at ironing them out
if/once the overall approach is deemed acceptable.
Arne.
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
