[racket-dev] gtk & too-small menu bar

From: Sam Tobin-Hochstadt (samth at ccs.neu.edu)
Date: Tue May 17 15:16:57 EDT 2011

On Tue, May 17, 2011 at 3:08 PM, Robby Findler
<robby at eecs.northwestern.edu> wrote:
> On Tue, May 17, 2011 at 2:05 PM, Sam Tobin-Hochstadt <samth at ccs.neu.edu> wrote:
>> On Tue, May 17, 2011 at 2:58 PM, Robby Findler
>> <robby at eecs.northwestern.edu> wrote:
>>> On Tue, May 17, 2011 at 1:45 PM, Sam Tobin-Hochstadt <samth at ccs.neu.edu> wrote:
>>>> On Tue, May 17, 2011 at 12:04 PM, Robby Findler
>>>> <robby at eecs.northwestern.edu> wrote:
>>>>> In consultation with Matthew, I've pushed a change that fixes the too
>>>>> small menu bar problem, at least on a VM on my laptop.
>>>>>
>>>>> If you're seeing this problem, can you check and see if the change
>>>>> fixes it for you too?
>>>>>
>>>>> Also, if someone could try it out on a unity setup, that'd be helpful.
>>>>
>>>> This works for me on both my machine running Unity, and my machine
>>>> running Gnome3.
>>>>
>>>> On Unity, there's a black bar where the menu bar would be, since Unity
>>>> puts the menus in the top panel.  I'm not sure what the right way to
>>>> remove that is.
>>>
>>> Wouldn't the right thing be to actually put the menus there instead of
>>> removing that bar? (Or am I misunderstanding something?)
>>
>> No, Unity makes a global design choice that menus go in the top panel
>> (like on a Mac).
>>
>> Here's a screenshot that shows what's going on:
>>  http://www.linuxuser.co.uk/wp-content/uploads/2010/09/Ubuntu-Ubunity-Screenshot-4.png
>
> I understood that.
>
> Oh! Are you saying that there is a space at the top of the window (as
> opposed to the screen)?

Right.

> Did that not used to be there?

Previously, that space had the menus in it, I think.

> Hm. I can see how my change would have
> done that. But given that the original code didn't work, I don't see
> how to fix the problem without an explicit test on whether the menu
> bar is in the window or not. Well, it requires more understanding of
> gtk than I have, anyways.

Oh, the current behavior is a big improvement.  I expect that the
current problem is a lower-level issue with our GTK bindings.  I'll
see if I can come up with a smaller test case.
-- 
sam th
samth at ccs.neu.edu



Posted on the dev mailing list.