- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Listening for shift key pressed

by Aliaksei Syrel

Hi, Thanks for the fast answer. But keyDown or keyUp are triggered only for not modifier keys (Tab, space, [0-9a-Z]). When I press Shift, keyDown is not triggered. :( Cheers, Alex On Fri, Nov 21, 2014 at 4:12 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Hi, > > I've some hints! > > Try listening to the keyDown and keyUp events of a morph. And take a look > at the #key message of a keyboard event. > > Cheers, > Guille > > On Fri, Nov 21, 2014 at 4:06 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> > wrote: > >> Hi, >> >> In our project we would like to trigger some actions when user presses >> down/up Shift button. But we didn't find how to do it. It seems that such >> keys as Shift, Capslock, Ctrl are event modifiers in Pharo, that apply on >> already existing events (in HandMorph>>generateKeyboardEvent: evtBuf). >> >> Do you have any ideas or maybe have experience concerning described >> problem? >> Thanks in advance. >> >> Cheers, >> Alex >> > >

Nov. 21, 2014

Re: [Pharo-dev] Listening for shift key pressed

by Guillermo Polito

Hi, I've some hints! Try listening to the keyDown and keyUp events of a morph. And take a look at the #key message of a keyboard event. Cheers, Guille On Fri, Nov 21, 2014 at 4:06 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hi, > > In our project we would like to trigger some actions when user presses > down/up Shift button. But we didn't find how to do it. It seems that such > keys as Shift, Capslock, Ctrl are event modifiers in Pharo, that apply on > already existing events (in HandMorph>>generateKeyboardEvent: evtBuf). > > Do you have any ideas or maybe have experience concerning described > problem? > Thanks in advance. > > Cheers, > Alex >

Nov. 21, 2014

Listening for shift key pressed

by Aliaksei Syrel

Hi, In our project we would like to trigger some actions when user presses down/up Shift button. But we didn't find how to do it. It seems that such keys as Shift, Capslock, Ctrl are event modifiers in Pharo, that apply on already existing events (in HandMorph>>generateKeyboardEvent: evtBuf). Do you have any ideas or maybe have experience concerning described problem? Thanks in advance. Cheers, Alex

Nov. 21, 2014

Glorp and DBXTalk

by Hernan Wilkinson

Hi, quick question, how can I get Glorp for Pharo? And DBXTalk? If anyone can provide me with some links it will be much appreciated :-) -- *HernÃ¡n WilkinsonAgile Software Development, Teaching & Coaching* *Phone: +54 - 011 - *6091 - 3125 *Mobile: +54 - 911 - 4470 - 7207email: hernan.wilkinson(a)10Pines.comsite: http://www.10Pines.com <http://www.10pines.com/>* Address: Alem 693, Floor 5 B, Buenos Aires, Argentina

Nov. 21, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40380 Home: https://github.com/pharo-project/pharo-core

Nov. 21, 2014

[pharo-project/pharo-core] f9a0b8: 40380

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: f9a0b80a61c7f7cd29f7a833e93475d87b606d21 https://github.com/pharo-project/pharo-core/commit/f9a0b80a61c7f7cd29f7a833… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-21 (Fri, 21 Nov 2014) Changed paths: A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script380.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40380.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Text-Edition.package/SimpleEditor.class/instance/nonediting%2Fnontyping keys/cursorHome_.st M Text-Edition.package/TextEditor.class/instance/nonediting%2Fnontyping keys/cursorHome_.st M Versionner-Spec-Browser.package/VersionnerRepositoriesManager.class/instance/initialization/initializeSelectedRemotes.st Log Message: ----------- 40380 14510 Wrong editing history positions after using home-key https://pharo.fogbugz.com/f/cases/14510 14495 Adding dependent projects in Versionner fails (adding to array instead of collection) https://pharo.fogbugz.com/f/cases/14495 http://files.pharo.org/image/40/40380.zip

Nov. 21, 2014

Re: [Pharo-dev] ConfigurationOfGlamour not connected to repository

by Stephan Eggermont

Doru wrote: >Indeed, these are not needed. Those groups are not maintainable and make tool building a nightmare. We will remove them from all Moose configurations eventually :). Sorry, afaik the groups are essential complexity and removing them just increases the problems. Configuration management is essentially a 5-dimensional problem and the tools need to support different workflows so they will never be simple. Stephan

Nov. 21, 2014

Re: [Pharo-dev] VM fixes to review

by Esteban Lorenzano

> On 21 Nov 2014, at 13:56, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 21 Nov 2014, at 13:46, Ben Coman <btc(a)openInWorld.com> wrote: >> >> Ben Coman wrote: >>> Marcus Denker wrote: >>>>> On 21 Nov 2014, at 13:21, stepharo <stepharo(a)free.fr> wrote: >>>>> >>>>> can you mark them as 4.0 >>>>> >>>> >>>> The problem is that they now show up in the integrator app and the monkey will try to run them with a non-existing slice, failing them all. >>> I checked they are all tagged NoMonkey. >>> Sorry I didn't consider the Integrator app. >> >> Maybe the integrator app should only show issues tagged "Fix To Includeâ > > Yes, that might be a good idea. in the integrator app (latest version), you can configure the issues you want to see. default values are just âFix Review Neededâ and âFix Reviewed by the Monkey" Esteban > > Marcus > >

Nov. 21, 2014

Re: [Pharo-dev] VM fixes to review

by Marcus Denker

> On 21 Nov 2014, at 13:46, Ben Coman <btc(a)openInWorld.com> wrote: > > Ben Coman wrote: >> Marcus Denker wrote: >>>> On 21 Nov 2014, at 13:21, stepharo <stepharo(a)free.fr> wrote: >>>> >>>> can you mark them as 4.0 >>>> >>> >>> The problem is that they now show up in the integrator app and the monkey will try to run them with a non-existing slice, failing them all. >> I checked they are all tagged NoMonkey. >> Sorry I didn't consider the Integrator app. > > Maybe the integrator app should only show issues tagged "Fix To Includeâ Yes, that might be a good idea. Marcus

Nov. 21, 2014

Re: [Pharo-dev] VM fixes to review

by Esteban Lorenzano

> On 21 Nov 2014, at 13:46, Ben Coman <btc(a)openInWorld.com> wrote: > > Ben Coman wrote: >> Marcus Denker wrote: >>>> On 21 Nov 2014, at 13:21, stepharo <stepharo(a)free.fr> wrote: >>>> >>>> can you mark them as 4.0 >>>> >>> >>> The problem is that they now show up in the integrator app and the monkey will try to run them with a non-existing slice, failing them all. >> I checked they are all tagged NoMonkey. >> Sorry I didn't consider the Integrator app. > > Maybe the integrator app should only show issues tagged "Fix To Includeâ they are two things: 1) integrator app 2) monkey. is the 2nd one who will fail without noMonkey :) Esteban > -ben >

Nov. 21, 2014