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

[Jaromir Matas]

Hi Juan,

> > Squeak and Pharo simply open the same image as read -only and notify the user... For me it's a reminder I opened a wrong image and close it. It took a me a while to realize in Cuis there's something invisible running in the background when I by accident opened the same image twice. Now that I know it doesn't bother me; so I'm just reporting :)

> That's great! How do they do it? [...]

Hmm... I've just tested it and it looks like it's not read-only at all like I assumed but it allows me to save both versions of the changes files (not sure whether it's good or bad). The warning about opening the same image twice is nice though. Squeak tries to open the changes file for read-write first and if it fails then it tries to open the same file for read-only and generates the warning when it succeeds :) (But I'm just a beginner as regards files and external access).

Thanks,
Jaromir


--

Jaromír Matas

mail at jaromir.net

From: Juan Vuletich<mailto:JuanVuletich at zoho.com>
Sent: Tuesday, July 19, 2022 1:43
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: FW: Freezing UI - can't interrupt via Alt+.

Hi Jaromir,

On 7/18/2022 7:09 PM, Jaromir Matas via Cuis-dev wrote:
Hi Juan,

Thanks very much, all works great; I love you added the states of the processes to the Process Browser - it's so convenient to see right away what is active, what is suspended etc...

> > If you open an image and then open the same image again (to be precise: in my case I doubleclick on squeak.exe, the image opens, then I doubleclick squeak.exe again) then the second OS process starts running in the background taking 100% of one CPU's core capacity (and nothing opens) and it needs to be killed from the OS

> Has any other dialect in the Squeak family already fixed this?

Squeak and Pharo simply open the same image as read-only and notify the user...

That's great! How do they do it? I mean 1) how do they detect the same is already running? 2) how do they open in read-only mode? If you could take a look and perhaps port the relevant code to Cuis, that would be a great contribution.


For me it's just a reminder I opened a wrong image and close it. It took a me a while to realize in Cuis there's something invisible running in the background when I by accident opened the same image twice. Now that I know it doesn't bother me; so I'm just reporting :)

Thanks again; it's a real joy to try concurrent prcesses examples in Cuis now :D

:)


Best,

--

Jaromír Matas

mail at jaromir.net<mailto:mail at jaromir.net>


Cheers,



--

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/20220719/608dedef/attachment-0001.htm>