Ah! So it does! Apologies for the bad info. .Jerry On Nov 24, 2012, at 4:24 PM, Peter Haworth <[email protected]> wrote:
> Actually, the dictionary entry for copy says: > > "If a destination card, group, or stack is specified, the *copy* > command<http://glossary/c/99.xml>places the > ID <http://dictionary/property/2074.xml> > property<http://glossary/p/391.xml>of the newly created > object <http://glossary/o/329.xml> in the > it<http://dictionary/keyword/1456.xml> > variable <http://glossary/v/522.xml>, and the appropriate > message<http://dictionary/keyword/1473.xml>is sent." > > Not saying it actually happens, just that the dictionary claims it should. > Looks like the workaround is have a newxxx handler to check for it. > > Pete > lcSQL Software <http://www.lcsql.com> > > > > On Sat, Nov 24, 2012 at 1:42 PM, Richard Gaskin > <[email protected]>wrote: > >> This is a known inconsistency. Most other commands that create objects >> put the long ID of the newly-created object into "it", but not copy or >> clone. >> >> I think there's a bug report about that somewhere in the DB... >> > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
