[Cuis-dev] FW: FW: FW: Freezing UI - can't interrupt via Alt+.

[Jaromir Matas]

Hi Juan,

Gosh, this is amazing! I couldn't wait to see :)

I ran out of mean examples :D

One observation though: Sometimes, although rarely and irregularly, this happens:

I run an example (in the Workspace), e.g. this one:

[1/0] fork.
5 seconds asDelay wait.
self error: 'error'

and then I move the first debugger window and close it before the 5 second delay expires and when the second debugger opens I get an MNU error concerning drawing - I'm enclosing a snip (if I knew how to file out the debugger's stack contents I'd send it too). And the next time you run the same example it may happen again or may not... Can't figure out any pattern except you have to move the first debugger window before closing it.

--
One stupid question: How do you make the image download the latest changes you made at github? I thought this would work: World menu -> changes -> install new updates but it doesn't... Now I think it's maybe not supposed to download from github but just locally from the CoreUpdates folder... Is that so?

What I do now (sorry if it sounds too stupid) is I download a new image which contains the latest changes in the CoreUpdates folder already...

The thing is I'm on Windows and don't do any git stuff or any command line stuff ;) Is there a way for users like me to update easily?

--
Well, actually, what would think about situations like this:

[1/0] fork.
[ 10000 factorial. Processor yield ] repeat

would you expect, or consider reasonable to expect, the UI to process the 1/0 exception during the long computation?

I'd tend to say no but then when I look at this example:

[1/0] fork.
[ 10000 factorial. 5 seconds asDelay wait ] repeat

I'm not so sure... The delay blocks the UI and a thus a new UI is created etc. while in the former case yield just allows other processes of the same priority to run etc… which are implementation details…

And if you run the former example forked:

[[1/0] fork.
[ 10000 factorial. Processor yield ] repeat] fork

You won’t be surprised the 1/0 exception is executed immediately after the first yield. Which leads me closer to expecting the 1/0 exception appear after the first yield even in the former example. I believe the computation’s result shouldn’t depend on whether it runs in the UI or not.

I'm curious to know your opinion.

Many thanks,
jaromir





--

Jaromír Matas

mail at jaromir.net

From: Juan Vuletich<mailto:JuanVuletich at zoho.com>
Sent: Thursday, July 14, 2022 19:17
To: Discussion of Cuis Smalltalk<mailto:cuis-dev at lists.cuis.st>
Cc: Juan Vuletich<mailto:JuanVuletich at zoho.com>; Jaromir Matas<mailto:mail at jaromir.net>
Subject: Re: [Cuis-dev] FW: FW: Freezing UI - can't interrupt via Alt+.

Hi Jaromir,

Just added a few new changes. When you have time, please update, retest, report.

Thanks!

On 7/14/2022 12:25 PM, Jaromir Matas via Cuis-dev wrote:
Hi Juan,

>> And this example stopped working properly when abandoning:
>>
>> [self halt] ensure: [self halt]

> What is the behavior you see? What is the behavior you expect? At what update number did it work as you expected?
In this case:
[self halt] ensure: [self halt]
If you abandon both debuggers, two more UIs keep running; It behaved and in my test image in Squeak it still behaves ok meaning no extra UIs are left behind after abandoning. I admit I couldn’t keep up to study your changes these days and my Squeak image is already a week old :)

In this case:
[1/0] fork.
5 seconds asDelay wait.
self error: 'error'
If you Proceed the error one extra UI would stay running.

And just now I’ve noticed Alt+. would leave one extra UI running as well (in both Abandon and Proceed cases). My image is fresh but it’s possible my previous experiments influence these latest ones.

I’ll have to analyze the situation in more detail because in Squeak analogous changes worked quite fine so I’m getting too confused where the differences are :) Please bear with me, I’ll be able to continue next week I hope. Thanks for your patience.

Thanks!
Jaromir





--

Juan Vuletich

www.cuis-smalltalk.org<http://www.cuis-smalltalk.org>

https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev

https://github.com/jvuletich

https://www.linkedin.com/in/juan-vuletich-75611b3

https://independent.academia.edu/JuanVuletich

https://www.researchgate.net/profile/Juan-Vuletich

https://patents.justia.com/inventor/juan-manuel-vuletich

https://twitter.com/JuanVuletich


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20220714/d0eee957/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MNU drawing fails.png
Type: image/png
Size: 270757 bytes
Desc: MNU drawing fails.png
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20220714/d0eee957/attachment-0001.png>