Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Avoid a bad iPhoto5 'vanishing album' bug' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Avoid a bad iPhoto5 'vanishing album' bug
Authored by: robg on Jan 27, '05 12:36:49PM

Glad Pages handling of smaller documents went back to normal; I still haven't seen any issues with the 'typical' filesizes.

I got the file (and sent you a reply). That's a most interesting test; clearly it's beyond the scope of Pages' mission to handle something like that :). I was impressed that it did, but yea, I wouldn't want to work that way too much -- not so much the typing, as I found that acceptable. But searching, moving, replacing, etc. would all be troublesome.

Just for grins, I tried opening the same file in Word (I exported it from Pages to Word). Differences? Word took a *lot* longer to open the file for me, and then took a long time to repaginate it. Once I finally jumped to a spot in the text, though, typing was notably quicker than in Pages. But if I jumped around in the document, I then had another small delay before I could type at full speed again.

It's almost like Word somehow works on updating only the visible page in real time, then does the rest of the work in the background ... Pages, on the other hand, seems to update the whole document each time you type a letter.

Mainly, though, what I learned is the reason why I write my books with each chapter in its own file -- no word processor wants to work with that much data, and no author wants to LOSE that much data in the event of a bad crash! :)


[ Reply to This | # ]