May 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Roassal-Woden dynamically change an element height without redrawing

by Alexandre Bergel

You need to update GT-InspectorExtensions also Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On May 11, 2015, at 11:02 AM, Lusa Nicolas <nicolas.lusa(a)usi.ch> wrote: > > Hi, > > thank you it works now. > > Cheers, > Nicolas > > > On May 11, 2015, at 5:54 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> Hi Lusa, >> >> This was missing. Please update Woden (Core & Roassal) and you can do: >> -=-=-=-=-=-=-=-=-=-=-=-= >> v := RWView new. >> >> e := RWCube element. >> >> v add: e. >> >> e when: RWMouseButtonDown do: [ :evt | >> evt element shape width: 2. >> evt element shape height: 2. >> evt element shape color: WDColor green. >> >> e changed. >> ]. >> ^ v >> -=-=-=-=-=-=-=-=-=-=-=-= >> >> Let us know how this goes >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >>> On May 11, 2015, at 8:19 AM, Lusa Nicolas <nicolas.lusa(a)usi.ch> wrote: >>> >>> Hi folks! >>> >>> I am working with Roassal-Woden and I want to dynamically change the size of an element already drawn and already added to my view. This could be overcome simply by drawing a new element on top of the current one but works only for bigger elements. >>> What if I want to take the current one and simply change it? >>> >>> Here is what I thought would be working but it isn't: >>> >>> shape height: aValue. >>> element changed. >>> >>> Where shape is my RWShape (a RWCube in my case) and element is the shape element (an RWElement). >>> The curious thing is that this code is actually working for the color: >>> >>> shape color: aWDColor. >>> element changed. >>> >>> Any tips on what is wrong about my code? >>> >>> Cheers, >>> Nicolas >>> >> >> > >

May 11, 2015

Re: [Pharo-users] Roassal-Woden dynamically change an element height without redrawing

by Alexandre Bergel

Hi Lusa, This was missing. Please update Woden (Core & Roassal) and you can do: -=-=-=-=-=-=-=-=-=-=-=-= v := RWView new. e := RWCube element. v add: e. e when: RWMouseButtonDown do: [ :evt | evt element shape width: 2. evt element shape height: 2. evt element shape color: WDColor green. e changed. ]. ^ v -=-=-=-=-=-=-=-=-=-=-=-= Let us know how this goes Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On May 11, 2015, at 8:19 AM, Lusa Nicolas <nicolas.lusa(a)usi.ch> wrote: > > Hi folks! > > I am working with Roassal-Woden and I want to dynamically change the size of an element already drawn and already added to my view. This could be overcome simply by drawing a new element on top of the current one but works only for bigger elements. > What if I want to take the current one and simply change it? > > Here is what I thought would be working but it isn't: > > shape height: aValue. > element changed. > > Where shape is my RWShape (a RWCube in my case) and element is the shape element (an RWElement). > The curious thing is that this code is actually working for the color: > > shape color: aWDColor. > element changed. > > Any tips on what is wrong about my code? > > Cheers, > Nicolas >

May 11, 2015

Re: [Pharo-users] Roassal-Woden dynamically change an element height without redrawing

by Lusa Nicolas

Hi, thank you it works now. Cheers, Nicolas On May 11, 2015, at 5:54 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi Lusa, > > This was missing. Please update Woden (Core & Roassal) and you can do: > -=-=-=-=-=-=-=-=-=-=-=-= > v := RWView new. > > e := RWCube element. > > v add: e. > > e when: RWMouseButtonDown do: [ :evt | > evt element shape width: 2. > evt element shape height: 2. > evt element shape color: WDColor green. > > e changed. > ]. > ^ v > -=-=-=-=-=-=-=-=-=-=-=-= > > Let us know how this goes > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On May 11, 2015, at 8:19 AM, Lusa Nicolas <nicolas.lusa(a)usi.ch> wrote: >> >> Hi folks! >> >> I am working with Roassal-Woden and I want to dynamically change the size of an element already drawn and already added to my view. This could be overcome simply by drawing a new element on top of the current one but works only for bigger elements. >> What if I want to take the current one and simply change it? >> >> Here is what I thought would be working but it isn't: >> >> shape height: aValue. >> element changed. >> >> Where shape is my RWShape (a RWCube in my case) and element is the shape element (an RWElement). >> The curious thing is that this code is actually working for the color: >> >> shape color: aWDColor. >> element changed. >> >> Any tips on what is wrong about my code? >> >> Cheers, >> Nicolas >> > >

May 11, 2015

Re: [Pharo-users] Custom error class

by Sven Van Caekenberghe

Hi Mark, Deep into Pharo, http://rmod.lille.inria.fr/pbe2/ contains a chapter about exceptions. Apart from that, the image is of course the best example ! Have a look at the hierarchy below Exception, and try to follow the references of each class. You should be able to find out how each exception gets signalled and handled. Try NotFound for example. Sven > On 11 May 2015, at 16:13, Mark Rizun <mrizun(a)gmail.com> wrote: > > Hi guys! > > I was wondering if there is a tutorial/chapter in books or smth to read > about implementing custom error class properly. If not maybe there are some > good examples already implemented, so I could learn by exploring them. > Thanks in advance! > > Mark > > > > -- > View this message in context: http://forum.world.st/Custom-error-class-tp4825693.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

