SYSTEM WARNING: Creating default object from empty value

SYSTEM WARNING: Creating default object from empty value

Mantis - Squeak
Viewing Issue Advanced Details
1272 Browser major always 05-26-05 21:55 02-07-07 06:42
new 3.8  
0001272: HierarchyBrowser>setClass:selector: is broken
HIerarchyBrowser inherits setClass:selector: from Browser. Since this method strongly assumes that the class list view is of a class category, we are bound for trouble. The chances of the hierarchy exactly matching the category are slim to none.

The root of the problem is redefining a class in a HB; most of the code invoked as a result is inherited from B and just makes bad assumptions. See Browser>defineClass:notifying: etc.

At best you get the wrong class being selected in your HB, at worst you get notifier about a problem unrelated to the class change you made. Very confusing.
Does it make sense for a hierarchy browser to dispaly the class category view?
3.8-6662 image.
Debug log attached, though not very helpful
parent of 0001302new  HierarchyBrowser class hierarchy view does not update when new class added 
parent of 0005631new  Saving a class definition in the hierarchy browser causes a walkback 
Not all the children of this issue are yet resolved or closed.
 SqueakDebug.log [^] (4,413 bytes) 05-26-05 21:55
 HierarchyBrowser.RJT.2.cs.gz [^] (610 bytes) 10-14-05 03:28
 HBclassListDebugLog.log [^] (3,411 bytes) 02-07-07 06:34

10-14-05 02:02   
I have a fix for this bug, I ran into it myself.
I reimplemented the method

HierarchyBrowser>> buildSystemCategoryBrowserEditString

and added the initialization so the Hierarchy browser would have it's class list.

This fixed the problem of selecting Browse from the category pane on a Heirarchy Browser. -Ron
10-14-05 03:28   
That change sucked. I didn't like the results. I makes no sense to browse a category and end up in a hierarchyBrowser, there is no guarantee all the classes in a category will have the same Hierarchy. I changed it so that it opens a regular browser instead and acts consistantly with other category browsers for other areas. (besides I uploaded the wrong patch file!!)
02-07-07 06:42   
Another DebugLog datum. From sq7067.

When browsing some parts of the heirarchy the confusion seriously hinder work.

It would be nice to find a way to separate the hierarchy index from the
catagory index browser uses. The problem is the sheer size of the two classes. And the total confusion between classList in the two.

When does the hierarchy browser mean one thing and when the other when it uses the same messages as browser?