Igor, I had a look at Athens demo to understand how to manage sessions and surfaces because Roassal uses AthensSurface and there is a defensive mechanism in place in Roassal to initialize the surface in case it is not done. In the meantime, I have discovered that the red rectangle bug is present in Athens demos as well.
So, to reproduce. AthensFlakeDemo new openInWorld save image open image I tested in Moose 5.0. 1. Should I open a bug entry in Pharo? 2. With my superficial knowledge of Athens, my guess is that the session management can be done in Athens so that Roassal (and other tools built on top of Athens) do not need to do it. May be it is the case already but the demos are not using it then. Usman On Mon, Dec 2, 2013 at 5:14 PM, Usman Bhatti <[email protected]> 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. > > 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? > > regards, > > Usman >
