July 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Morph does not refresh or show

by Lukas Renggli

>> ScrollBar>>animateValue: aNumber duration: anInteger >> Â Â Â Â anInteger <= 0 >> Â Â Â Â Â Â Â Â ifTrue: [ self setValue: aNumber ] >> Â Â Â Â Â Â Â Â ifFalse: [ >> Â Â Â Â Â Â Â Â Â Â Â Â | startTime start | >> Â Â Â Â Â Â Â Â Â Â Â Â startTime := Time millisecondClockValue. >> Â Â Â Â Â Â Â Â Â Â Â Â start := value roundTo: scrollDelta. >> Â Â Â Â Â Â Â Â Â Â Â Â [ | delta | >> Â Â Â Â Â Â Â Â Â Â Â Â [ (delta := Time millisecondClockValue - startTime) < anInteger ] >> whileTrue: [ >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self setValue: (aNumber - start) * (delta / anInteger) + start. >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Processor yield ]. >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self setValue: aNumber ] >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â fork ] >> >> Typically morphic animations should be implemented implemented using >> the built-in stepping mechanism (#wantsSteps, #step, ...), but that's >> not always possible. > > I would say, that's the only way how morphs should animate themselves. > Because if you do it otherwise (like in a loop), then you pausing a > rest of processing, blocking UI etc and this is not good. I agree, but the above code does not have that problem. In fact it works pretty well, i.e. when the system is busy/slow it just sets the end state of the animation. > A good example for morphs animation is bouncing atoms. But i'm not > sure if it still residing in pharo images. Now if somebody is looking for an interesting project I would suggest to implement CoreAnimation clone (http://en.wikipedia.org/wiki/Core_Animation) CoreAnimation is a beautiful and powerful object-oriented animation system for Cocoa. It should be strait forward to port the API, because Cocoa is essentially a nice implementation of Morphic. Lukas -- Lukas Renggli www.lukas-renggli.ch

July 28, 2011

Re: [Pharo-project] Does anyone has FUEL running in Pharo 1.3?

by Martin Dias

On Thu, Jul 28, 2011 at 4:15 AM, Friedrich Dominicus < frido(a)q-software-solutions.de> wrote: > Martin Dias <tinchodias(a)gmail.com> writes: > > > Hi Friedrich > > > > It should run. How can I reproduce your error? > Well I probably had not a plain Pharo 1.3 (was not aware of that) > but I reinstalled a fresh Pharo 1.3 and it simple loaded. > > I'm sorry for the noise > > Fine. You are welcome. > Friedrich > > -- > Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim > Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus > >

July 28, 2011

Re: [Pharo-project] FloatArray inaccuracy

by Igor Stasenko

Float numbers are inexact and always been. Maybe you meant that they are more inexact than you expected? :) FloatArray stores floats using 32-bit floating point precision format. While Float(s) using 64 bits. No surprise that values stored in FloatArray are less precise. On 28 July 2011 08:34, Martin Dias <tinchodias(a)gmail.com> wrote: > If forgot to specify that I run this on Pharo 1.3 build #226 in Windows with > : > > Smalltalk vmVersion ----> 'Croquet Closure Cog VM [CoInterpreter > VMMaker.oscog-eem.56]' > > Martin > > On Thu, Jul 28, 2011 at 3:30 AM, Martin Dias <tinchodias(a)gmail.com> wrote: >> >> Hi >> >> I found that FloatArray>>at:put: is inaccurate: >> >> | floats | >> floats := FloatArray new: 1. >> floats at: 1 put: 11.22321. >> floats at: 1 " ------------> 11.223210334777832 " >> >> >> Do you know this issue? >> >> >> This is the implementation of at:put:: >> >> at: index put: value >> Â Â Â <primitive: 'primitiveAtPut' module: 'FloatArrayPlugin'> >> Â Â Â value isFloat >> Â Â Â Â Â Â ifTrue:[self basicAt: index put: value asIEEE32BitWord] >> Â Â Â Â Â Â ifFalse:[self at: index put: value asFloat]. >> Â Â Â ^value >> >> Thanks in advance >> Martin > > -- Best regards, Igor Stasenko AKA sig.

July 28, 2011

Re: [Pharo-project] Morph does not refresh or show

by Igor Stasenko

