Actually you shouldn't have to change any of that. Even after setting the hcaddressing to false, you can still use the longer references to distinguish between same-named objects. So you could just leave the original scripts alone in those cases.
The same goes for backgrounds. Since it's an imported HC stack there will only be one background available on any card, and that's the one that will receive the message even if another background has a similar handler. An unplaced group won't get the message. So basically just leave those two cases alone and they should work. In any new handlers you write, you can go ahead and reference fields and buttons without bothering with the longer identifiers. On October 5, 2014 11:25:04 PM CDT, kee nethery <k...@kagi.com> wrote: >Yep. So two things I need to do are: > >1. Resolve any name duplications between card and background objects. >If I have card field “bork” and background field “bork”, getting it to >where I can remove “card” and “background” will cause issues if two >objects on the same card have the same name. > >2. Move all background scripts into the stack script AND make sure that >no two backgrounds have the same command or function name. If >background 1 has a “on bork” and background 2 has a completely >different “on bork” I need to alter the scripts that call bork to >distinguish between them. > >Thanks Jacque! > >Kee > > >> On Oct 5, 2014, at 1:18 PM, J. Landman Gay <jac...@hyperactivesw.com> >wrote: >> >> On 10/5/2014, 1:52 PM, Francis Nugent Dixon wrote: >>> Kee Nethery says that he wants to remove backgrounds in a stack >>> “to bring it into the modern era” Can anybody explain this statement >? >>> >>> What does this mean ? Is the background mechanism dying, or even >>> being dropped ? >> >> No, nothing has changed. I think what Kee meant was that he didn't >want to specify "card field" or "background button" when referring to >those objects. In HC that was required but in LC doesn't need those >longer references. You can refer to a card field just as "field" and LC >will still find it. >> >> The HCAddressing property controls whether card fields and background >buttons need to be referenced specifically by their owner locations. >All HC stacks are imported with HCAddressing set to true. If you set >the HCAddressing to false, the requirement no longer applies, and the >controls will be found just as they are in native LC stacks. >> >> -- >> Jacqueline Landman Gay | jac...@hyperactivesw.com >> HyperActive Software | http://www.hyperactivesw.com >> >> >> _______________________________________________ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your >subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > >_______________________________________________ >use-livecode mailing list >use-livecode@lists.runrev.com >Please visit this url to subscribe, unsubscribe and manage your >subscription preferences: >http://lists.runrev.com/mailman/listinfo/use-livecode -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
