24 Jul
2015
24 Jul
'15
4:23 p.m.
On Fri, Jul 24, 2015 at 3:41 PM, Alexandre Bergel <alexandre.bergel(a)me.com>
wrote:
Okey... I will resolve it on my side if it will annoy me long enough.
This was meant just for demonstration, because it's not complete yet ---
for example if you click on unrelated element (that doesn't have
RTResizable) it will not deselect it, and more. So the implementation will
still change... but if the current state is enough for you, then whatever.
I also assume that there is no way to intercept "all" clicks? I guess
TRMorph might now.
I think that
TRDrag* events should require that you are over the dragged
element with your
mouse, because now the behavior is that if the mouse gets
outside the element, drag events are still being fired. But maybe I should
fix this on my side.
All these event business is hard to get right. However, with Roassal3 (on
top of Bloc) this will all be much easier since BlMorph will be behind each
Roassal element. I therefore expect the morph to handle events in a much
better way than TRShape.
To better illustrate my point look at this
https://www.youtube.com/watch?v=4rHdiwGdr4s
When the mouse is completely out of the element
the resizing is still
occurring (because the drag event is still being applied),
and then compare
it to the behavior of resizing Playground -- there it happens only where it
makes sense.
Yes, it makes sense.
I haven't found any applicable example
directly in Roassal, but you can
look into my
smalltalkhub peteruhnak/roassal-contrib repo
(same as we used before for
moving stuff from dynacase)
at DCRTResizable>>example
Yes, this is an excellent example! I have also seen that you need to
connect the element to the view: if one click on the view, then the you
want to remove the handle. Bloc will offer this feature.
The previous class RTResizeable has been renamed as
RTSimpleResizable and
the class DCRTResizable is now called RTResizable. I have saved the package
with DynaCASE-Roassal2-AlexandreBergel.157.
Just a note, your previous class was called RTResizEable, with an extra
"e", so if someone used it it will break now. But I don't know if Pharo has
deprecation mechanism for classes. (The proper spelling is without the
extra "e" - resizable.)
Peter