Re: name vs short name

> Am 05.07.2019 um 21:24 schrieb Klaus major-k via use-livecode > : > ... >> >> because... >> logical but wrong: >> set the name of button 1 to the name of button 2 >> logical but error: >> set the short name of button 1 to the short name of button 2 >> a cognitive leap but works: >> set the na

Re: name vs short name

Hi Mark, > Am 05.07.2019 um 21:20 schrieb Mark Wieder via use-livecode > : > > On 7/5/19 10:17 AM, Bob Sneidar via use-livecode wrote: >> If you can set the name and you get the same effect, why try to set the >> short name? > > because... > logical but wrong: > set the name of button 1 to the

Re: name vs short name

On 7/5/19 10:17 AM, Bob Sneidar via use-livecode wrote: If you can set the name and you get the same effect, why try to set the short name? because... logical but wrong: set the name of button 1 to the name of button 2 logical but error: set the short name of button 1 to the short name of butt

Re: name vs short name

If you can set the name and you get the same effect, why try to set the short name? The ling name is the full reference to the object using it's ID. Of course, you would have fits if you could set that to something different! The dictionary is obviously wrong, it should have used "get" not "set"

Re: name vs short name

Hi all, > Am 04.07.2019 um 14:31 schrieb Sean Cole (Pi) via use-livecode > : > > 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. H

Re: name vs short name

It is possible to make it an optional keyword though. set the [short] name of to Sean Cole On Thu, 4 Jul 2019 at 13:29, Klaus major-k via use-livecode < use-livecode@lists.runrev.com> wrote: > > > > Am 04.07.2019 um 14:22 schrieb Klaus major-k via use-livecode < > use-livecode@lists.runrev.co

Re: name vs short name

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 dic

Re: name vs short name

> Am 04.07.2019 um 14:22 schrieb Klaus major-k via use-livecode > : > > Hi Paul, > >> Am 04.07.2019 um 14:12 schrieb Paul Dupuis via use-livecode >> : >> >> No it is not consistent, but some of the syntax was baked into Metacard long >> ago, >> often in response to some specific customer a

Re: name vs short name

Hi Paul, > Am 04.07.2019 um 14:12 schrieb Paul Dupuis via use-livecode > : > > 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

Re: name vs short name

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 e