[Pharo-dev] Roassal Bug related to Athens?

Igor Stasenko siguctua at gmail.com
Mon Dec 2 16:12:21 EST 2013


http://code.google.com/p/nativeboost/wiki/SessionManagement


On 2 December 2013 22:02, Igor Stasenko <siguctua at gmail.com> wrote:

>
>
>
> On 2 December 2013 17:14, Usman Bhatti <usman.bhatti at gmail.com> wrote:
>
>> Hello Igor,
>>
>> Moose 5.0 is using Athens as default canvas for Roassal and we have bug
>> with Roassal that seems to be related to Athens.
>> http://code.google.com/p/moose-technology/issues/detail?id=1019
>>
>> I think it is related to the fact that we create a surface in the OS with
>> Athens and once we quit the image, the surface is destroyed as well. So,
>> when image is restarted with the visualization trying to use the surface,
>> we get the error.
>>
>> right.
>
>
>> Could you point to what possibly can be done to avoid this error? Merely
>> checking the existence of an appropriate drawing surface in Athens every
>> time visualization is drawn, would it suffice?
>>
>> yes.. i explained and given examples multiple times both for NB and
> Athens (and last time it was like couple weeks ago).
>
>  http://lmgtfy.com/?q=nativeboost+session+aware&l=1
>
> regards,
>>
>> Usman
>>
>
>
>
> --
> Best regards,
> Igor Stasenko.
>



-- 
Best regards,
Igor Stasenko.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131202/453dc6b8/attachment-0002.html>


More information about the Pharo-dev mailing list