You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we open a space (example figure 1), then save and leave our Pharo image, this creates a problem. When you want to re-open the image, it either opens a few microseconds before closing or it does not open at all. Very rarely, it can open, with a debugge window (figure 2). The Pharo image then works (more or less) correctly. The problem reappears with each new launch of this image.
You should either block the fact of being able to save if a space is open, to close the space automatically at the backup or at least know (via a debugge window) why the image does not launch, and how to fix it.
If the error ever occurs, a single way from the image (once it has launched) to fix it is to click in the header bar on Library/Toplo/Cleanup Universe
Firgure1 :
Firgure2 :
The text was updated successfully, but these errors were encountered:
When we open a space (example figure 1), then save and leave our Pharo image, this creates a problem. When you want to re-open the image, it either opens a few microseconds before closing or it does not open at all. Very rarely, it can open, with a debugge window (figure 2). The Pharo image then works (more or less) correctly. The problem reappears with each new launch of this image.
You should either block the fact of being able to save if a space is open, to close the space automatically at the backup or at least know (via a debugge window) why the image does not launch, and how to fix it.
If the error ever occurs, a single way from the image (once it has launched) to fix it is to click in the header bar on Library/Toplo/Cleanup Universe
Firgure1 :
Firgure2 :
The text was updated successfully, but these errors were encountered: