Still trying to figure my fault...
Still trying to figure my fault...
- Subject: Still trying to figure my fault...
- From: Graham Wihlidal <email@hidden>
- Date: Fri, 3 Aug 2001 15:42:52 -0600
Hey list, sorry again for junking this list.
I have one class file I called Controller. I basically has all the code
for this app of mine in it. I have declared a variable in the header:
IBOutlet NSTextField *connectWindowMessage;
Upon startup, a login window is displayed where you enter your username
and password. You do so and it brings up a window called
connectWindow. It then calls setStringValue on the
connectWindowMessage variable to say "Connecting" and then it attempts
to connect a CFSocket. When it connects successfully it changed that
message text to "Sending Details" and then sends a command across the
socket. When it receives the reply, it is SUPPOSED to change the
message text to "Connected" but it never does! As if it is sending to a
nil object. The thing that gets me is, the variable is fine in the
first function which calls it, but it my socketDataAvailable callback
for the CFSocket, it is like that variable was nulled? Both functions
that setStringValue on that variable are in the same class. What is
going on? Forgive my ignorance, but a simple solution would be to
somehow reconnect the address of this variable to the NSTextField in the
IB Nib. How do you do that in Obj-C\Cocoa? I don't think you WOULD
need to. IB should make this variable always available unless you
forcefully free it right?
Thanks in advance,
Graham Wihlidal