Hi Peter, Events are emitted by Trachel directly. Roassal does not emit event itself. But it can define callbacks for these events.
Being able to define multiline by clicking on a line is very valuable. go go go! And ask question if you are blocked. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Jul 31, 2014, at 4:26 PM, Peter Uhnák <i.uh...@gmail.com> wrote: > Addendum: generally when it comes to Mouse events, using TRMouse* events > should be the way to go? E.g. I want to add a control point when I click > somewhere on the line so I could subscribe for TRMouseRightClick > announcement. My question however is whether using TRachert events is ok. > Shouldn't this be handled at Roassal level as it was done in Roassal1 > (ROMouseRightClick)? > > > On Thu, Jul 31, 2014 at 9:58 PM, Peter Uhnák <i.uh...@gmail.com> wrote: > While playing with RTMultiLine I thought that it would be nice to have option > for RTDraggable elements to snap to a grid / move only by fixed increments - > for example the position could only be divisible by 10 (grid size would be > 10), so dragging from 20@10 to 26@4 would jump to 30@0. Is something like > this possible with current implementation? > > The second question is: is it possible for element to subscribe for position > updates of another element? (I.e. element A watches for movement of element B > and moves accordingly). I know I could add both of them to a composite shape > or RTGroup (RTDraggable>>groupToDrag:), however I would prefer something more > loosely coupled. > > In RTDraggable>>initializeElement: i found > " element when: TRMouseDragging do: [ :e | e element translateBy: e step. > e signalUpdate ]" > however it is commented out so perhaps there some other way? > > Peter >
