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: jctull on Jan 26, '05 12:12:20PM

Pages is plagued with the slow typing problem as well on my G4 TiBook (1 GHZ, 768MB RAM, 10.3.7). I have noticed this in general with Cocoa applications. Usually graphics intensive tasks cause massive slowdowns, generally when manipulating graphic items, but the typing thing may new.

For instance, in OmniGraffle, if you select some items, then try to move them via the mouse, the action gets super slow and almost appears to freeze. It is more efficient to move things by dragging with the mouse. But this makes simple moves along a single plane harder to do.

So my thinking has been that there are some problems with Cocoa rendering or a problem with Quartz, but this is only a guess. Regardless, it has been a sore point for me for some time.



[ Reply to This | # ]
Avoid a bad iPhoto5 'vanishing album' bug
Authored by: robg on Jan 26, '05 02:41:18PM

Odd; I haven't noticed a slow typing problem in Pages -- it keeps up with me, no matter how quickly I type. This is on my G4/1.33GHz PowerBook. What exactly are you seeing that you describe as slow typing? How long after you type do the letters show up?

I also haven't noticed any overbearing slowdowns in OmniGraffle; I can drag around 10 to 15 objects at once with the mouse with ease...

-rob.



[ Reply to This | # ]
Avoid a bad iPhoto5 'vanishing album' bug
Authored by: jctull on Jan 27, '05 11:55:10AM

Well, this was happening Tuesday evening on a newsletter I am putting together. I returned to the project yesterday and did not notice the issue, but I was not doing a lot of writing this time. Perhaps there was something else going on with my system, or it was occurring for other reasons not easily discernible.

I tested a large paste into Pages yesterday. I copied the text from Les Miserables by Victor Hugo from Project Gutenberg and pasted it into a new, blank document. It took about 3-4 minutes to process the paste. The text had forced line breaks, etc. I cut it and manipulated it in BBEdit to get rid of extraneous return carriages. (When I tried this in Pages, I got the spinning cursor for over ten minutes -- replace 2 carriage returns with 1 -- and force quit the app). The cleaned up document was over 1200 pages and everything seemed okay (1.3 MB file size). It took about 20 seconds to open with Pages not already open. If I go anywhere in the document and do rapid typing, the text falls behind my typing. This might be 60 wpm typing -- I am not a good typer. I will try to send you the document to play with.



[ Reply to This | # ]
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! :)

-rob.



[ Reply to This | # ]