cmdGesturesEnabled false -> no halos ?

Hello,

Is it the intended behavior that turning off the preference
cmdGesturesEnabled makes it impossible to get halos ?

This is new in trunk (as of 15697). The change is in
Morph>>#handleMouseDown: where there is a new test.

If it is indeed intended, it does bother me quite a bit, as I need both
halos working and cmdGesturesEnabled set to false in my application.

(To be precise, I made some morphs respond in a specific way to
Ctrl-dragging which is made impossible if cmdGesturesEnabled is true
because then Ctrl is intercepted, again in Morph>>#handleMouseDown:)


Stef
       

On 05.03.2016, at 12:11, Stéphane Rollandin <[hidden email]> wrote:
>
> Hello,
>
> Is it the intended behavior that turning off the preference cmdGesturesEnabled makes it impossible to get halos ?

Yes, see comment in disableProgrammerFacilities.

> This is new in trunk (as of 15697). The change is in Morph>>#handleMouseDown: where there is a new test.
>
> If it is indeed intended, it does bother me quite a bit, as I need both halos working and cmdGesturesEnabled set to false in my application.
>
> (To be precise, I made some morphs respond in a specific way to Ctrl-dragging which is made impossible if cmdGesturesEnabled is true because then Ctrl is intercepted, again in Morph>>#handleMouseDown:)

Hmm, cmdGesturesEnabled seems to control lots of independent behavior. Maybe we need more fine-grained settings?

- Bert -

> Hmm, cmdGesturesEnabled seems to control lots of independent behavior. Maybe we need more fine-grained settings?

I would say so :)

Stef

> Is anyone using gestures ?

What are gestures ?

Stef

> Hmm, cmdGesturesEnabled seems to control lots of independent behavior. Maybe we need more fine-grained settings?

I guess the main hurdle as I see it is that halos are considered in
disableProgrammerFacilities to be part of a programmer tools, not user ones.

Maybe adding a preference saying "my app is using halos" would do it.
Then in Morph>>#handleMouseDown: we could have something like


        (anEvent blueButtonChanged
                and:[Preferences cmdGesturesEnabled
                        or: [Preferences myAppUsesHalos "tmp name"]])
        ifTrue: [^ self blueButtonDown: anEvent].


Stef

i would like to use gestures to do rapid zooming

On Saturday, March 5, 2016, Stéphane Rollandin <[hidden email]> wrote:

Is anyone using gestures ?

What are gestures ?

Stef

Hi there,

I don't consider halos as being programmer-specific only. Any application can use it. I just recently tidied up "HaloMorph" and extracted the base class "SimpleHaloMorph." This should make it really simple for applications to use any custom halo for any specific morph in an application.

Best,
Marcel

On Linux, if you disable the #swapMouseButtons preference, you can use
Control + Blue-button-drag on a window to change its size.  In the
apropriate app, a good gesture for zooming too.

Use without Control key to move.

On Sun, Mar 6, 2016 at 10:59 AM, Kjell Godo <[hidden email]> wrote:

> I don't consider halos as being programmer-specific only. Any application
> can use it. I just recently tidied up "HaloMorph" and extracted the base
> class "SimpleHaloMorph." This should make it really simple for applications
> to use any custom halo for any specific morph in an application.

Fine, so we agree on that.

Now the practical question is how to have both halos and Ctrl handling
in Morph>>#handleMouseDown: where we currently find:


        (anEvent controlKeyPressed
                        and: [anEvent blueButtonChanged not
                                and: [Preferences cmdGesturesEnabled]])
                ifTrue: [^ self invokeMetaMenu: anEvent].


So the catch here is that I need Preferences cmdGesturesEnabled to be
true in order to have halos, but per the above test this makes my morph
unable to catch a Ctrl-event.


Stef