name vs short name

[Sean Cole (Pi)]

Klaus,

you are right! The dictionary entry is wrong.

It would not make logical sense to be able to set the short name of
something just as it is not logical to set the long or abbreviated name of
it. Hence why we have ONLY set the name of it. The 'short' keyword would be
superfluous.

But the dictionary should have the examples the other way round.

Sean Cole
*Pi Digital*


On Thu, 4 Jul 2019 at 11:03, Klaus major-k via use-livecode <
use-livecode at lists.runrev.com> 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
>