Re: Terminal matrices

[Gerd Möllmann]

martin rudalics <rudalics@gmx.at> writes:

>>> Neither did I.  The first thing we would have to do is to mold the menu
>>> bar according to the buffer displayed in the child frame.  The attached
>>> patch does that.  The next problem is that a click on a menu bar item
>>> must _not_ select that item's frame but keep the child frame selected.
>>> This looks like the harder part because I have no idea where to do it -
>>> I'm afraid it's toolkit dependent.
>
> I now tried again with the GUI behavior and think that there's nothing
> we should change:
>
> - Clicking with the mouse on the menu bar of the root of a child frame
>   should operate on the root frame - this was the behavior ever since
>   and I don't think we want to change it.
>
> - If users want to operate on the proper "menu bar" of the child frame,
>   they should use the F10 key which pops up the menu bar items in a
>   special menu operating on the child frame.  Nothing to change either
>   but for the fact that the Help menu appears first.

Okay.

> The behavior on tty frames OTOH should be changed.  When a child frame
> is selected and has no menu bar, invoking the menu bar of the root
> should show the corresponding menu in the root frame and only have a
> key's binding operate on the child frame.  Currently, a user gets the
> tmm-menubar in the child frame which is however presumed to operate in
> normal sized tty-frames and is completely unsuitable for smaller frames.
>
> I attached a few changes to 'popup-menu' and 'menu-bar-open' which have
> the menu bar popups happen in the root frame while the command execution
> proper is done again in the child window.  Please have a look.

I tried it and it works well for me, but with one subtlety: I have a
child frame open and open the Tools menu. I move the mouse over the menu
items. When I move the mouse to menu items "under" which is the child
frame, they don't get highlighted.

I made me a todo item for that.

>
> There are two issues I currently don't understand yet: One is that my
> nextstep builds don't make child frames correctly on a GUI any more - I
> could bet this worked earlier.  Unfortunately, my earlier ns-builds
> currently fail with
>
> libgnustep-gui.so.0.27: cannot open shared object file: No such file or 
> directory
>
> so I can't verify that claim any more.  I'm not yet sure whether I
> should re-install the old libraries and possibly deleted the newer
> ones.

Works with current master on macOS for me, with and without your patch.
Should I look for something specific not working?

> The other issue is that on my Xfce terminal F10 activates the terminal's
> menu bar which is probably not what the user wants.  But that behavior
> might be hardcoded and some different key binding would be needed
> instead.  On terminals without built-in menu bars this is obviously not
> an issue.

Can't say something valuable to that, I'm afraid.

Looking forward to your patch appearing on master! Thanks!