So all this discussion reminded me that I wrote an export/import stack some time ago. I definitely don't still have a copy on my computer, so I went looking on the web:
geoff canyon livecode export -- nothing useful, maybe it was in the runrev era? geoff canyon runrev export -- no luck. I remembered that I used XML formatting for the export. Something like XML Geoff Canyon export did the trick. 21 years ago? What?? Then off to archive.org to find the actual file: mcripper.mc And... I'm looking at my ancient history! I'm curious to try it on a large stack and see how it does. gc On Wed, Aug 31, 2022 at 9:10 PM Sean Cole via use-livecode < use-livecode@lists.runrev.com> wrote: > Yeah, I could really do with it giving me some feedback as to where this > object is. Actually, I could... > ... I just wrote a plugin for it. Use scCreatePlugin "","" (scCreatePlugin > on its own doesn't work from the message box like the dictionary suggests). > Then in the script I used > > global gLastObject > > on savingProperties pLongId, @pProperteis > --> your code > put "saving properties of" && pLongId into gLastObject > put word -2 to -1 of gLastObject > wait 0.01 millisec with messages > end savingProperties > > ---- > > Once I ran this it displayed which substack it was working on in the > message box and once it had failed the global showed me the last parameter > it had successfully accessed. Cool. But I still can't work out which > parameter of either that object (a standard text field) or the next (a > group with no behaviours or anything out of the ordinary as far as I can > tell). I'll come back to it tomorrow. It's silly o'clock now. > > Sean > > On Wed, 31 Aug 2022 at 17:13, Mark Wieder via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > On 8/31/22 03:00, Sean Cole via use-livecode wrote: > > > > > LC Team: :-) It would be REALLY handy if proper errors were thrown when > > one > > > occurs that can help us easily understand what the issues are. Also, if > > > prior to release documentation were gone through to make sure they are > > > legible. And if plugins released actually work as described. :-) > > > > Actually, it's even worse. > > The result is empty if no error occurred and "* successful" if it > > worked. To me that seems backwards. > > > > https://quality.livecode.com/show_bug.cgi?id=23911 > > > > -- > > Mark Wieder > > ahsoftw...@gmail.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 > _______________________________________________ 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
