Are you sure that the NSTimer is the issue? Make sure you compile
with all optimisations turned off while you are still developing.
Otherwise the debugger won't be able to tell what part of the code is
executed and returns garbage.
Gruss,
Daniel
On 08.02.2007, at 15:25, Ludwig Villiger wrote:
I found out, that when the Timer is not initiated before I check,
the log says correctly, that the timer is not valid. But when the
timer is initiated and then invalidated, the log says: -
[NSCFDictionary isValid]: selector not recognized [self = 0x3f02d0]
It seems, that something is messed up, because NSTimer* volTimer is
not a NSDictionary object. Sometimes the Log says also
NSAppleScript or NSEvent instead of NSDictionary. That's crazy!
What's wrong here?
Ludwig
Am 08.02.2007 um 09:42 schrieb Ludwig Villiger:
I am checking with - isValid if the NSTimer is active. When he is
active then - isValid returns 1, but when the timer is inactive it
produces a crash.
timi=[volTimer isValid];
In the log I see, that it stops at this line of code above, when
the Timer is not active.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Student-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Student-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40student.ethz.ch
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Student-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
