Beginners October 2017

beginners@lists.squeakfoundation.org

12 participants
9 discussions

Re: [Newbies] losing focus
by Ralph Boland 26 Oct '17

26 Oct '17

Found/fixed problem: When my morph containing a collection of my button morphs was resized the icons (forms) were resized but not the buttons. So you were right. Oddly enough the containing morph knew how big each button was supposed to be so it allocated enough screen space for each button. I thought it was resizing the buttons too but I was wrong. In other places I did resize my button morphs when needed so in those instances it (of course) worked all along. > Hi Ralph, > can you file-out and share your version of the IconicButton class? I could but to you wouldn't have found the problem there because the way the code is written it is the responsibility of the code delivering the new icon/form to the button that is responsible for changing the button's extent. I suppose I could pass the icon/form and the new extent to the button together and let it be responsible for the changes. I'll think about it. Morph >> #handleEvent: is too low-level for your use case. You should only overwrite/implement #handlesMouseDown: and #mouseDown:, for example. my button class implemented #handleEvent only to set a breakpoint. I assume you mean that I should have instead did the same with #mouseDown: I will give this a try and see if it avoids my getting the emergency window. I had no idea that #handleEvent is lower level than #mouseDown:. Is there a place that I can learn things like this? Squeak seems to provide little documentation here (as elsewhere). It is definitely a trial by fire for me to figure all this GUI stuff out. I have little knowledge/interest in GUIs but need to know this since I am developing some children's educational software in Squeak. > Seems to me that the icon in your button is bigger than your button. > Only the button/owner gets the events here. YOU WERE RIGHT. This is what I did wrong. I knew that it is the button that gets the events; just failed to resize the button. > ... > Best, > Marcel Thanks. In retrospect this looks pretty obvious. :( Ralph --------------------------------Original message-------------------------------------------------- Am 25.10.2017 05:58:10 schrieb Ralph Boland <rpboland(a)gmail.com>: I created a button class which is version of IconicButton (by cutting and pasting) that does extra things that I need. One of the things that I do is expand the size of my button (actually a collection of my buttons) when running an application that uses it. When I do so only a small area of near the top left corner of my button seems to have focus so then if I click on that area the button works but otherwise it does not. When I click within my botton's working area >handleEvent: anEvent> is called by >processMouseOver: anEvent>. When my button does not work the method is not called because, I believe, the portion of my button that was clicked does not have focus. Note that when my button size is expanded it's position is also changed because other morphs have also expanded but this expansion does not seems to cause confusion as to where the button is because the working focus area remains in the same part of my button. But there appears to be confusion as to the size of my button and its focus area. Debugging this is a pain. When I set a break point in >handleEvent: anEvent> the emergency handler pops up. when I do a I get my stack with >handleEvent: anEvent> at the top of the stack. But I have gathered little useful information by looking at this stack. The only solution I can think of is to discard by button (buttons) and reinstantiate them every time they need to be resized. Is there something that I should be setting when I resize my button so that it's focus area is correct? Is discarding my buttons and reinsantiating them the only solution? Any help or insight appreciated. Ralph Boland

3 2

Is there a list that Smalltalk provides to show which keyboard character represents which number ?
by RedTigerFish 25 Oct '17

25 Oct '17

Transcript show: ((898324234234324329) printStringBase: 150); cr. After executing the above code, I get the following: <http://forum.world.st/file/t371379/tutu.jpg> I understand that each of those characters represents a number which in this case must be less than 150. Is there a list that Smalltalk provides to show which keyboard character represents which number ? ----- Dig, dig where you are, Down below's well. Let those that walk in darkness shout, Down below's hell. -- Sent from: http://forum.world.st/Squeak-Beginners-f107673.html

2 2

Losing focus
by Ralph Boland 25 Oct '17

25 Oct '17

I created a button class which is version of IconicButton (by cutting and pasting) that does extra things that I need. One of the things that I do is expand the size of my button (actually a collection of my buttons) when running an application that uses it. When I do so only a small area of near the top left corner of my button seems to have focus so then if I click on that area the button works but otherwise it does not. When I click within my botton's working area <MyButton>>handleEvent: anEvent> is called by <MouseOverHandler>>processMouseOver: anEvent>. When my button does not work the method <handleEvent: anEvent> is not called because, I believe, the portion of my button that was clicked does not have focus. Note that when my button size is expanded it's position is also changed because other morphs have also expanded but this expansion does not seems to cause confusion as to where the button is because the working focus area remains in the same part of my button. But there appears to be confusion as to the size of my button and its focus area. Debugging this is a pain. When I set a break point in <MyButton>>handleEvent: anEvent> the emergency handler pops up. when I do a <revert> I get my stack with <MyButton>>handleEvent: anEvent> at the top of the stack. But I have gathered little useful information by looking at this stack. The only solution I can think of is to discard by button (buttons) and reinstantiate them every time they need to be resized. Is there something that I should be setting when I resize my button so that it's focus area is correct? Is discarding my buttons and reinsantiating them the only solution? Any help or insight appreciated. Ralph Boland

2 1

Is it possible to make squeak workspace vim-like?
by RedTigerFish 25 Oct '17

25 Oct '17

I am very fond of VIM and have been so accustomed to its style of typing and entering. Is it possible to make squeak workspace vim-like? ----- Dig, dig where you are, Down below's well. Let those that walk in darkness shout, Down below's hell. -- Sent from: http://forum.world.st/Squeak-Beginners-f107673.html

3 2

In Squeak SmallTalk, what can I do to display a number in any hex I want?
by RedTigerFish 25 Oct '17

25 Oct '17

I have done a basic arithmetic calculation and got the answer aaHere is the SmallTalk code in Squeak: Transcript show: 'aa='.Transcript show: 23124234 * 431213; cr. The output is aa=99714703158429971470315842 is a decimal number.What can I do to display a number in any hex I want ?? -- Sent from: http://forum.world.st/Squeak-Beginners-f107673.html

6 10

Re: [Newbies] Animation question
by LEnglish 13 Oct '17

13 Oct '17

Because of garbage collection issues, smooth animation in Squeak isn’t really possible. My little OpenGL spaceship firing a missile animation had this annoying pause every so-often, as the GC activated and froze the screen. Was hoping that Craig Latta would release a minimal Spoon image that allowed me to load the OpenGL plugin code, because the GC in the minimal image took about 1/50th (or less) of the time that the complete image takes, but he got sidetracked with his Caffeine project. Lawson "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." -Brian Kernighan > On Oct 12, 2017, at 11:18, Bert Freudenberg <bert(a)freudenbergs.de> wrote: > > No, you have to put that test in the step method, because it has to be checked every time the position changes. > > Or you have to wait until the animation is done before doing the test - it does work in your first example with my "hack". It does not work in the second example because the forked code is executed after that test (plus forking is bad for this anyways). > > - Bert - > > On Thu, Oct 12, 2017 at 7:39 PM, obrienj <obrienj(a)protonmail.com <mailto:obrienj@protonmail.com>> wrote: > The problem is that I want use something like (self position) >= (120@100) ifTrue: [self color: Color yellow] outside of the step method. Even though the morph moves, it's position remains unchanged and the boolean tests false. Hope this makes sense. > > > >> -------- Original Message -------- >> Subject: Re: [Newbies] Animation question >> Local Time: October 12, 2017 10:25 AM >> UTC Time: October 12, 2017 5:25 PM >> From: bert(a)freudenbergs.de <mailto:bert@freudenbergs.de> >> To: obrienj <obrienj(a)protonmail.com <mailto:obrienj@protonmail.com>>, A friendly place to get answers to even the most basic questions about Squeak. <beginners(a)lists.squeakfoundation.org <mailto:beginners@lists.squeakfoundation.org>> >> >> On Thu, Oct 12, 2017 at 6:24 PM, obrienj <obrienj(a)protonmail.com <mailto:obrienj@protonmail.com>> wrote: >> I am having difficulty getting the following example to work using either delay or step: >> >> aMorph := Morph new. >> aMorph position: (100@100). >> aMorph openInWorld. >> 30 timesRepeat: [aMorph position: aMorph position +(1@0). Transcript show: 'test '; cr.]. >> (aMorph position) >= (120@100) ifTrue: [aMorph color: Color yellow]. >> Transcript show: 'position: ', aMorph position; cr. >> >> For example: >> >> aMorph := Morph new. >> aMorph position: (100@100). >> aMorph openInWorld. >> delay := Delay forMilliseconds: 20. >> [30 timesRepeat: [aMorph position: aMorph position +(1@0). delay wait.].] fork. >> (aMorph position) >= (110@100) ifTrue: [aMorph color: Color yellow]. >> Transcript show: 'position: ', aMorph position; cr. >> >> In the first example the morph moves, changes color, and the Transcript shows its final position. However, in the second example the morph moves but does not change color and the Transcript shows its starting position. >> >> Morphic animation is based on stepping. That means, you don't move a Morph repeatedly in a loop, but Morphic tells your morph to update its position repeatedly. >> >> You need to make your own Morph subclass and implement a "step" method. Whenever that method is called, it moves the morph by a little. For example, you could use an existing method called" translateBy:" >> >> | aMorph | >> aMorph := Morph new openInWorld. >> aMorph startStepping: #transformedBy: at: Time millisecondClockValue arguments: {MorphicTransform offset: -3 @ -3} stepTime: 200. >> >> However, it's unlikely no existing method does your specific animation, so you indeed need to implement it, eg >> >> step >> self position: self position + (1@0). >> (self position) >= (120@100) ifTrue: [self color: Color yellow]. >> >> So this is the Right Way. Without bad hacks you cannot do meaningful animation from a workspace. There is a hack however: If you insert "World doOneCycle" in the while loop of your first example, it will actually work, because it will redraw the world in each loop. However, this would prevent two objects animating independently, that's why the design calls for the "step" method approach. >> >> - Bert - >> > > > _______________________________________________ > Beginners mailing list > Beginners(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/beginners

4 3

Re: [Newbies] Animation question
by LEnglish 13 Oct '17

13 Oct '17

LEnglish LEnglish5(a)cox.net Unfortunately, can’t run that without windows, if I read the title correctly (“for windows”) Also, I was using OpenGL, which might have complicated things. Thanks for the link. I’ll try to figure out what they did differently than my experiment. L > On Oct 12, 2017, at 16:09, Chris Cunningham <cunningham.cb(a)gmail.com> wrote: > > Hi Lawson, > > Actually smooth animation in Squeak is possible. The best I've seen is at: > http://www.zogotounga.net/comp/saucers.htm <http://www.zogotounga.net/comp/saucers.htm> > This is pure squeak/morphic, using stepping. > > This isn't to say there aren't issue lurking about, of course. > > -cbc > > On Thu, Oct 12, 2017 at 3:41 PM, LEnglish <LEnglish5(a)cox.net <mailto:LEnglish5@cox.net>> wrote: > > > > Because of garbage collection issues, smooth animation in Squeak isn’t really possible. > > My little OpenGL spaceship firing a missile animation had this annoying pause every so-often, as the GC activated and froze the screen. > > Was hoping that Craig Latta would release a minimal Spoon image that allowed me to load the OpenGL plugin code, because the GC in the minimal image took about 1/50th (or less) of the time that the complete image takes, but he got sidetracked with his Caffeine project. > > Lawson > > "Debugging is twice as hard as writing the code in the first place. > Therefore, if you write the code as cleverly as possible, you are, > by definition, not smart enough to debug it." > -Brian Kernighan > > > >> On Oct 12, 2017, at 11:18, Bert Freudenberg <bert(a)freudenbergs.de <mailto:bert@freudenbergs.de>> wrote: >> >> No, you have to put that test in the step method, because it has to be checked every time the position changes. >> >> Or you have to wait until the animation is done before doing the test - it does work in your first example with my "hack". It does not work in the second example because the forked code is executed after that test (plus forking is bad for this anyways). >> >> - Bert - >> >> On Thu, Oct 12, 2017 at 7:39 PM, obrienj <obrienj(a)protonmail.com <mailto:obrienj@protonmail.com>> wrote: >> The problem is that I want use something like (self position) >= (120@100) ifTrue: [self color: Color yellow] outside of the step method. Even though the morph moves, it's position remains unchanged and the boolean tests false. Hope this makes sense. >> >> >> >>> -------- Original Message -------- >>> Subject: Re: [Newbies] Animation question >>> Local Time: October 12, 2017 10:25 AM >>> UTC Time: October 12, 2017 5:25 PM >>> From: bert(a)freudenbergs.de <mailto:bert@freudenbergs.de> >>> To: obrienj <obrienj(a)protonmail.com <mailto:obrienj@protonmail.com>>, A friendly place to get answers to even the most basic questions about Squeak. <beginners(a)lists.squeakfoundation.org <mailto:beginners@lists.squeakfoundation.org>> >>> >>> On Thu, Oct 12, 2017 at 6:24 PM, obrienj <obrienj(a)protonmail.com <mailto:obrienj@protonmail.com>> wrote: >>> I am having difficulty getting the following example to work using either delay or step: >>> >>> aMorph := Morph new. >>> aMorph position: (100@100). >>> aMorph openInWorld. >>> 30 timesRepeat: [aMorph position: aMorph position +(1@0). Transcript show: 'test '; cr.]. >>> (aMorph position) >= (120@100) ifTrue: [aMorph color: Color yellow]. >>> Transcript show: 'position: ', aMorph position; cr. >>> >>> For example: >>> >>> aMorph := Morph new. >>> aMorph position: (100@100). >>> aMorph openInWorld. >>> delay := Delay forMilliseconds: 20. >>> [30 timesRepeat: [aMorph position: aMorph position +(1@0). delay wait.].] fork. >>> (aMorph position) >= (110@100) ifTrue: [aMorph color: Color yellow]. >>> Transcript show: 'position: ', aMorph position; cr. >>> >>> In the first example the morph moves, changes color, and the Transcript shows its final position. However, in the second example the morph moves but does not change color and the Transcript shows its starting position. >>> >>> Morphic animation is based on stepping. That means, you don't move a Morph repeatedly in a loop, but Morphic tells your morph to update its position repeatedly. >>> >>> You need to make your own Morph subclass and implement a "step" method. Whenever that method is called, it moves the morph by a little. For example, you could use an existing method called" translateBy:" >>> >>> | aMorph | >>> aMorph := Morph new openInWorld. >>> aMorph startStepping: #transformedBy: at: Time millisecondClockValue arguments: {MorphicTransform offset: -3 @ -3} stepTime: 200. >>> >>> However, it's unlikely no existing method does your specific animation, so you indeed need to implement it, eg >>> >>> step >>> self position: self position + (1@0). >>> (self position) >= (120@100) ifTrue: [self color: Color yellow]. >>> >>> So this is the Right Way. Without bad hacks you cannot do meaningful animation from a workspace. There is a hack however: If you insert "World doOneCycle" in the while loop of your first example, it will actually work, because it will redraw the world in each loop. However, this would prevent two objects animating independently, that's why the design calls for the "step" method approach. >>> >>> - Bert - >>> >> >> >> _______________________________________________ >> Beginners mailing list >> Beginners(a)lists.squeakfoundation.org <mailto:Beginners@lists.squeakfoundation.org> >> http://lists.squeakfoundation.org/mailman/listinfo/beginners <http://lists.squeakfoundation.org/mailman/listinfo/beginners> > > > _______________________________________________ > Beginners mailing list > Beginners(a)lists.squeakfoundation.org <mailto:Beginners@lists.squeakfoundation.org> > http://lists.squeakfoundation.org/mailman/listinfo/beginners <http://lists.squeakfoundation.org/mailman/listinfo/beginners> > > > _______________________________________________ > Beginners mailing list > Beginners(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/beginners

1 0

Re: [Newbies] Animation question
by Bert Freudenberg 12 Oct '17

12 Oct '17

No, you have to put that test in the step method, because it has to be checked every time the position changes. Or you have to wait until the animation is done before doing the test - it does work in your first example with my "hack". It does not work in the second example because the forked code is executed after that test (plus forking is bad for this anyways). - Bert - On Thu, Oct 12, 2017 at 7:39 PM, obrienj <obrienj(a)protonmail.com> wrote: > The problem is that I want use something like (self position) >= (120@100) > ifTrue: [self color: Color yellow] outside of the step method. Even though > the morph moves, it's position remains unchanged and the boolean tests > false. Hope this makes sense. > > > > -------- Original Message -------- > Subject: Re: [Newbies] Animation question > Local Time: October 12, 2017 10:25 AM > UTC Time: October 12, 2017 5:25 PM > From: bert(a)freudenbergs.de > To: obrienj <obrienj(a)protonmail.com>, A friendly place to get answers to > even the most basic questions about Squeak. <beginners@lists. > squeakfoundation.org> > > On Thu, Oct 12, 2017 at 6:24 PM, obrienj <obrienj(a)protonmail.com> wrote: > >> I am having difficulty getting the following example to work using either >> delay or step: >> >> aMorph := Morph new. >> aMorph position: (100@100). >> aMorph openInWorld. >> 30 timesRepeat: [aMorph position: aMorph position +(1@0). Transcript >> show: 'test '; cr.]. >> (aMorph position) >= (120@100) ifTrue: [aMorph color: Color yellow]. >> Transcript show: 'position: ', aMorph position; cr. >> >> For example: >> >> aMorph := Morph new. >> aMorph position: (100@100). >> aMorph openInWorld. >> delay := Delay forMilliseconds: 20. >> [30 timesRepeat: [aMorph position: aMorph position +(1@0). delay >> wait.].] fork. >> (aMorph position) >= (110@100) ifTrue: [aMorph color: Color yellow]. >> Transcript show: 'position: ', aMorph position; cr. >> >> In the first example the morph moves, changes color, and the Transcript >> shows its final position. However, in the second example the morph moves >> but does not change color and the Transcript shows its starting position. >> > > Morphic animation is based on stepping. That means, you don't move a Morph > repeatedly in a loop, but Morphic tells your morph to update its position > repeatedly. > > You need to make your own Morph subclass and implement a "step" method. > Whenever that method is called, it moves the morph by a little. For > example, you could use an existing method called" translateBy:" > > | aMorph | > aMorph := Morph new openInWorld. > aMorph startStepping: #transformedBy: at: Time millisecondClockValue > arguments: {MorphicTransform offset: -3 @ -3} stepTime: 200. > > However, it's unlikely no existing method does your specific animation, so > you indeed need to implement it, eg > > step > self position: self position + (1@0). > (self position) >= (120@100) ifTrue: [self color: Color yellow]. > > So this is the Right Way. Without bad hacks you cannot do meaningful > animation from a workspace. There is a hack however: If you insert "World > doOneCycle" in the while loop of your first example, it will actually work, > because it will redraw the world in each loop. However, this would prevent > two objects animating independently, that's why the design calls for the > "step" method approach. > > - Bert - > > >

1 0

Animation question
by obrienj 12 Oct '17

12 Oct '17

I am having difficulty getting the following example to work using either delay or step: aMorph := Morph new. aMorph position: (100@100). aMorph openInWorld. 30 timesRepeat: [aMorph position: aMorph position +(1@0). Transcript show: 'test '; cr.]. (aMorph position) >= (120@100) ifTrue: [aMorph color: Color yellow]. Transcript show: 'position: ', aMorph position; cr. For example: aMorph := Morph new. aMorph position: (100@100). aMorph openInWorld. delay := Delay forMilliseconds: 20. [30 timesRepeat: [aMorph position: aMorph position +(1@0). delay wait.].] fork. (aMorph position) >= (110@100) ifTrue: [aMorph color: Color yellow]. Transcript show: 'position: ', aMorph position; cr. In the first example the morph moves, changes color, and the Transcript shows its final position. However, in the second example the morph moves but does not change color and the Transcript shows its starting position.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Beginners October 2017