On Wed, Jun 19, 2002 at 01:05:36PM +0000, Mikhael Goikhman wrote:
> On 19 Jun 2002 13:54:05 +0200, Dominik Vogt wrote:
> >
> > On Mon, Jun 17, 2002 at 02:30:53PM -0400, parv wrote:
> > > in message <[EMAIL PROTECTED]>,
> > > wrote fvwm-workers thusly...
> > > >
> > > > I'm not quite happy with the tear-off menu code yet:
> > > >
> > > > - Torn off menus have a strange focus policy.
> > > > - There is no good way to handle tear off menus with the mouse.
> > > > - Placement and sizing of the menus is not perfect.
> > > >
> > > > What do others think about tear-off menus? What should be done?
> > > > How can we improve usability? Are there other issues I missed?
>
> First, tear menus are great.
>
> Of course they should be implemented as a module not to cause problems,
> but until then the current implementation solves most of the needs.
Module or not, as long as menus grab about every key on the
keyboard, they won't cooperate nicely with the rest of fvwm.
> My problems. I am not sure MenuStyle should not be allowed when a tear
> off menu is on the screen.
[snip]
> Is it possible to just automatically recapture all affected tear offs
> after MenuStyle is changed?
Hm, this would mean to unmap all affected tear off menus, tear
out from scratch but don't modify their position. Sure, that's
not easy but possible. And then, it would be nice to create
tear-off menus from scratch, without posting the menu normally
first.
> Another issue, I think the top menu title should be separated using
> ("" TearMenuOff), not ("" Nop) separator. Then mouse 2 binding on a title
> may be removed.
Can't remember what this is about right now. I'll look it up in
the code later.
> And finally. It would be nice to document tear offs and TearMenuOff.
Once we have found a nice solution. I don't want to spend a lot
of time documenting features that are thrown away again.
> > > pressing "escape" on torn off menu's window title doesn't make it
> > > disappear, only on the actual menu (items).
> >
> > Should it? Closing tear-off menus should be more difficult that
> > closing normal menus so that you don't close them accidentally.
> > To deactivate the menu, simply move the mouse away. What do
> > others think of this?
>
> I agree about making it harder to be close. I am not even sure that
> Escape on items should close a tear off, but it may,
This brings up a simplle question: What are the right keys to
- tear off a posted menu (currently Backspace)
- destroy a tear off menu (currently Escape)
> > Well, to sum it up, I can think of at least three features that
> > do not work well with tear-off menus:
> >
> > - menu animation
> > - continuation menus ("more...")
> > - sub menus
> >
> > I don't see a good solution for either of these, except
> > recommending not to use any of these features with tear-off menus.
>
> Hmm, really, "More..." does not work now in tear-off menus.
> Is it possible to get a decoration height into account when creating
> continuation menus as Dan previously suggested?
No, because (a) the decoration height can not easily be calculated
from within the menu code and (b) the decorations may change at
any time.
> As for menu animation and sub menus I don't see a problem.
It works, but it is confusing.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, email: [EMAIL PROTECTED]
LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen
fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20
--
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]