May 11, 2015

Custom error class

by Mark Rizun

Hi guys! I was wondering if there is a tutorial/chapter in books or smth to read about implementing custom error class properly. If not maybe there are some good examples already implemented, so I could learn by exploring them. Thanks in advance! Mark -- View this message in context: http://forum.world.st/Custom-error-class-tp4825693.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 11, 2015

Wait two seconds

by Torsten Bergmann

Sean wrote on Twitter (https://twitter.com/SeanDenigris) >At times I'm still floored by the simple elegance of #Smalltalk. Today's smile-evoking snippet: `2 seconds asDelay wait`â¦ perfectly said :) Why so complicated "2 seconds wait" will do as well, is more compact and crystal clear ;) Have fun T.

May 11, 2015

Roassal-Woden dynamically change an element height without redrawing

by Lusa Nicolas

Hi folks! I am working with Roassal-Woden and I want to dynamically change the size of an element already drawn and already added to my view. This could be overcome simply by drawing a new element on top of the current one but works only for bigger elements. What if I want to take the current one and simply change it? Here is what I thought would be working but it isn't: shape height: aValue. element changed. Where shape is my RWShape (a RWCube in my case) and element is the shape element (an RWElement). The curious thing is that this code is actually working for the color: shape color: aWDColor. element changed. Any tips on what is wrong about my code? Cheers, Nicolas

May 11, 2015

Re: [Pharo-users] MouseWheel events

by Matthieu Lacaton

> > That is correct by default, but you can always hack the VM if you reeeeally > want that behavior. Also, if you just wait a bit, I'm in the process of > remapping the wheel simulation shortcuts to be extremely less likely to > conflict with actual keyboard events. It is already done for Mac. I wrote > the patch for GNU/Linux & Windows, but didn't have machines available when > I > was testing (the code may take a bit of massaging to compile). The upside > is > that it's a backward compatible VM change, so you will be able to take > advantage of it in any Pharo version that will run on the latest VMs. > Okay, no problem I'll wait. No, you would code it the same way. In the image, MouseWheelEvents are > created regardless of the keyboard event used to simulate them. The only > thing different would be the keyboard equivalents. Okay, I double checked that and in the Pharo 4 version of the VM found on http://pharo.org/download by clicking the big blue "windows" button MouseWheel events are not created on an actual mouse wheel because the charcode returned is 0. But with the latest VM it works and mousewheel events are indeed created so it is my fault for not using the latest VM :) Thanks a lot ! 2015-05-11 2:34 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Matthieu Lacaton wrote > > Let's say for example thant I want to create a rectangle on the screen > and > > be able to move it up and down by pressing CTRL + up / down arrow and be > > able to rotate it with the mouse wheel. Does this mean that on Linux I > > just > > can't ? > > That is correct by default, but you can always hack the VM if you reeeeally > want that behavior. Also, if you just wait a bit, I'm in the process of > remapping the wheel simulation shortcuts to be extremely less likely to > conflict with actual keyboard events. It is already done for Mac. I wrote > the patch for GNU/Linux & Windows, but didn't have machines available when > I > was testing (the code may take a bit of massaging to compile). The upside > is > that it's a backward compatible VM change, so you will be able to take > advantage of it in any Pharo version that will run on the latest VMs. > > > Matthieu Lacaton wrote > > And does this mean that if I create an application able to react to mouse > > wheel, I need to code it differently for Windows and for Linux ? > > No, you would code it the same way. In the image, MouseWheelEvents are > created regardless of the keyboard event used to simulate them. The only > thing different would be the keyboard equivalents. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/MouseWheel-events-tp4824839p4825605.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

May 11, 2015

[ANN]: MixedNumberPrinter

by Sean P. DeNigris

I wrote a little tool to print fractions/decimals as mixed numbers. Enjoy :) Gofer it smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; package: 'MixedNumberPrinter'; load. Usage Examples: 1.25 mixedNumberString = '1Â¼'. "use special ASCII characters when possible" 1.125 mixedNumberString = '1 1/8' ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-MixedNumberPrinter-tp4825615.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 11, 2015

Re: [Pharo-users] MouseWheel events

by Sean P. DeNigris

Matthieu Lacaton wrote > Let's say for example thant I want to create a rectangle on the screen and > be able to move it up and down by pressing CTRL + up / down arrow and be > able to rotate it with the mouse wheel. Does this mean that on Linux I > just > can't ? That is correct by default, but you can always hack the VM if you reeeeally want that behavior. Also, if you just wait a bit, I'm in the process of remapping the wheel simulation shortcuts to be extremely less likely to conflict with actual keyboard events. It is already done for Mac. I wrote the patch for GNU/Linux & Windows, but didn't have machines available when I was testing (the code may take a bit of massaging to compile). The upside is that it's a backward compatible VM change, so you will be able to take advantage of it in any Pharo version that will run on the latest VMs. Matthieu Lacaton wrote > And does this mean that if I create an application able to react to mouse > wheel, I need to code it differently for Windows and for Linux ? No, you would code it the same way. In the image, MouseWheelEvents are created regardless of the keyboard event used to simulate them. The only thing different would be the keyboard equivalents. ----- Cheers, Sean -- View this message in context: http://forum.world.st/MouseWheel-events-tp4824839p4825605.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 11, 2015