tag:support.multimarkdown.com,2013-02-12:/discussions/problems-v4-ios/223-multi-app-editing-with-automatically-update-when-file-is-changed-by-another-programMultiMarkdown Software, LLC: Discussion 2019-04-05T00:19:56Ztag:support.multimarkdown.com,2013-02-12:Comment/471285092019-03-30T00:39:31Z2019-03-30T00:39:31ZMulti-app editing with "Automatically update when file is changed by another program" <div><p>Mark,</p>
<p>Thanks for writing.</p>
<p>The file merge code was based on the needs of the macOS app, and is one<br>
of the things that still needs fine tuning on iOS.</p>
<p>The original design was to merge changes made to the file while the<br>
macOS app was running (e.g. typically changes made on another device,<br>
but you can also use multiple apps at the same time to edit a file.)</p>
<p>iOS works a bit differently, and tends to disable/throttle background<br>
apps a bit more than macOS.</p>
<p>And as you note, iCloud is a bit of a black box when it comes to file sync.</p>
<p>If you're editing a file in multiple apps on a single iOS device, then<br>
the signal indicating that a file has been changed is probably not<br>
making it to the app, so it effectively gets ignored. I'll have to add<br>
code to check for changes whenever the app comes back to the foreground<br>
if there is an open file.</p>
<p>For now, the file merging should work reliably if you are working on the<br>
same file on multiple devices (e.g. Dropbox or iCloud files.) Or if you<br>
have two apps open on an iPad at the same time.</p>
<p>Dropbox should work ok even if switching back and forth between apps,<br>
since Composer can control dropbox sync. But iCloud is less reliable<br>
for this.</p>
<p>To use two apps simultaneously on the same file, open them using split<br>
screen so that both apps stay active. Any changes made by the other app<br>
should appear as soon as the file is saved (which doesn't always happen<br>
instantly since iOS likes to save on its own time. I need to add some<br>
triggers to force a save when the keyboard disappears for example, but<br>
closing the file forces a save.)</p>
<p>Fletcher</p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/471285092019-04-02T17:14:11Z2019-04-02T17:16:13ZMulti-app editing with "Automatically update when file is changed by another program" <div><p>Hi Fletcher,</p>
<p><br></p>
<p>Thanks for the details on what's going on under the hood, and confirmation of why I'm seeing differences with how the other apps behave.</p>
<p><br></p>
<p>I should have specified that my situation is all about changes getting updated when an app switch occurs, though: I am iPhone-only (and so was once again jealous to be lacking Split-View if this is already working for that). File writes do work immediately when switching to the background, though, so I get instant and reliable updates in the other app as soon as I've switched to it.</p>
<p>(If I used an iPad then I'd certainly be looking for saves on events like iOS keyboard dismiss etc. but then I'd also be using a hardware keyboard anyway - and would probably then be demanding a <em>Settings > Preview > Update preview whenever text changes</em> -level of save frequency for my Split View app too!)</p>
<p><br></p>
<p>My problem with the app-switch updates is only about the reverse trip: I guess from what you say that 1Writer/Textastic/etc must have specifically coded to check for file updates when brought to the foreground, and if you're going to do the same then my use case will certainly be addressed here.</p>
<p>At the moment I'm trying to remember to manually close the document before switching out, before opening it again after switching back (the Recent Files list from the latest beta helps a lot with all this!). The manual close is not to force a save (you're right that it does, but backgrounding will do so anyway), but instead to ensure that the file has to be reopened and read afresh (in order to notice the updates). Removing this requirement will be perfect.</p>
<p><br></p>
<p>And as for that original checkbox in the Settings... I hadn't even realised that this was file <em>merge</em> code... - so if there's any way that this can make its way from macOS to iOS then you might have a solution to one of the reasons many of us are still wary of cross-device editing with iCloud Drive ;)</p>
<p><br></p>
<p>Speak soon,</p>
<p>Mark</p></div>markotag:support.multimarkdown.com,2013-02-12:Comment/471285092019-04-04T01:11:11Z2019-04-04T01:11:11ZMulti-app editing with "Automatically update when file is changed by another program" <div><p>Mark,</p>
<p>Still some things to work on, but the newest build (pushed out a bit ago) should improve the cooperation between Composer and other applications if you are jumping back and forth between applications.</p>
<p>Thanks again for writing in!!</p>
<p>Fletcher</p>
<p>--<br>
Fletcher T. Penney<br>
Manager, Founder<br>
MultiMarkdown Software, LLC<br>
<a href="mailto:admin@multimarkdown.com">admin@multimarkdown.com</a></p></div>Fletchertag:support.multimarkdown.com,2013-02-12:Comment/471285092019-04-05T00:18:20Z2019-04-05T00:19:56ZMulti-app editing with "Automatically update when file is changed by another program" <div><p>Fletcher hi,</p>
<p>Certainly a nice relief to be greeted with a new TestFlight build this morning... with a full three months to play with now, but with far more than just an expiry reset in the release notes! But then to read in them that you have already implemented the backing file checks, I was over the moon...</p>
<p>There is a definite trap in the check that occurs when switching apps multiple times, and I'll write down the steps to reproduce when I get some proper time to isolate it - but tonight I just wanted to send my thanks for this particular work :)</p>
<p><br></p>
<p>And with this build I can also already strike off another of the requests I was going to make next... that of Xs Max support? Only took a moment to clock why the app suddenly felt more 'sharp' and 'solid'... I'm sure you've got lots of other plans for UI layout, but not being both zoomed-in and letterboxed would definitely have been worthy of a mention in the release notes for me!</p>
<p>And to read also of the background work underway on core components and to improve (again!?) the text engine performance, I think I'm as excited as you are!</p>
<p><br></p>
<p>Speak soon,</p>
<p>Mark</p></div>marko