24 Jul
2015
24 Jul
'15
3:41 p.m.
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.
On another note:
I added methods for moving to RTLayoutTranslator for all sides, so you can probably move
it to Roassal if it looks ok to you.
Yes yes yes!
It is all in!
This is an excellent contribution!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.