At least LEO should alarm that file has changed and ask user to reload the project. Otherwise user can get unpleasant errors when he'll see the problem when a lot of job is done (and there'll arise a problem with merging what was overwrited and what was added)
пятница, 5 июля 2019 г., 1:18:37 UTC+3 пользователь Edward K. Ream написал: > > > > On Mon, Jul 1, 2019 at 1:57 AM gar <[email protected] <javascript:>> wrote: > >> Say I am working under the same LEO project on multiple computers syncing >> with GIT (or whatever) >> Say leo's project file changed remotely, and then I update it locally. >> I expect LEO to discover that and ask me what to do. >> But as I see LEO does not handle this and all I can do - close the >> project and open it again. >> Is that the only option to reload LEO project? >> > > Yes, that's the only way at present. I think I understand what you want, > but imo reloading Leo is the only safe thing to do. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/908b4b6e-bd3e-4f29-aba4-54d924e0c2e5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
