🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.next.programmer
Article #1340

Re: NXBrowser problem...

#1340
From: Brian Willoughby
Date: Thu, 08 Oct 1992 03:27
45 lines
2733 bytes
Sharon Zakhour writes
| [...much...]

Thank you. Thank you. Thank you.
NeXT has been silent for too long, especially about the NXBrowser class.  I  
really appreciate the communication that several folks at NeXT have been taking  
the time for.

| I'm sorry to hear that you find NeXTanswers "nearly useless".  We write these  
| in our spare time and it's disappointing to hear that they are not being well  
| received.  We try to police them for accuracy and content but sometimes  
| errors do creep in.  We are interested in keeping them as accurate and up to  
| date as possible and we hope that when you find errors or inconsistencies  
| that you will send them to nextanswers@next.com.  Help us to help the.
| community.

Well, I did send in about 15 or 20 bugs to NeXT, and read many questions from  
people also having trouble with NXBrowser.  It didn't seem like NeXT was  
supporting their browser at the time, but now I am happy to see that trend take  
an about-face.  Now that the "community" is growing, I'm glad to see a high  
level of interaction from NeXT employees.

| The information I gave above for the 3.0 case is also true in the 2.x case  
| although there were a couple of bugs that complicated matters.  For example,  
| under 2.x no matter WHERE you called -setCellClass: for NXBrowser, you always  
| needed to call loadColumnZero (unless you didn't care if the first column  
| used the default cell).  Also, this approach didn't work at all if you set  
| reuseColumns:YES on the browser -- this would crash the application.  These  
| bugs have all been cleaned up for 3.0.

By the way, I was calling -reuseColumns:YES for EVERY browser that I created.   
No wonder I initially had so many crashes.  In fact, it wasn't even the browser  
code that was crashing, it was a totally unrelated part of my code that was  
experiencing corrupted instance variables.  I eventually found a magic  
combination that was crash-proof.

I suppose this will all be moot as soon as I attempt to recompile the  
program...

| Sharon Zakhour
| Developer Support 
-- 
Brian Willoughby	Software Design Engineer, BSEE NCSU
BrianW@SoundS.WA.com	Sound Signal Processing Software and Consulting
NeXTmail welcome	- NO EMAIL SOLICITATION without prior permission
Technical Details
Message-ID: <Bvs9LG.Is@sounds.wa.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!nwnexus!sounds!brianw
References: <5332@rosie.NeXT.COM>

Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.programmer
Path: arc1-ca.pugleaf.net!sparky!uunet!nwnexus!sounds!brianw
From: BrianW@SoundS.WA.com (Brian Willoughby)
Subject: Re: NXBrowser problem...
Message-ID: <Bvs9LG.Is@sounds.wa.com>
Sender: brianw@sounds.wa.com (Brian Willoughby)
Reply-To: BrianW@SoundS.WA.com
Organization: SoundSoftware, Bellevue, WA, USA
References: <5332@rosie.NeXT.COM>
Date: Thu, 8 Oct 1992 03:27:15 GMT
Lines: 45