On 28 July 2011 09:04, Lukas Renggli <renggli(a)gmail.com> wrote: > You need to give the morph the time to refresh. This regularly happens > in the UI process, but probably not in your case because the system is > busy with other things. Have a look at how OB implements the smooth > scrolling of the panes: > > ScrollBar>>animateValue: aNumber duration: anInteger > Â Â Â Â anInteger <= 0 > Â Â Â Â Â Â Â Â ifTrue: [ self setValue: aNumber ] > Â Â Â Â Â Â Â Â ifFalse: [ > Â Â Â Â Â Â Â Â Â Â Â Â | startTime start | > Â Â Â Â Â Â Â Â Â Â Â Â startTime := Time millisecondClockValue. > Â Â Â Â Â Â Â Â Â Â Â Â start := value roundTo: scrollDelta. > Â Â Â Â Â Â Â Â Â Â Â Â [ | delta | > Â Â Â Â Â Â Â Â Â Â Â Â [ (delta := Time millisecondClockValue - startTime) < anInteger ] > whileTrue: [ > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self setValue: (aNumber - start) * (delta / anInteger) + start. > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Processor yield ]. > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â self setValue: aNumber ] > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â fork ] > > Typically morphic animations should be implemented implemented using > the built-in stepping mechanism (#wantsSteps, #step, ...), but that's > not always possible. > I would say, that's the only way how morphs should animate themselves. Because if you do it otherwise (like in a loop), then you pausing a rest of processing, blocking UI etc and this is not good. A good example for morphs animation is bouncing atoms. But i'm not sure if it still residing in pharo images. > Lukas > > On 28 July 2011 08:21, abara <barakat2(a)illinois.edu> wrote: >> Hello, >> >> I am having an issue where I need to refresh an object that is a subclass of >> RectangleMorph in a window. My object needs to travel across the screen at >> certain intervals. >> >> A controller object tells this RectangleMorph object where wants it, and in >> turn the Rectangle object sets its new position with >> Â Â Â Â self position: newX@ newY. >> >> but the object does not show up. It does however take the exact time it >> should to travel, but it just doesn't display itself. >> >> When I run the same program in debug, everything works fine, meaning I can >> see the object travel across the screen. Am I missing a method to refresh >> the object in real time? >> I have tried >> self changed, etc. >> >> Thanks >> Barakat >> >> >> >> -- >> View this message in context: http://forum.world.st/Morph-does-not-refresh-or-show-tp3700516p3700516.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > -- Best regards, Igor Stasenko AKA sig.

July 28, 2011

Re: [Pharo-project] Does anyone has FUEL running in Pharo 1.3?

by Friedrich Dominicus

Martin Dias <tinchodias(a)gmail.com> writes: > Hi Friedrich > > It should run. How can I reproduce your error? Well I probably had not a plain Pharo 1.3 (was not aware of that) but I reinstalled a fresh Pharo 1.3 and it simple loaded. I'm sorry for the noise Friedrich -- Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus

July 28, 2011

Re: [Pharo-project] Does anyone has FUEL running in Pharo 1.3?

by Francois Stephany

Fuel 1.4 works fine on Pharo 1.3 for me (CogVM, MacOS & Linux). What's the error message ? On 28/07/11 08:38, Friedrich Dominicus wrote: > Just wondering, because while trying to load it I get an error message > > Regards > Friedrich >

July 28, 2011

Re: [Pharo-project] Morph does not refresh or show

by Lukas Renggli

You need to give the morph the time to refresh. This regularly happens in the UI process, but probably not in your case because the system is busy with other things. Have a look at how OB implements the smooth scrolling of the panes: ScrollBar>>animateValue: aNumber duration: anInteger anInteger <= 0 ifTrue: [ self setValue: aNumber ] ifFalse: [ | startTime start | startTime := Time millisecondClockValue. start := value roundTo: scrollDelta. [ | delta | [ (delta := Time millisecondClockValue - startTime) < anInteger ] whileTrue: [ self setValue: (aNumber - start) * (delta / anInteger) + start. Processor yield ]. self setValue: aNumber ] fork ] Typically morphic animations should be implemented implemented using the built-in stepping mechanism (#wantsSteps, #step, ...), but that's not always possible. Lukas On 28 July 2011 08:21, abara <barakat2(a)illinois.edu> wrote: > Hello, > > I am having an issue where I need to refresh an object that is a subclass of > RectangleMorph in a window. My object needs to travel across the screen at > certain intervals. > > A controller object tells this RectangleMorph object where wants it, and in > turn the Rectangle object sets its new position with > Â Â Â Â self position: newX@ newY. > > but the object does not show up. It does however take the exact time it > should to travel, but it just doesn't display itself. > > When I run the same program in debug, everything works fine, meaning I can > see the object travel across the screen. Am I missing a method to refresh > the object in real time? > I have tried > self changed, etc. > > Thanks > Barakat > > > > -- > View this message in context: http://forum.world.st/Morph-does-not-refresh-or-show-tp3700516p3700516.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Lukas Renggli www.lukas-renggli.ch

July 28, 2011

Re: [Pharo-project] Does anyone has FUEL running in Pharo 1.3?

by Martin Dias

Hi Friedrich It should run. How can I reproduce your error? Martin On Thu, Jul 28, 2011 at 3:38 AM, Friedrich Dominicus < frido(a)q-software-solutions.de> wrote: > Just wondering, because while trying to load it I get an error message > > Regards > Friedrich > > -- > Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim > Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus > >

July 28, 2011

[Pharo-project] Does anyone has FUEL running in Pharo 1.3?

by Friedrich Dominicus

Just wondering, because while trying to load it I get an error message Regards Friedrich -- Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus

July 28, 2011

Re: [Pharo-project] FloatArray inaccuracy

by Martin Dias

If forgot to specify that I run this on Pharo 1.3 build #226 in Windows with : Smalltalk vmVersion ----> 'Croquet Closure Cog VM [CoInterpreter VMMaker.oscog-eem.56]' Martin On Thu, Jul 28, 2011 at 3:30 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > Hi > > I found that FloatArray>>at:put: is inaccurate: > > | floats | > floats := FloatArray new: 1. > floats at: 1 put: 11.22321. > floats at: 1 " ------------> 11.223210334777832 " > > > Do you know this issue? > > > This is the implementation of at:put:: > > at: index put: value > <primitive: 'primitiveAtPut' module: 'FloatArrayPlugin'> > value isFloat > ifTrue:[self basicAt: index put: value asIEEE32BitWord] > ifFalse:[self at: index put: value asFloat]. > ^value > > Thanks in advance > Martin >

July 28, 2011