Keynote storing obsolete format data, and possible connection to crashes
An “Ah ha!” moment with Keynote leading to a question about how it stores information regarding themes and fonts, and whether this is a bug in Keynote and/or if there is something that end users can do as a work-around. These points came to my attention today when I exported from Keynote to PowerPoint to share a (very inferior 😉 ) version of my presentation with a colleague. Note that the Keynote file I exported from has not exhibited any problems related to error messages or crashes.
(1) Prior to making the export, I changed all slides to Keynote’s standard out-of-the-box “Gradient” theme since I had used Keynote Theme Park animated “Global Cool” theme (www.keynotethemepark.com). However, even though no slide any longer contained the KTP theme, in doing the export Keynote created a media folder of movies that contained the animated KTP theme. So Keynote is apparently storing obsolete file data and not cleaning up its house after the file is changed.
(2) Prior to making the export, I changed all slides to use only fonts that I knew to be on my colleague’s PC. However, when I looked under the “Contents” tab of the resulting Powerpoint file’s “Properties” info, I discovered that Powerpoint was listing all the fonts that had been in the original Keynote file but that I had long since changed to Arial and Arial Narrow. Checking through the Powerpoint file slide by slide confirmed that the original fonts do not appear. Again, it appears that Keynote is storing obsolete information.
MY QUESTION: I am wondering if what I discovered today about Keynote’s “elephant memory” is indicating a bug of some sort, and if so, is there a reasonable work-around for end users that will enable us to avoid having files bloated with obsolete data.
Also, I am wondering if this storing of obsolete file data could be related to the ”missing file” error reports and Keynote crashes that others have noted in this forum and that I addressed in my previous post. The solution I had discovered was a file level work-around, but the question remained as to what had brought it on.
BTW, this is with Keynote 3.0.0 because I reinstalled Keynote recently thinking that this procedure might resolve the crashing problem described in my previous post to this forum; the reinstall didn’t, but the problem was solved at a file level in the manner described in my previous post. Now that I finally have time tonight to upgrade again to Keynote 3.02, when I run Software Update expecting to see the Keynote 3.02 upgrade listed, it’s not there. Hmmmmm.… I know I can get it from Apple’s download site but since the site lists two downloads (3.0.1v2 and 3.0.2), I thought it’d be better to let software update manage this process. Now I’m not so sure.
(1) Prior to making the export, I changed all slides to Keynote’s standard out-of-the-box “Gradient” theme since I had used Keynote Theme Park animated “Global Cool” theme (www.keynotethemepark.com). However, even though no slide any longer contained the KTP theme, in doing the export Keynote created a media folder of movies that contained the animated KTP theme. So Keynote is apparently storing obsolete file data and not cleaning up its house after the file is changed.
(2) Prior to making the export, I changed all slides to use only fonts that I knew to be on my colleague’s PC. However, when I looked under the “Contents” tab of the resulting Powerpoint file’s “Properties” info, I discovered that Powerpoint was listing all the fonts that had been in the original Keynote file but that I had long since changed to Arial and Arial Narrow. Checking through the Powerpoint file slide by slide confirmed that the original fonts do not appear. Again, it appears that Keynote is storing obsolete information.
MY QUESTION: I am wondering if what I discovered today about Keynote’s “elephant memory” is indicating a bug of some sort, and if so, is there a reasonable work-around for end users that will enable us to avoid having files bloated with obsolete data.
Also, I am wondering if this storing of obsolete file data could be related to the ”missing file” error reports and Keynote crashes that others have noted in this forum and that I addressed in my previous post. The solution I had discovered was a file level work-around, but the question remained as to what had brought it on.
BTW, this is with Keynote 3.0.0 because I reinstalled Keynote recently thinking that this procedure might resolve the crashing problem described in my previous post to this forum; the reinstall didn’t, but the problem was solved at a file level in the manner described in my previous post. Now that I finally have time tonight to upgrade again to Keynote 3.02, when I run Software Update expecting to see the Keynote 3.02 upgrade listed, it’s not there. Hmmmmm.… I know I can get it from Apple’s download site but since the site lists two downloads (3.0.1v2 and 3.0.2), I thought it’d be better to let software update manage this process. Now I’m not so sure.
2003 Powerbook, 15”, 1.25 GHz, 1.25 Gb RAM., Mac OS X (10.4.8), Looking forward to Keynote 4.
