It created a smartcrumbs folder which contained 1 .livecode.sc folder which contained 3 subfolders, medias, scripts and shareTexts. medias contained 1 images folder with 2,325 jpeg files. The scripts folder contained 22,006 livecodescript files. The sharedTexts folders contained 7,352 GUID ref’d folders with one or more html files as well as 7,462 separate html files. And that is all.
Having tried again using the Export button from the magicPallet (which, because of the delay between pressing the button and it actually exporting, should have a spinner or something to show its working on it) I get the same result but this time with nothing in the message box or any log file. I’ll try again but from the message box. The guide definitely says it will create a json file in each .livecode.sc folder that contains information about other objects and substacks. It doesn’t say we need to export each substack individually. But the json file should hold info about all the other stuff as well. We’ll see. Sean Cole Pi Digital Productions Ltd eMail Ts & Cs > On 31 Aug 2022, at 13:46, Brian Milby via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Had it created any of the script or other objects? Curious whether it > builds the JSON first or if it is done while exporting the other assets. > > Thanks, > Brian > >> On Aug 31, 2022, at 6:02 AM, Sean Cole via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> Well, I had to leave it overnight to finish exporting as it was clear to >> take some time. This was for just the main stack, not my long list of >> stacks. Looking at the message box this morning, though, has a response >> >> Message execution error: >> Error description: Object: object does not have this property >> Hint: >> >> 'Object does not have this property' ?? What property? Thanks LC for giving >> me all the information I need to fix it [shrugs]. It hasn't created the >> JSON file in the main .sc folder so it must have abandoned the operation at >> some point. >> >> I'll give it another go now after a reset and to another faster drive to >> see if that improves things but with no other info to go on I have no idea >> what needs to be done. >> >> 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. :-) >> >> Sean >> >> >>> On Wed, 31 Aug 2022 at 04:05, Mark Wieder via use-livecode < >>> use-livecode@lists.runrev.com> wrote: >>> >>>>> On 8/30/22 19:36, Sean Cole via use-livecode wrote: >>>>> just another 96 stacks to go. >>>>> Looks like I'll set up an automation script. >>> >>> Ouch! I think the library would do well to check the password status and >>> allow entering and cacheing the password as necessary. Too bad it's >>> closed source so we can't fix it. >>> >>> -- >>> 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 _______________________________________________ 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
