(no subject)
(no subject)
- Subject: (no subject)
- From: Paul Fox <email@hidden>
- Date: Mon, 12 Aug 2002 10:47:55 +0100
To: email@hidden
Subject: Re: Missing mouseUp events
X-Mailer: Created by CRiSP-Mail v6.3 (CRiSP v8.0.7a)
Date: Mon, 12 Aug 2002 10:25:29 +0000
Following up myself...
>
I'm playing with makeFirstResponder and seem to have a problem.
>
>
I am implementing something very similar to MS Windows MDI windows
>
(dont shriek in horror - they are optional). Each MDI window is
>
essentially a hiererachy of NSView's. When you click on the title
>
bar of the MDI window it needs to forward focus to the appropriate
>
embedded child NSView in that tree.
>
>
I use makeFirstResponder for this purpose.
>
>
WHat I am finding is that when I do this mouseDown on the title
>
and try to set the focus, I never receive mouseUp events.
>
>
Even if I comment out the calls to makeFirstResponder I am failing
>
to get the mouseUp event - which is puzzling. It works fine when I have
>
a single MDI window but as soon as I go to two of them it works
>
bizarrely. More than likely a silly simple error in my code - but I am at
>
a loss to where the mouseUp is going. I have printf()'s in pretty
>
much all the important NSView callback methods - but cannot track it down.
>
>
Any suggestions as to how to find out what might be going on?
>
>
thanx
Hm. Found my problem. I implement the X11 function XRaiseWindow to make
the clicked window the top of the visible window order. So far
the only way to implement this I have found is:
[w removeFromSuperviewWithoutNeedingDisplay];
[s addSubview: w];
Is there any other way to make a NSView top of the visible stack?
Temporarily removing the view from the parent causes the subsequent
mouseUp event to be lost which is a little bit criminal and sad.
thanx
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.