Hi Stephen --
Sounds like yet another reason to drop morphic, if you ask me, and go back to good-old MVC…
To you? Maybe. Fortunately, us frequent users of and contributors to Squeak/Morphic see this a bit differently. ;-)
I’ve been watching this thread and wondering why nobody suggests the simplest answer: [...]
First, counting the number of characters, your suggestion has more compared to using #future:. ;-) Second, I am not quite sure how you define "simplest", but using #fork comes with *a lot* of semantic baggage. One might encounter all kinds of nasty debuggers just because one does not know about the challenges of multi-processing and shared data structures and so on. Just because ST-80 MVC did not even try to support you in this regard does not imply that it is better compared to Morphic. At least, Morphic gives you something to work with.
It is so funny how people react to things they do not yet know much about. Many times, they are kind of anxious and claim to know better without even trying to learn about that unfamiliar territory. Jumping to conclusions ... so many times ... just jumping to conclusions. It is exhausting.
In general, I am always interested in discussing and improving the challenging parts in Squeak, including Morphic. However, if somebody thinks that "replacing everything" can make things better, that somebody deliberately chose to not participate in such a discussion any longer.
Guess what? Nothing is perfect. Try to look for the nice things. It may even brighten up your day a little bit. ;-)
Best, Marcel Am 24.02.2023 02:14:46 schrieb Stephen Travis Pope stephen@heaveneverywhere.com:
Sounds like yet another reason to drop morphic, if you ask me, and go back to good-old MVC…
stp
--------
Stephen Travis Pope Ojai, California, USA [pastedGraphic.tiff] http://HeavenEverywhere.com http://FASTLabInc.com https://vimeo.com/user19434036/videos http://heaveneverywhere.com/Reflections
On Feb 23, 2023, at 1:54 PM, Vanessa Freudenberg vanessa@codefrau.net wrote:
Because Morphic is not multi-thread-clean, you have to be really careful how to write the do_something to be reliably executed from a different process. You have to coordinate with the UI process. In which case it actually becomes simpler to just stay in the UI process and use the mechanisms available.
Vanessa
On Thu, Feb 23, 2023 at 11:38 AM Stephen Travis Pope <stephen@heaveneverywhere.com [mailto:stephen@heaveneverywhere.com]> wrote:
I’ve been watching this thread and wondering why nobody suggests the simplest answer:
[(Delay forSeconds: 5) wait. do_something] fork.
stp
--------
Stephen Travis Pope Ojai, California, USA <pastedGraphic.tiff> http://HeavenEverywhere.com [http://heaveneverywhere.com/] http://FASTLabInc.com [http://fastlabinc.com/] https://vimeo.com/user19434036/videos [https://vimeo.com/user19434036/videos] http://heaveneverywhere.com/Reflections [http://heaveneverywhere.com/Reflections]
On Feb 22, 2023, at 11:16 AM, karl ramberg <karlramberg@gmail.com [mailto:karlramberg@gmail.com]> wrote:
On Wed, Feb 22, 2023 at 8:47 AM Taeumel, Marcel via Squeak-dev <squeak-dev@lists.squeakfoundation.org [mailto:squeak-dev@lists.squeakfoundation.org]> wrote:
(bm2 future: 1000) doButtonAction.
Also works for objects that are not or cannot be in the world.
Uses Morphic alarms when when in UI process. Ah, that's cool. I never used #future: :-)
Best, Karl
Best, Marcel From: Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org [mailto:squeak-dev-bounces@lists.squeakfoundation.org]> on behalf of Eduardo Ochs <eduardoochs@gmail.com [mailto:eduardoochs@gmail.com]> Sent: Wednesday, February 22, 2023 7:17:01 AM To: The general-purpose Squeak developers list <squeak-dev@lists.squeakfoundation.org [mailto:squeak-dev@lists.squeakfoundation.org]> Subject: Re: [squeak-dev] How do I "sleep 5"? Hi Karl! Fantastic, thanks! =) I added this to the class in which I'm putting most of my stuff,
!See class methodsFor: 'as yet unclassified' stamp: 'Edrx 2/22/2023 02:54'! run: aBlock after: ms | aButton | aButton := SimpleButtonMorph new. aButton openInWorld; hide; target: aBlock; actionSelector: #value; addAlarm: #doButtonAction after: ms. ! !
and now I can simply run this
See run: [ kf := self currentHand keyboardFocus ] after: 5000.
to save into the variable kf the morph on which the keyboard focus is after 5 seconds. Neat! =)
Cheers, Eduardo Ochs http://anggtwu.net/eev-squeak.html [http://anggtwu.net/eev-squeak.html]
On Wed, 22 Feb 2023 at 01:56, karl ramberg <karlramberg@gmail.com [mailto:karlramberg@gmail.com]> wrote:
Hi, A morph has to be in the world to be able to interact with it; eg. #openInWorld.
If you don't want to see the morph you can send it message #hide. It makes the morph invisible but it's still in the world and can interact with it.
To see the morph again send #show. To delete the morph send #delete. The morph will be garbage collected.
Best, Karl
On Tue, Feb 21, 2023 at 11:57 PM Eduardo Ochs <eduardoochs@gmail.com [mailto:eduardoochs@gmail.com]> wrote:
Hi Vanessa! Thanks! =) This works in a workspace,
"Create a SimpleSwitchMorph with label 'Toggle' and a SimpleButtonMorph with label 'Flash'. The button will be placed below the switch." sm := SimpleSwitchMorph new. sm openInWorld. bm := SimpleButtonMorph new. bm openInWorld. bm position: bm position + (0@32). "Three ways of toggling the color of the switch:" sm toggleState. bl := [ sm toggleState ]. bl value. bm target: bl. bm actionSelector: #value. bm doButtonAction. "Two ways of toggling the switch after 1000ms:" sm addAlarm: #toggleState after: 1000. bm addAlarm: #doButtonAction after: 1000.
but this doesn't:
bm2 := SimpleButtonMorph new. bm2 target: bl. bm2 actionSelector: #value. bm2 addAlarm: #doButtonAction after: 1000.
What is the right way to add an alarm to a morph that is not shown on the screen? Also, can I create a new invisible morph every time that I want to run an alarm? Are they going to be garbage collected?
Thanks in advance! Eduardo Ochs http://anggtwu.net/eev-squeak.html [http://anggtwu.net/eev-squeak.html]
On Tue, 21 Feb 2023 at 02:16, Vanessa Freudenberg <vanessa@codefrau.net [mailto:vanessa@codefrau.net]> wrote:
The best way to do this in Morphic is with "alarms":
self addAlarm: #changeKeyboardFocus after: 5000.
which would execute the morph's changeKeyboardFocus method 5 seconds later.
The way of sleeping you suggest is possible too but more tricky, since you would have to move your wait code to an extra process to not block the UI process, but then make sure that the actual work is done in the UI process again (Morphic is not multithreaded, although Squeak is).
Vanessa
On Mon, Feb 20, 2023 at 8:49 PM Eduardo Ochs <eduardoochs@gmail.com [mailto:eduardoochs@gmail.com]> wrote:
Hi list,
a few days ago I asked for help on how to send a "synthetic" keyboard event to a morph, and Karl Ramberg gave me exactly the right hints in this thread:
http://lists.squeakfoundation.org/pipermail/squeak-dev/2023-February/223473.... [http://lists.squeakfoundation.org/pipermail/squeak-dev/2023-February/223473....]
My code is ready except for documentation and comments - I'll work on that in the next few days and then post the result here and on the wiki...
...but there's a feature that I want to add to it that - again =( - needs something that I'm not being able to discover by myself. How do I write a line of code that waits for 5 seconds, sort of like running "sleep 5" in a shell, and that doesn't block the rest of the system? If I have that I'll be able to run these two lines in a workspace,
self mySleep: 5000. kf := self currentHand keyboardFocus.
switch the keyboard focus to something else by clicking on it, and then the variable kf will be set to this "something else"...
Thanks in advance! Eduardo Ochs http://anggtwu.net/eev-squeak.html [http://anggtwu.net/eev-squeak.html]