<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="#954F72" style="word-wrap:break-word"> <div class="WordSection1"> Hi Juan, <o:p> </o:p> I’ve stumbled upon this irregularity: <o:p> </o:p> If you run this in the Workspace… <o:p> </o:p> [Smalltalk installLowSpaceWatcher] fork. [Smalltalk installLowSpaceWatcher] fork <o:p> </o:p> … the system ends up with two processes running the #lowSpaceWatcher method; the root cause is #installLowSpaceWatcher runs unprotected against multiple concurrent invocations. <o:p> </o:p> I’d suggest running the # installLowSpaceWatcher’s code as the Semaphore >> #critical section: see attached changeset with a more detailed description in the method comment. Please feel free to modify in any way :) <o:p> </o:p> Thanks for your opinion, Jaromir <o:p> </o:p> -- Jaromír Matas<o:p></o:p> mail@jaromir.net <o:p> </o:p> <div style="mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: <a href="mailto:cuis-dev@lists.cuis.st">Jaromir Matas via Cuis-dev</a> Sent: Wednesday, July 6, 2022 9:29 To: <a href="mailto:JuanVuletich@zoho.com">Juan Vuletich</a>; <a href="mailto:cuis-dev@lists.cuis.st"> Discussion of Cuis Smalltalk</a> Cc: <a href="mailto:mail@jaromir.net">Jaromir Matas</a> Subject: Re: [Cuis-dev] FW: FW: Freezing UI - can't interrupt via Alt+. </div> <o:p> </o:p> Hi Juan,<o:p></o:p> <o:p> </o:p> > It is nice to use Smalltalk as it is meant to be used: a place to experiment, learn and build, and share as we do it.<o:p></o:p> <o:p> </o:p> Exactly; Smalltalk is such a wonderful tool for that! Is there any other language / system providing so much flexibility at all? Before Smalltalk I tried Python but gave up, no fun (for me; no offence!) ;D<o:p></o:p> <o:p> </o:p> > Doing it as a bunch is much better than by oneself!<o:p></o:p> <o:p> </o:p> So valuable! Feedback, motivation, new angles, fun... thanks to all!<o:p></o:p> <o:p> </o:p> > I think the logic to pick which process to interrupt may still be improved, we need to figure out how.<o:p></o:p> <o:p> </o:p> This is an interesting note; I'll have to think about it :)<o:p></o:p> <o:p> </o:p> Many thanks for all your answers and help.<o:p></o:p> <o:p> </o:p> Best,<o:p></o:p> Jaromir<o:p></o:p> <o:p> </o:p> -- Jaromír Matas<o:p></o:p> mail@jaromir.net <o:p> </o:p> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> From: <a href="mailto:JuanVuletich@zoho.com">Juan Vuletich</a> Sent: Tuesday, July 5, 2022 15:28 To: <a href="mailto:cuis-dev@lists.cuis.st">Discussion of Cuis Smalltalk</a> Cc: <a href="mailto:mail@jaromir.net">Jaromir Matas</a> Subject: Re: [Cuis-dev] FW: FW: Freezing UI - can't interrupt via Alt+.<o:p></o:p> </div> <o:p> </o:p> Hi Jaromir, On 7/5/2022 7:41 AM, Jaromir Matas via Cuis-dev wrote: <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> Hi Juan,<o:p></o:p> <o:p></o:p> Thank you very much; I learn a lot from your feedback.<o:p></o:p> </blockquote> Thank you too. I'm also learning from these exercises. It is nice to use Smalltalk as it is meant to be used: a place to experiment, learn and build, and share as we do it. Doing it as a bunch is much better than by oneself! <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> Question: Did you leave your previous update #5347 off from #newProcessIfUI: intentionally or by mistake? The example in the comment now blocks the UI... I'm attaching a simplified version of the previous proposal just in case... <o:p></o:p> </blockquote> My intention was to remove the call to #terminate, as it is now superfluous thanks to your better #mainLoop. I also removed the call to #newUIProcessIfNeeded by mistake. I kind of integrated your change, adding it back. <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> but frankly, I barely know what I'm doing... it's so interrelated and I can't foresee possible impact of even a small change, sorry if I missed something.<o:p></o:p> </blockquote> Since you have started contributing to Cuis, you pushed me a little beyond my comfort zone each time. It is easy to miss some detail! We go, step by step, carefully. As we go, Cuis keeps improving and we keep learning. Thanks for that. <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <o:p></o:p> One more question: in your previous update #5346 you changed the return value from UIProcess to oldUIProcess: I can't figure out why... in case you have a spare minute :)<o:p></o:p> </blockquote> The old ui process can be taken "as the one the user tried to interrupt with cmd + .". Answering the new UIProcess was a mistake. In the update I just pushed I added comments and renamed variables in the involved methods, trying to make all this clearer. I think the logic to pick which process to interrupt may still be improved, we need to figure out how. <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <o:p></o:p> > [...] it is no longer possible to have 2 different worlds running in different processes. <o:p></o:p> > Well the UIProcess class variable already precludes this. When we work on enabling multiple worlds, each with its own running process, we'll see.<o:p></o:p> <o:p></o:p> yes, that's what I thought... no harm done at the moment; later, each world might need to have it's own "UIProcess" variable.<o:p></o:p> </blockquote> Exactly! <o:p></o:p> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> Thanks again,<o:p></o:p> best,<o:p></o:p> Jaromir<o:p></o:p> <o:p></o:p> <o:p> </o:p> </blockquote> Cheers,<o:p></o:p> <pre>-- </pre> <pre>Juan Vuletich</pre> <pre><a href="http://www.cuis-smalltalk.org">www.cuis-smalltalk.org</a></pre> <pre><a href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev</a></pre> <pre><a href="https://github.com/jvuletich">https://github.com/jvuletich</a></pre> <pre><a href="https://www.linkedin.com/in/juan-vuletich-75611b3">https://www.linkedin.com/in/juan-vuletich-75611b3</a></pre> <pre><a href="https://independent.academia.edu/JuanVuletich">https://independent.academia.edu/JuanVuletich</a></pre> <pre><a href="https://www.researchgate.net/profile/Juan-Vuletich">https://www.researchgate.net/profile/Juan-Vuletich</a></pre> <pre><a href="https://patents.justia.com/inventor/juan-manuel-vuletich">https://patents.justia.com/inventor/juan-manuel-vuletich</a></pre> <pre><a href="https://twitter.com/JuanVuletich">https://twitter.com/JuanVuletich</a></pre> <o:p> </o:p> <o:p> </o:p> </div> </body> </html>