Well, Brian, here's what I've found out:
Files that are about 10 KB will work.
Files that are of a 3-digit KB size, forget it.
Frankly, I'm mystified. I guess the lack of RAM explains it.
But I find it rather ironic (and insane) that on a device that will play (or stream) a video file, which is HUGE, that OO can't handle something that's a mere few hundred KB.
I feel like I'm back in the 80s... At least that 300 KB file of mine would fit on a 5¼-inch DD floppy disk!
You say, "You should be able to find ways to make the new device useful in your workflows." Yes, I have: creating, editing, and using tiny, tiny outlines.
The more I think about it, the more I find myself scratching my brain over this. I use OmniGraffle on my iPad every day. Phenomenal app, and it has to be somewhat demanding because of the graphics involved. Yet OmniOutlines are merely text, so why the big RAM conflict?
Obviously I don't understand enough about the back end.
Files that are about 10 KB will work.
Files that are of a 3-digit KB size, forget it.
Frankly, I'm mystified. I guess the lack of RAM explains it.
But I find it rather ironic (and insane) that on a device that will play (or stream) a video file, which is HUGE, that OO can't handle something that's a mere few hundred KB.
I feel like I'm back in the 80s... At least that 300 KB file of mine would fit on a 5¼-inch DD floppy disk!
You say, "You should be able to find ways to make the new device useful in your workflows." Yes, I have: creating, editing, and using tiny, tiny outlines.
The more I think about it, the more I find myself scratching my brain over this. I use OmniGraffle on my iPad every day. Phenomenal app, and it has to be somewhat demanding because of the graphics involved. Yet OmniOutlines are merely text, so why the big RAM conflict?
Obviously I don't understand enough about the back end.
Last edited by santra; 2011-05-25 at 05:55 AM.. Reason: missed one of Bryan's remarks that I want to respond to
Threaded Mode