name vs short name

Paul Dupuis paul at researchware.com
Thu Jul 4 08:12:28 EDT 2019


No it is not consistent, but some of the syntax was baked into Metacard 
long ago, often in response to some specific customer asking for a way 
to do some specific thing. Remember, Metacard was effectively a product 
of a single person.

For LiveCode to change it now would break far fr too many existing stacks



On 7/4/2019 6:03 AM, Klaus major-k via use-livecode wrote:
> Hi friends,
>
> this is on my mind for a very long time.
>
> put the name of img 1 -> image "xyz"
> put the short name of img 1 -> xyz
>
> However:
> set the short name of img 1 to "xyz2" -> compilation error, see below...
>
> We have to:
> set the name of img 1 to "xyz2"
>
> This does not seem logical at all to me!?
>
> Can someone please explain in a comprehensible (sic!) way why this is so? :-)
>
> BTW:
> Looks like the dictionary is wrong here (or am I missing something obvious?)
> Entry about name:
> ...
> set the [{ long | abbreviated | short }] name of object to string
> ...
> ?
>
> I tried:
> set the long name of btn 1 to "hello sailor!"
> set the abbreviated name of btn 1 to "hello sailor!"
> set the short name of btn 1 to "hello sailor!"
>
> And got "Compilation error: can't set this property..." in all three cases.
>
> Thanks a lot in advance!
>
>
> Best
>
> Klaus
> --
> Klaus Major
> https://www.major-k.de
> klaus at major-k.de
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>





More information about the Use-livecode mailing list