August 2013 - Pharo-dev - lists.pharo.org

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Aug. 6, 2013

Aug. 6, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/… 1 regressions found. KernelTests.Numbers.LargePositiveIntegerTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Aug. 6, 2013

Aug. 6, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linu… 1 regressions found. KernelTests.Numbers.LargePositiveIntegerTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses

1 0

[update 3.0] #30325
by Esteban Lorenzano Aug. 6, 2013

Aug. 6, 2013

30325 ----- 11294 Bugs in refactoring when using traits https://pharo.fogbugz.com/f/cases/11294 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Environment-Esteb… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Core-EstebanLoren… http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusRefactoring-EstebanLo… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-EstebanLorenzano.506…

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Aug. 6, 2013

Aug. 6, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/… 1 regressions found. KernelTests.Numbers.LargePositiveIntegerTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Aug. 6, 2013

Aug. 6, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/… 1 regressions found. KernelTests.Numbers.LargePositiveIntegerTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Aug. 6, 2013

Aug. 6, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linu… 1 regressions found. KernelTests.Numbers.LargePositiveIntegerTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses

1 0

[update30] #30323
by Esteban Lorenzano Aug. 6, 2013

Aug. 6, 2013

30323 ----- 11200 Repeated methods in superclasses, explicit requirement no implemented, repeated methods in traits https://pharo.fogbugz.com/f/cases/11200 (pass 1)

1 0

Re: [Pharo-dev] KeyDown and KeyUp without automatic key repeating.
by Ronie Salgado Aug. 5, 2013

Aug. 5, 2013

Thank you, Its not exactly what I need, but using it I can hack the result that I want using some dictionary holding the key down state. Greetings, Ronie Salgado 2013/8/5 Erwan Douaille <douailleerwan(a)gmail.com> > I made an example, i guess it's what you need. > Cheat with the keyUp > > ExempleKey new > > Mouse over the morph and try key left / right > > > 2013/8/5 Ronie Salgado <roniesalg(a)gmail.com> > >> Hello, >> I need to know how I can handle a KeyDown and a KeyUp morph event without >> automatic key repeating, to be able to setup an object that performs per >> frame animation. >> For the ones who have worked with SDL, what I need is something like >> SDL_EnableKeyRepeat(0, 0) >> >> Greetings, >> Ronie Salgado >> > > > > -- > Best regards, > > Douaille Erwan <douaille.erwan(a)gmail.com> >

1 0

Aug. 5, 2013

Hi guys I found a problem with method renaming. The scenario is the following one: - you have a message browser open with a list a methods (resulting from a sender/implementor). - you rename a method and you get an error why because the message browser does not replace the currently changed method. and the RGMethodDefinition that represented the renamed method defines the code like that MessageBrowser>>wrapItem: anItem | s | s :=String streamContents: [ :aStream | 3 to: (cachedHierarchy at: anItem) size do: [:i | aStream << ' ']. aStream << anItem methodClass name << ' ('. anItem isFromTrait ifTrue: [ aStream << anItem compiledMethod origin name; space ]. aStream << (anItem category ifNil: ['']) <<')']. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^ {s. anItem selector}. RGMethodDefinition>>compiledMethod "Retrieves the compiled method of this definition if exists" | rClass | (rClass := self realClass) notNil ifTrue: [ (rClass includesSelector: self selector) ifTrue: [ ^rClass >> self selector ] ]. ^nil category ^ self protocol protocol self isActive ifTrue: [ ^ self compiledMethod category ]]. self isHistorical ifTrue: [ ^ self protocolAtPointer ifNil:[ self compiledMethod ifNil:[ protocol ] ifNotNil:[ :cm| cm category ] ] ]. ^ protocol So I patched the protocol method as follows protocol self isActive ifTrue: [ ^ self compiledMethod ifNil: [ ' '] ifNotNilDo: [ :cm | cm category ]]. "I hate this ifNil test, the problem is that when we rename a method, a method definition in a list may still refers to the old selector and the definition of compiled method is that case is not finding the associated method because it holds the old selector and not the one corresponding to the one defined in the class." self isHistorical ifTrue: [ ^ self protocolAtPointer ifNil:[ self compiledMethod ifNil:[ protocol ] ifNotNil:[ :cm| cm category ] ] ]. ^ protocol I imagine that the best solution would be that the tools update their contents but I wanted to know your point of view. Stef

2 2

KeyDown and KeyUp without automatic key repeating.
by Ronie Salgado Aug. 5, 2013

Aug. 5, 2013

Hello, I need to know how I can handle a KeyDown and a KeyUp morph event without automatic key repeating, to be able to setup an object that performs per frame animation. For the ones who have worked with SDL, what I need is something like SDL_EnableKeyRepeat(0, 0) Greetings, Ronie Salgado

1 0