Or you can use an image instead as they happily handle SVG files nowadays…
:-Håkan
On 21 Feb 2019, 18:18 +0100, Tore Nilsen via use-livecode
, wrote:
>
> The simple solution was to «group» each individual SVG widget and add the
> grab me command to the group.
>
__
My mistake, I meant handles, not handlers. The widgets are used to display
chess pieces. The actual script «controlling" each widget/group is a behavior,
where the script itself resides in a button script.
Best regards
Tore
> 21. feb. 2019 kl. 18:36 skrev hh via use-livecode
> :
>
>> Tore w
> Tore wrote:
> Since my student does not need any handlers (in fact would not
> want any handlers added to the widgets) ...
That's exactly why I wrote ControlHandles: The approach doesn't
change any property of a control/widget.
Your approach does (grouping, scripting) ...
_
Thanks for your explanation. Since my student does not need any handlers (in
fact would not want any handlers added to the widgets), the examples from
«ControlHandles89» could not be used.
The simple solution was to «group» each individual SVG widget and add the grab
me command to the group.
B
On 2/21/19 7:02 AM, hh via use-livecode wrote:
Widgets are not ordinary controls.
So this is not a bug, rather a missing feature (the widget
author will have to implement an own "grab"-handler).
The widget passes mouseDown but not in a way that "grab" can
be used. MouseMove isn't passed (=> not u
Widgets are not ordinary controls.
So this is not a bug, rather a missing feature (the widget
author will have to implement an own "grab"-handler).
The widget passes mouseDown but not in a way that "grab" can
be used. MouseMove isn't passed (=> not usable) at all.
You could try "ControlHandles89"
When one of my students tried to use grab me command in a mouseDown handler on
a SVG widget, some strange things happened. In run-mode, the script did not
work as expected. The widget would not move with the mouse. When switching back
to edit mode, the widget started to move with the mouse onc
