I've been curious about what's different "under the hood" in
FrameMaker's Dropbox support. I see this sort of error regularly from
clients who use Dropbox as a file system. FrameMaker generally doesn't
"like" shared and network folders (it's rather intolerant of network
latency while saving), so I thought perhaps Adobe had adjusted FM to
save more reliably to Dropbox. Or perhaps not.
I don't recall seeing the error message about losing image data before
FM 2017. Does anybody know if this is a new message?
I regret that I don't have a solution, other than "Don't save directly
to a Dropbox folder".
-Alan
On 6/16/17 10:33 AM, Art Campbell wrote:
When following the instructions for working on files in Dropbox from FM 17,
I'm getting a herd of temp files saved with numeric extensions, and errors
displaying that the file I'm working on can't be saved. Also that the file
was saved but image data (Frameimage maybe?) was lost.
Anyone else using this feature and getting it to work seamlessly?
TIA,
Art
Art Campbell
[email protected]
"... In my opinion, there's nothing in this world beats a '52 Vincent and
a redheaded girl." -- Richard Thompson
No disclaimers apply.
--
Alan Houser
Group Wellesley, Inc.
Consultant and Trainer, Technical Publishing
arh on Twitter
412-450-0532
_______________________________________________
This message is from the Framers mailing list
Send messages to [email protected]
Visit the list's homepage at http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to [email protected]
