This might be a stupid question, but might it be possible for this new control to completely replace the existing image control?

There aren't very many special properties relating especially to images. If the new object implemented those at least to a first approximation, then perhaps it could simply be called "image". All existing uses of images would work, and the gloss would be that the image object had gained some exciting new capabilities.

Is this a mad dream?

On 03/11/2017 18:41, Mark Waddingham via use-livecode wrote:
On 2017-11-03 19:33, Rick Harrison via use-livecode wrote:
I like “vectorImage” too!

“Picture" has been used for images for a long time,
and we don’t want to add more confusion for users.

Where do you think the confusion would come from?

As I said one of the goals of this control would eventually be to replace the image object - so at some point (all being well) you will be able to do:

   set the filename of <insertcontrolname> "foo" to "foo.png"
   set the filename of <insertcontrolname> "foo" to "foo.gif"
   set the filename of <insertcontrolname> "foo" to "foo.jpg"
   set the filename of <insertcontrolname> "foo" to "foo.png"


   set the content of <insertcontrolname> "foo" to tPngData

At this point, describing the control as a 'vectorImage' might also seem confusing.

Warmest Regards,


use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription 

Reply via email to