🚀 go-pugleaf

BrianW@SoundS.WA.com (Brian Willoughby) writes:

>I posted the answer to this on Sep 14, but it was perhaps obscured among some  
>other answers - here is a short recap:

>After MUCH experimentation under 2.1, I found that -appDidInit: and  
>-setBrowserOutlet: were not reliable places to make the -setCellClass: call.  I  
>subclassed NXBrowser and included the following class method:

>+ initialize
>{
>	[super initialize];
>	[NXBrowserSub setCellClass:[NXBrowserTextFieldCell class]]; // bogus?
>	[self setCellClass:[NXBrowserTextFieldCell class]];
>	return self;
>}

>This code looks redundant, but that is because I never went back to look at it  
>until today.  I guess the old adage: "don't fix it if it ain't broke" applies  
>here.  I would assume that either line would suffice, but I haven't tested  
>anything but what appears above.

Well, it is with deep regret that I inform you that I wasn't able to
get the above to work under 3.0.  It seems to work okay if I do the
setCellClass in initFrame of the NXBrowser.  Are you still using the
above code under 3.0?
Tim

-- 
Tim McClarren     | "...a bajillion brilliant Jobsian lithium licks."
timm@ncsa.uiuc.edu|
(217)244-0015     |