CalendarMaker for OS X 
 |
For "How To" questions and answers, click here. Included in the How To articles is how to bring OS 9 calendars forward to CalendarMaker 5. |
|
|||
| v.5.0.4 | |||
| 1. | HOT: Update--Apple appears to have fixed this
problem in OS X 10.5.2. Critical bug found in Leopard Mac OS X 10.5 with applications that use Apple's Core Data such as CalendarMaker 5.0.4. READ THIS. If you save your file when you don't need to and then quit, you will lose all your calendar's data. While you're waiting for Apple to fix this problem or for us to find a work-around, you need to learn when not to save. The following is true of all OS X applications, though the problem only affects applications using Core Data (a particular portion of the operating system). The file below is not in need of saving because the red button does not have a black dot.  = don't
need to save, so do NOT save.The file below is in need of saving because the red button does have a black dot.  = needs
to be saved. The Quit command will instruct you to save as part of quitting.What do to -- if the file is dot-free, do not save and quit. CalendarMaker, as with all OS X applications, will not let you quit without saving if the file has the dot. There is never a need to do a separate Save command before quitting. You'll be OK if you just stop saving, unless the Quit command tells you to save as part of the Quit function. |
||
| 2. | CalendarMaker's import from iCal appears to be broken in Leopard Mac OS 10.5. We're trying to figure out what Apple changed. | ||
| 3. | Known Issues with CalendarMaker 5.0.4 (as stated in current ReadMe file). a) Fitting the calendar layout size or margins to the useable paper size or margins may cause the calendar to print on too many sheets of paper. You may need to manually adjust the layout size or margins. If you experience this please contact us with make and model of the printer you are using and the version of the printer driver software. [We have had no customer reports of this potential problem.] b) Color gradients will always draw 100% opaque when printing. c) Printing or exporting from an already saved document will mark the document as needing saving again. With version 5.0.4 we have removed from the list of Known Issues, "Event dates and times may need to be adjusted if document is used in different time zones." |
||
| 4. | Important: Version 5.0.4 informational note -- You will damage your calendar file if you open and save it using a version prior to 5.0.3 once you have updated it with version 5.0.4. Version 5.0.3 will prevent you from opening a 5.0.4 file. Version 5.0.2 and prior will warn you, but will not prevent you from opening and damaging your file. You should make sure that you don't have any versions of CalendarMaker prior to 5.0.4. | ||
| 5. | Warning: We have had a few reports (a very low
percentage) with both v.5.0.4 and prior versions of calendars crashing, not opening,
or opening with no data. The crash is not in the CalendarMaker application itself,
but in the database software that is built into the OS X operating system. To find
the cause we need to get a copy of the calendar file prior to the problem occurring.
We have a request, which is also a good suggestion. Please make regular back-up copies
of your calendar files. If you do get a crash you will have a recent back-up and
we may be able to duplicate the event and fix it. UPDATE: We found one of these problems.
See number 1 above. To do this, each time you save, locate the saved file on your hard drive. Click on it ONCE to select the file, then type a Command-D to make a Duplicate of the file. This will name the copy as "'your file name' copy" and then "'your file name' copy 1" and then "'your file name' copy 2", etc. Alternatively, you could name each of these back-up copies as follows--CM1-2007-11-08-PM06-15 where the digit after the CM is 1 for your main calendar file, 2, 3, etc. if you have multiple calendars. Then YYYY-MM-DD-(AM or PM)HH-MM. The important thing to remember is, NEVER open any of the back-up copies with the CalendarMaker application UNTIL after you have contacted us and we have advised you. |
||
| 6. | CalendarMaker (all OS X versions) fails to launch -- CalendarMaker 5 requires Mac OS X 10.4.3 or greater. | ||
| 7. | When switching from portrait to landscape, CalendarMaker will ask if you want to change your calendar layout size to the same as the paper. Normally the automatic adjustment will produce the correct result. If there is a problem, you may notice that a very slight portion of your calendar along either the left edge or the right edge did not print. If this occurs, open the Inspector to the first pane, Calendar & Layout Settings, and select the Layout tab. Try adjusting the Layout Size width downward two points and increasing the left and right margin each by one point. If the print area is still incorrect for your printer, repeat the adjustment of decreasing the Layout Size width by two and increasing both the left and right margins by one. | ||
| 8. | Certain printing problems have been reported with HP printers printing black as yellow
-- HP C6180 with Mac OS X 10.5.1 and Intel. HP C5280 with Mac OS X 10.5.1 and (not sure if Intel or Power PC). HP PSC 1317 with Mac OS X 10.5.1 and Intel. HP 7410 with Mac OS X 10.5.1 and Intel. If you have one of these printers, please contact us. We are particularly interested if you do or do NOT have a printing problem with these printers. This is starting to look like an HP problem with Leopard Mac OS X 10.5.1 and Intel. Let us know your printer make and model, your OS version, and your chip type (Intel or Power PC). Though this problem does not seem to affect all applications, it does affect many--not just CalendarMaker. To read an Apple discussion group on this problem, click here. (This and the next two links will open in new browser windows.) To read HP's comments for Photosmart and All-in-One products, click here. To read HP's comments for PSC 1310 series, click here. It appears that HP is not recognizing that there is a problem. Current hypothesis and work-around -- assuming that these printers will only print bit-mapped graphics, the following steps should allow you to print calendars until Apple and HP get this problem solved: Select Export As from CalendarMaker's File menu, then change the pop-up menu near the bottom center from PDF to TIFF, save with a temporary file name, then print this temporary file using Apple's Preview application, and finally trash the temporary file. UPDATE February 10, 2008: It appears that Apple's 10.5.2 and the related new HP driver have now fixed this problem. |
||
|
|
|||
| v.5.0.3 | |||
| 9. | Version 5.0.3 includes several revisions necessary for Leopard Mac OS X 10.5. It does not fix a problem with Picture browser. The Picture browser window contents will not show correctly which causes the Picture browser window to be unusable. We recommend for this version, 5.0.3, that you do not use the Picture browser and instead always use the Choose File button option when available. [This was fixed in v.5.0.4.] | ||
|
|
|||
| v.5.0.2 | |||
| 10. | In version 5.0.2 do NOT use the "Match appearance to entire calendar" button on the Grid Part Appearance pane of the Inspector if the selected item is already the same as the entire calendar. This will cause a non-recoverable crash. [This was fixed in v. 5.0.3.] | ||
|
|
|||
| v.5.0.1 | |||
| 11. | Version 5.0.1 (fixed in v. 5.0.2) The fixes made to importing in Version 5.0.1 fixed one problem and created a new problem. Version 5.0.1 does not like importing CalendarMaker 4 files that have "icons" in an event but no text. Version 5.0.1 will also not import iCal files. | ||
|
|
|||
| v.5.0 | |||
| 12. | Version 5.0 (fixed in v. 5.0.1) After using the Picture Copier it is a good idea to save, quit and relaunch. This will avoid an unexpected problem in another area of the application. The unexpected problem is the Picture Browser freezing (hanging). This is the Picture button on the toolbar. If this happens, it is just the Picture Browser that is frozen. You can still do everything else. The solution is to Save and Quit, then relaunch the program and re-open your calendar document. (If you think about it, you can avoid the problem by opening and closing the Picture Browser prior to using the Picture Copier feature.) | ||
| 13. | Version 5.0 (fixed in v. 5.0.1) There are two features that may not work properly
if the Picture Browser is not initialized. To initialize the Picture Browser click
on the Pictures button in the toolbar. Once the Picture Browser window is open, you
may close it. You have now initialized the Picture Browser. This step is necessary
(or at least highly recommended) before doing either of the following: a) Import > Events and Pictures From CalendarMaker 4 Calendar File, and b) Picture Copier (for importing pictures and icons from CalendarMaker 4 files without the events). |
||
| 14. | Version 5.0 (fixed in v. 5.0.1) There is a complex way to crash CalendarMaker when importing holidays. Import one batch such as General Holidays. Then "select all" in the Events List and delete them. Then import a different batch of holidays. Save and Quit. Then open the file and import General Holidays again. The application will hang in the import process requiring a "force quit." | ||
| 15. | Version 5.0 (fixed in v. 5.0.1) The menu command for setting the default characteristics of an event does not remember justification, such as centered justified. Also, if you select multiple days in the Event List, the justification choices are grayed out. | ||