<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">I’m new to the Cuis implementation of Smalltalk.</div><div class="">I’ve dabbled with Squeak and Pharo in the past … and then life would strike and distract me from it. :-)</div><div class=""><br class=""></div><div class="">Now, I’m playing with Cuis — and I really like the minimalist approach.</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">System: MacBook Pro 16” (2019)</div><div class="">OS: macOS Catalina (10.15.7)</div><div class="">Cuis image: Cuis5.0-4963.image</div></blockquote><div class=""><br class=""></div><div class="">I’ve been working my way through “The Cuis” book (<a href="https://cuis-smalltalk.github.io/TheCuisBook/" class="">https://cuis-smalltalk.github.io/TheCuisBook/</a>), learning lots.</div><div class=""><br class=""></div><div class="">It’s all been running quite stable until today and have run into two issues.</div><div class=""><br class=""></div><div class="">(I did DuckDuckGo around to find similar issues, but I didn’t find any. If these are noted somewhere, please point me to them. Thanks! 🙂)</div><div class=""><br class=""></div><div class="">ISSUE #1</div><div class=""><br class=""></div><div class="">I got to the clock morph chapter (<a href="https://cuis-smalltalk.github.io/TheCuisBook/A-Clock-Morph.html" class="">https://cuis-smalltalk.github.io/TheCuisBook/A-Clock-Morph.html</a>) and got the clock running.</div><div class=""><br class=""></div><div class="">Then, I started playing with the #stepTime values — just for fun. I set it to values like “16” and “66.7” and then, suddenly, the whole environment froze.</div><div class=""><br class=""></div><div class="">The Squeak menu still responded, but it wouldn’t allow me to quit.</div><div class=""><br class=""></div><div class="">I sent it a USR1 signal, and it generated a crash dump, here: <a href="https://www.dropbox.com/s/1e4st9fp8xrm29p/crash-01.dmp?dl=0" class="">https://www.dropbox.com/s/1e4st9fp8xrm29p/crash-01.dmp?dl=0</a></div><div class=""><br class=""></div><div class="">Is this a known issue? I realize a step time of 16ms (or possibly even 67.7ms) is pretty short, but I didn’t expect it to freeze everything.</div><div class="">(Sadly, I hadn’t saved the image, so I lost all the samples I’d added. :-( )</div><div class=""><br class=""></div><div class="">ISSUE #2</div><div class="">After restarting Cuis, I re-added the LineExampleMorph (section 7.1.1 - <a href="https://cuis-smalltalk.github.io/TheCuisBook/Going-Vector.html" class="">https://cuis-smalltalk.github.io/TheCuisBook/Going-Vector.html</a>)</div><div class="">And instantiated it.</div><div class="">It drew a green line.</div><div class=""><br class=""></div><div class="">Then, I went to the class definition and changed its superclass from Morph to MovableMorph and saved.</div><div class=""><br class=""></div><div class="">Everything seems fine … but, when I clicked on the existing green line, the debugger popped up</div><div class=""><br class=""></div><div class="">So, I closed the debug window and went to the Workspace window and executed “LineExampleMorph allInstancesDo: [:x | x delete. ]”</div><div class="">The green line disappears, but a debug window popped up.</div><div class="">So, I changed the class back to “Morph” … and then a “Recompiling” dialog popped up … and stayed there.</div><div class="">Then debug windows started popping all over — to the point where the whole display is unusable.</div><div class=""><br class=""></div><div class="">It looks like it may have generated a log file for each debug message (there are 16 of them … 😉)</div><div class=""><br class=""></div><div class="">Here’s a screen recording (.mov file) of what it looked like:<a href="https://www.dropbox.com/s/ja6hynzfpka5jua/Cuis-Smalltalk-Issue02.mov?dl=0" class="">https://www.dropbox.com/s/ja6hynzfpka5jua/Cuis-Smalltalk-Issue02.mov?dl=0</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">I guess my overall questions are:</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Should these kinds of things be happening?</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Or are these somehow n00b errors on my part?</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>How can I ensure data is lost as I experiment with the environment?</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Since the whole philosophy of Smalltalk is to be able to examine the whole system and try things, I’d like to do that without worrying that the next thing I do could blow up the environment. 😉</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>These don’t seem like things that should freeze the environment.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Thanks, in advance, for any insights you might have.</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>— Mark</div></body></html>