The messages listed in the issue (Browser >> addSystemCategory, PluggableThemedPanelMorph >> duplicateClassWithNewName: aSymbol) have not been modified to handle the nil case on cancel.
I'm not sure what in this update addresses them. They do showcase yet a few more cases where you do NOT want to handle nil and empty differently though. :) Cheers, Henry On Oct 7, 2009, at 12:18 49PM, Stéphane Ducasse wrote: > > 10469 > ----- > - Issue 1235: UIManager #request:initialAnswer: returns nil on Cancel > instead of empty string > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
