Re: Switching content of NSBox causes strange(?) error msg
Re: Switching content of NSBox causes strange(?) error msg
- Subject: Re: Switching content of NSBox causes strange(?) error msg
- From: "Daniel Käsmayr" <email@hidden>
- Date: Thu, 9 Aug 2001 10:02:11 +0200
- Organization: http://freemail.web.de/
Hi tyler!
Thanx for the explanation, it does make sense to me. Although I dont see why the timer is directly calling a draw method instead of calling a method to check for visibility first...?! could increase performance as well as make things like my posting obsolete :)
Dan
>
Given the error message, and your discovery of the item in
>
question, I'm making a guess, but it seems likely to me that it's
>
something like:
>
>
There is a timer for the pulsing (heartbeat) of the default button.
>
When the timer "fired", the button tried to draw and the first step of
>
drawing is, I believe, locking the focus. The focus was not lockable
>
because the button was no longer IN a window containing a focus
>
mechanism and so an assertion was supplied to let you know that
>
something wasn't as it should be.
>
>
Don't know what the best work around is, but maybe not to worry about it?
>
>
tyler
>
>
>
On Wednesday, August 8, 2001, at 12:43 AM, Daniel Kdsmayr wrote:
>
>
> Hello again...
>
>
>
> after playing around with my NSBox a bit, trying to remove some objects
>
> I finally discovered what was causing the problem: a NSButton that had
>
> the keystroke eq. set tu "return" so it was pulsating. After killing
>
> the key equivalent everything worked as expected.
>
>
>
> Does anyone have an explanation for this behavior?
>
>
>
> Thanx,
>
>
>
> Dan
>
>
>
>
_______________________________________________________________________
1.000.000 DM gewinnen - kostenlos tippen -
http://millionenklick.web.de
email@hidden, 8MB Speicher, Verschluesselung -
http://freemail.web.de