Anonymous | Login | 03-02-2021 02:10 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
0001272 | [Squeak] Browser | major | always | 05-26-05 21:55 | 02-07-07 06:42 | |||||||
Reporter | tim | View Status | public | |||||||||
Assigned To | ||||||||||||
Priority | normal | Resolution | open | |||||||||
Status | new | Product Version | 3.8 | |||||||||
Summary | 0001272: HierarchyBrowser>setClass:selector: is broken | |||||||||||
Description |
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. |
|||||||||||
Additional Information |
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 |
|||||||||||
Attached Files |
![]() ![]() ![]() |
|||||||||||
|
![]() |
||||||||||||||||
SYSTEM WARNING: Creating default object from empty value SYSTEM WARNING: Creating default object from empty value
|
Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
61 total queries executed. 37 unique queries executed. |