Revisiting NSTextView bugs in Interface Builder (rant about BugRe porter)
Revisiting NSTextView bugs in Interface Builder (rant about BugRe porter)
- Subject: Revisiting NSTextView bugs in Interface Builder (rant about BugRe porter)
- From: Jeff Laing <email@hidden>
- Date: Tue, 11 Jan 2005 11:01:01 +1100
A while back, I reported that i was having problems with Interface Builder
crashing if I tried to use custom NSTextView subclasses which had
pre-defined text.
Few people here managed to reproduce the problem.
Well, I reported it on bugreporter like a good little drone, and today (back
from holidays) I took a look to see what the status was.
Problem ID: 3900619
State: Closed/Duplicate
Thats it? Thats all I get? Not even a single line of explanation?
And when I click on the State (Definition) link to see if they give me any
further information, it describes exactly two states.
Open/Analyze
Open/Verify
so I have no idea whether Closed/Duplicate means that its closed because
a) it is a bug
b) its not a bug
but the nett result is that it feels like
c) go away, we don't care
No wonder people don't bother reporting things to Apple when thats the
feedback they get.
To the Apple staff who lurk here, and from time to time recommend that
people ensure they use BugReporter, perhaps you need to check that Apple
really want people to use it.
Obviously I'm ranting and perhaps others have more success with BugReporter
feedback than this. But seriously, we have this sort of defect tracking
system here as well and I'd have my ass handed to me on a platter by my boss
if I included this little in a defect response that was going to be seen by
a customer.
_______________________________________________
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