On Sat, 14 Dec 2002, Dan Espen wrote:
> Marcus Lundblad <[EMAIL PROTECTED]> writes: > > > > > > On Sat, 14 Dec 2002, Dan Espen wrote: > > > Hmm, hangover, I'LL TRY NOT TO SHOUT! Thanks! :) > > Yep, its the same. > > > Also I'm thinking about wether Style Unclosable should apply also for > > tear-off menus. > > The argument in favour: The user has requested this > > expliciltly through a style > > The arguments against: It is incosistent with how hints are handled and > > there is no other way to close it (what does destroy do on a tear-off, > > kill fvwm?). > > It only takes a second to try it. > (No it doesn't kill Fvwm.) > > I don't know why we would need a Style Unclosable. > We have more direct methods of removing the close button > from a titlebar. (I know it affect context menus too.) Well, too late :-) I already implemented (Un)Maximizable, (Un)Iconifiable (spelleing?), (Un)Closable. I also implemented AllowMaximizeFixedSize/DisallowMaximizeFixedSize if DisallowMaximizeFixedSize is on, if resize is not permitted then maximize is automatically also disabled (in is_function_allowed). AllowMaximizeFixedSize gives the default behaviour ie. maximize is allowed unless turned off by hints or through the style option. > > I think the idea of the MWM hint, is that applications that didn't > implement the delete window protocol would set the hint. This > was to encourage the user to use other means to close the window, > perhaps the file->close menu entry. > It all seems pretty pointless anyway, Fvwm can still apply close/delete > to the window. I always thought it was more for appearance. Yes, I guess it's more for appearance. But I found a use for Uniconifiable. When using the icon box, either I have to turn on icon for the icon box Style * NoIcon Style FvwmIconBox Icon or assign a special menu for the icon box window that lacks an iconify entry. In my opinion the Uniconifiable style is more clear than using special functions. And even if you replace all Iconify in the config with a complex function it's still possible to use an FvwmConsole. And so for consistency I thought I might as well implement the others. And I guess I'll trow in conditionals for these 3 aswell. //Marcus > > -- > Dan Espen E-mail: [EMAIL PROTECTED] > -- 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]
