In 2.0 we will integrate the event refactorings we did to start to be able to
think about event dispatch.
Fernando built state machine on top of our enhanced events.
Fernando state machine idea for handling events is probably the way to go.
Stef
On Apr 19, 2012, at 8:19 PM, p...@highoctane.be w
Le 19/04/2012 20:04, Stéphane Ducasse a écrit :
> We have been doing it and we will continue. Now if you have concrete with
> examples suggestions
> please let us know.
It is not easy for me, it required long though on the matter.
One think I really really don't like is the use of symbol, becaus
Interacting with tablets and touch is indeed a different experience (just
inputting numbers properly is big - gestures would be great for example).
Longpress or double touch is also to be discussed. For editing a point,
you'd be better off with two fingers or a double touch.
I am experimenting wi
Hilaire
we should just continue and slowly but steadily fix and simplify.
We have been doing it and we will continue. Now if you have concrete with
examples suggestions
please let us know.
Stef
> Responding to myself as it may be useful to other:
>
>
> btn showSelectionFeedback: false.
Something for the next UI remake perhaps, with lessons learned.
Support for more "gestures" etc., long click being one... (am using a drag as a
substitute for those myself, in the meantime...)
Regards, Gary
Sent from my iPad
On 18 Apr 2012, at 10:32, Hilaire Fernandes wrote:
> Hello,
>
> Don
Responding to myself as it may be useful to other:
btn showSelectionFeedback: false.
btn changed.
but well.
Hilaire
Le 18/04/2012 11:32, Hilaire Fernandes a écrit :
> Hello,
>
> Don't know if any of you tried to use long click event with pluggable
> button.
>
> At first it lo
Hello,
Don't know if any of you tried to use long click event with pluggable
button.
At first it looks pretty easy, as:
btn on: #mouseStillDown send: #hello to: self.
does the job.
The hell is comming because btn aspect is changed but it states is not
changed. This is what I want but the aspec
