🚀 go-pugleaf

In article <1992Oct02.163647.20446@infko.uucp> benz@infko.uni-koblenz.de  
(Hartmut Benz) writes:
> Hi you gurus out there!
> 
> I'm absolutely new to NeXT-programming so this question might be really  
> stupid, but ...
> 
> I have a small application running under 2.1 with a Form inside a Window  
like
> 
> 		Field 1 [        ]
> 		Field 2 [        ]
> 
> I have a connection 'fields' to this form and used to set values like  
this:
> 
> 		[fileds setIntValue:someValue at:1];
> 
> and everything worked fine until THE UPRGRADE TO 3.0!
> After that (and the rebuilding of the application of course) nothing  
happens  
> with this fields. Also the documentation on Form tells me not to use  
this  
> method on it?
> 
> Two Questions:
> 1.	How do I do it?
> 2.	Why has this been changed?
> 
Well, in answer to your first question, it still works for me. I have a  
form called myForm. Create a controller that messages the form with a 
	
		[myForm setIntValue:someValue at:0]

Link a button to the controller. Compile. Click the button, and field 0  
takes the intValue from someValue. Seems to work all right.

As for the second question, if it still works, why not use it? All i can  
find in the documentation is a line in the setIntValue:at: method that  
says

"Form does not override Control's setIntValue: method;  your code should  
never use that method with a Form."




--
Adrian Smith
University of Alberta NeXT Campus Consultant
adrian@niagara.ucs.ualberta.ca
Audix: 5482