Re: A simple question about nsthread
Re: A simple question about nsthread
- Subject: Re: A simple question about nsthread
- From: j o a r <email@hidden>
- Date: Thu, 1 Dec 2005 10:57:27 +0100
Andrea: It's bad form to take off-list replies back to the list! Not
that it matters much in this case though.
On 1 dec 2005, at 10.48, Andrea Salomoni wrote:
You're wrong - every single Cocoa class is named with a capital
letter. Three actually: "NSSomeClass".
And it will help you fix the thread problem, because it will help
us help you more efficiently.
Yes understand.... thank you for tip but you mean I have to name my
classes in this way too?
Yes certainly - read the Cocoa / ObjC naming guidelines.
The outlet is probably populated when you load the corresponding
nib file, and I can't see from your code snippet that you ever do
that?
In the header file of myClass I have:
IBOutlet NSTextField * myTextField;
I though this should be enough... but maybe I wrong
Declaring a variable, and populating the variable, are two completely
different things.
I think that the simple answer to that question is "yes". That
said, the thread is not "inside another class". You should
probably try to find some documentation to help you improve your
understanding of threads vs. objects.
Yes I did and all documentation says to use [receiver
perormSelectorOnMainThread: method .
In another app I made i did the same and works fine, but this
method is in the controller class and the outlet exist.
I cannot find another documentation about it, because all the
documentations tell me the same: use performSelectorOnMainThread:
What I think you need is not the documentation on these particular
methods, but rather a more basic conceptual documentation on what a
thread is, and how it relates to the data it operates on.
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden