Yes I asked damien if it could produce a slice with all the code
because I could not easily see the conflict.
What I merged what another related issue 925 or 955 from memory. and
we have to integrate the pendings
items from 1235 (which should still be open).
Stef
On Oct 7, 2009, at 2:27 PM, Henrik Johansen wrote:
> 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
>>
[hidden email]
>>
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project>>
>
>
> _______________________________________________
> Pharo-project mailing list
>
[hidden email]
>
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Locked
