That’s an interesting approach Matthias. Most of my customers save locally to their Documents folder. It’s just a few people using filer servers or Dropbox (iCloud, etc). I wonder, is there a reliable way to ascertain if the file is on a server?
Marty > On Jan 29, 2020, at 11:48 AM, Matthias Rebbe via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Hi, > i´ve ran into a similar situation a few months ago. This is what i´ve done. > > I´ve saved the stack to the local temp folder and then used the revcopyfile > command to copy it to the network drive. > When opening the app and that stack i used revcopyfile to copy the stack from > the network drive to the local temp folder and opened that copy of the stack. > So always the stack in to the local temp folder is used, but a copy is made > to the network drive everytime i save the stack. > This takes some time, but it´s acceptable and it works pretty well. > > - > Matthias Rebbe > Life Is Too Short For Boring Code > >> Am 29.01.2020 um 19:08 schrieb Marty Knapp via use-livecode >> <use-livecode@lists.runrev.com>: >> >> Thanks Richard. What would be considered a large file? In my case I would >> guess the average file is around 1mb though in some cases it could be up to >> 5mb. >> >> In some cases the user has been able to recover from the “~” file but not >> always. But it’s disconcerting to them that they never know when it might >> happen again. And it’s amazing how many people don’t have a backup plan in >> place. >> >> Marty >> >>> On Jan 28, 2020, at 6:12 PM, Richard Gaskin via use-livecode >>> <use-livecode@lists.runrev.com> wrote: >>> >>> Marty Knapp wrote: >>> >>>> I have an app in which users create documents (stacks) that auto-save >>>> when they're closed. I have a a few customers who are getting >>>> corrupted stacks every once in a while. At least in a couple of cases >>>> they are saving to a network server or over an internet connection. >>> ... >>>> Does anyone have any input with my shutdown routine? Ways of making it >>>> more robust? >>> >>> Save is save. One command triggers the engine's save routine. Hard to get >>> leaner than that. >>> >>> As a general rule, I would not advise saving large live documents over a >>> network, or to any folder managed by network sync (Dropbox, iCloud, >>> Nextcloud, etc.). Tons of warnings from software vendors all over the web >>> about things like that. >>> >>> Are the users able to recover from the "~" copy? >>> >>> -- >>> Richard Gaskin >>> Fourth World Systems _______________________________________________ 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
