search

feenkcom / gtoolkit

Glamorous Toolkit is the Moldable Development environment. It empowers you to make systems explainable through experiences tailored for each problem.
https://gtoolkit.com
MIT License
1.1k stars 47 forks source link

Morphic world became unresponsive #1917

Closed offray closed 3 years ago

offray commented 3 years ago
Version OS
0.8.6.47 Manjaro

While I'm learning GToolkit, I'm using Morphic world for code refactoring, repositories management and other tasks. And while working in Morphic world it became unresponsive. I can not save any method or move any window on it. Also, despite I can move on GToolkit tabs, including Coder and Playgrounds, but I can not save new methods there and trying to execute previously working code gets the message "Redering..." and nothing happens. Frozen Morphic world and nonfunctional Glamorous Toolkit look like in the following screenshot (several unresponsive UI places have been underlined):

image

I will update to last published version and hope that this pretty serious bug is not there, as I can not commit new code to the repositories when this happens and I wonder how much work I lost (I'm kind of afraid of loosing it again).

girba commented 3 years ago

The Morphic World does not usually freeze. Do you know what specifically you did to make it so? Is it possible that the reason is an infinite loop in the asTiddler method?

offray commented 3 years ago

Wow! I just updated to the last version and Lepiter seems intriguing and awesome. Exploring it.

girba commented 3 years ago

Actually, as the Raw view seems to be frozen, it can also be that there is some infinite loop in the printing of some of the state. But, maybe something else is the problem. It would be useful to watch out if it happens again.

offray commented 3 years ago

The Morphic World does not usually freeze. Do you know what specifically you did to make it so? Is it possible that the reason is an infinite loop in the asTiddler method?

There is no infinite loop in asTiddler. I will upload the package again from its last commit and try to see where the bug happened. Thanks.

girba commented 3 years ago

Ok. I will close the issue in the meantime. Please reopen if it occurs again.