Btw, we should establish a policy:
if we extending a UI manager protocol,
do it in UIManager first
and then in all its subclasses.
Because all UI managers should have same protocol.
On 26 May 2011 15:02, Igor Stasenko <
[hidden email]> wrote:
> On 26 May 2011 13:53, Marcus Denker <
[hidden email]> wrote:
>>
>> On May 26, 2011, at 1:51 PM, Igor Stasenko wrote:
>>
>>> Marcus, could you tell what code are loaded in it?
>>> I could try to figure out why it fails.
>>> Because we need to fix all points, like that.
>>>
>>
>>
>> The problematic issue is this:
>>
>>
http://code.google.com/p/pharo/issues/detail?id=1817>>
>> I added it in 13215, and then did another 13215 without it.
>> Stef then build 13216 on top of the faulty one.
>>
>
> I think the problem was that
> UIManager default uiProcess
> leads to error
> if ui manager is non-interactive, not morphic one.
>
> It may lead to infinite loop, if error handling also attempts to use
> UIManager default uiProcess
>
>
>> Marcus
>>
>> --
>> Marcus Denker --
http://www.marcusdenker.de>> INRIA Lille -- Nord Europe. Team RMoD.
>>
>>
>
>
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>
--
Best regards,
Igor Stasenko AKA sig.
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Locked
