gnustep-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Last change in NSMenuView.m


From: Gregory Casamento
Subject: Re: Last change in NSMenuView.m
Date: Mon, 17 Jan 2011 14:08:11 -0500

I'm also not entirely certain how going into that code when the [[[NSApp mainWindow] menu] attachedMenu] method returns nil helps us in the first place.

GC

On Jan 17, 2011, at 1:25 PM, Germán Arias wrote:

Maybe:

&& ![[self menu] isTransient]

is better. But even with this, and independently of the menu style,
there are some problems with the transient menu at appicon. Seems like
don't track correctly the mouse.

On lun, 2011-01-17 at 10:20 -0500, Gregory Casamento wrote:
The issue I was trying to correct was that pull down menus were not
working with the previous code.

I will test the situation you describe below as well.

GC

On Monday, January 17, 2011, Germán Arias <address@hidden> wrote:
Hi Greg.

The addition at lines 1660 and 1661 in NSMenuView.m:

&& anAttachedMenu != nil

added an odd behavior at menu in window. This is because if you move the
mouse outside a submenu, the horizontal menu retrieves the mouse
tracking. But if the mouse is outside this too, the submenu is closed.
Then in next loop,there isn't an attached menu, and the code to handle
the menu in window is not executed, and variable "space" never arrive to
2. Then we can't break the loop. We need add 1 to variable "space" even
when there isn't an attached menu. Or I think so, I will test this
tomorrow.


_______________________________________________
Gnustep-dev mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/gnustep-dev




_______________________________________________
Gnustep-dev mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Gregory Casamento - GNUstep Lead/Principal Consultant, OLC, Inc.
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]