Import SVG with Multi-Path and Two colors
bobsneidar at iotecdigital.com
Thu Jan 2 19:50:17 EST 2020
An even better questions is, why can't an imported image have a file path property as well as a button? This is really where the file path SHOULD be. Think of it. We import an image. We create a button. We tell the button to use the imported image as an icon. We then tell the BUTTON where the IMAGE file path is! Wha???
As I have moaned about before, this has the effect of delinking any buttons copied from one stack to the other. Even when the image is ALSO coied, it gets a new ID, so the button link breaks. This makes groups of objects very non-portable. It may be better for me to not use buttons, and just use images, but there are reasons why buttons are better. For one, a button can have a different image assigned for different states eg. enabled, disabled etc.
I'll check the feature requests to see if this one has been put up. I am almost certain I have requested this in the past.
> On Jan 2, 2020, at 13:02 , Klaus major-k via use-livecode <use-livecode at lists.runrev.com> wrote:
> Hi all,
>> Am 02.01.2020 um 21:51 schrieb Sannyasin Brahmanathaswami via use-livecode <use-livecode at lists.runrev.com>:
>> Now, using Image As Control --> Image File [choose below in a file:}
>> it works. But it is not possibly to put this in the Path field, of the SVG icon.
>> So, Mark W. has done some magic in the engine for Import As Control, that is not possible in LCB/SVG widget.
>> This "image" will do the job. it is scales with no lossy pixels!
> yes, very cool!
> After importing that SVG file, it IS in fact an image object and we can use
> it immediatley as an icon in a button.
> But that raises the (naive?) question:
> Why do we have to convert a SVG widget with "drawingSvgCompile"
> to be able to use a SVG as an Icon in a button?
More information about the use-livecode