This file is for Users who want to know every single issue and fix that have been applied in all prior interim releases. It is always a good idea to read the latest release notes on the version you are now installing.

New Features in V-3.7 - Official Release

• Addresses the issue of flaky network file transfers in DirectSync.
• Adds Master Template tag for better management of group templates
• Restores AutoSync . AutoSync can sync any number of desktops/devices running Pimlical Calendar either on demand or automatically at intervals using a cloud-based server such as Dropbox (Dropbox is supported via CloudRail that in the future will also seamlessly support OneDrive, Box, Google Drive, pCloud and Egnyte as well. Note that DirectSync is still fully supported as the preferred Off-Cloud sync option.
• Many more minor features and fixes - see Revision History below for details.

New Features in this Release:

• Includes improved error messages in Contacts and Memos Apps.

New Features in this Release:

• Works around CloudRail issue of not properly finding lock files in AutoSync, thereby allowing conflicts to potentially occur.
• Works around CloudRail issue of crashing with an Exception Error when AutoSync was invoked automatically from the AutoSyncFrequency preference.
• Fixes a potential problem where AutoSync icon could be left displayed after AutoSync had terminated due to some error condition.

New Features in this Release:

• On vCard import, now ensures that the ModificationDate field is set to the current date/time if the vCard does not specify that field. Also now avoids setting the ModificationDate/LastAccessDate fields to the current Date/Time on vCard import.

New Features in this Release:

• Adds new sort criteria to Advanced Find: Modification Date (Find Only). This allows items to be sorted by their modification date. For example, you could set up a filter called Recent which has this as the first criteria sorting in descending order: that would then list the very most recent edit/updates first, followed by all remaining items in reverse chronological order of when they were updated (handy to find where that last item was you changed, when you can't remember exactly where it was or what the text was).

• The two preferences, ContactCategoriesToSync and MemoCategoriesToSync are now properly managed with selection lists (previously, these preferences could not be accessed without error).
• The Set Default button now handles the default settings for StringList and StringsList type preferences (previously, this button did not set the actual default setting). For example, preferences like DefaultApptStatus, or AutoSyncOptions

New Features in this Release:

• The Purge routine in P/D has been completely revamped to work the same way as the Purge routine in P/A and considerably simplified as a result. Previously, there was considerable confusion as to exactly what happened with purging (vis-a-vis creation of a separate history database, vs. keeping records in the same database with a special status). Purged records are now always marked as deleted in the main database, and automatically merged into the default archive database (PimlicalArchiveCalendar.dat). 
• The Delete button in the Display Results dialog will also put deleted records into the default archive database if the preference: PutDeletedRecordsInHistoryDB is set to True (the default for that preference is false).

• Fixes some default settings for the SET DEFAULT button to match the default Preference file provided on installation.
• Fixes an obscure issue with V-3.6.03 fix for generating times for BEGIN:VTIMEZONE block on ICS Export function (wrong Olson Timezone designation/locale could get generated).
• Fixes problem of not auto-scaling user icons in the Tasks View (the new, larger icons were way too big for the Tasks View Display).

New Features in this Release:

• Ensures the Set Default button in preferences sets the new, correct, default value for the preference: AutoSyncPath.
• Made some further improvements in the auto-layout of the Edit Dialog vis-a-vis horizontal/vertical resizing.
• When AutoSyncFilePath is changed, Pimlical now automatically resets AutoSync Authentication (so a new login is performed to the new cloud server).
• When HomeTimeZone, CreateTimeZone or CurrentTimeZone preferences are changed, Pimlical now automatically re-initializes the timezone and DST rule tables.
• Now temporarily includes messages to advise the user that only Dropbox is supported as an AutoSync option.

New Features in this Release:

• AutoSync is now operational again, this time using CloudRail. At this point, it has only been tested using CloudRail to drive Dropbox, but CloudRail is supposed to seamlessly drive OneDrive, Box, Google Drive and Egnyte as well. Make sure the preference AutoSyncPath is set to the correct, default value of: CloudRail/Dropbox/PimlicalAutoSync/

• Restores the ability to resize the Edit dialog so that it can be resized when necessary (such as when a really LARGE font was used on an item that takes up more vertical space). Also restores proper horizontal sizing (the Action Tag dialog's scroll bar was at a fixed position requiring a VERY wide dialog in prior versions).

New Features in this Release:

• When generating the BEGIN:VTIMEZONE block in an iCalendar export file, Pimlical now properly includes the time field for the starting date/time of when the timzone took effect (usually defaulted to start of Unix Epoch: 1Jan1970 at 00:00:00).

New Features in this Release:

• Fixes issue of using Change button in Advanced Find to change the categories of items assigned to a Google Calendar, but only when the preference AssignPimlicalCategoryToGC is True (default is false) and when moving to just a local calendar category (Previously, could result in items not being properly moved and assigned a null uniqueID).
• When syncing with Google Calendar, now writes any custom Pimlical tags at the START of the Note field to be compatible with Pimlical/Android, and which also avoids under some circumstances creating  superfluous new line codes at the end of the note field.

New Features in this Release:

• A new Action Tag has been added (MasterTemplate) which can be used on a template to indicate it's a "master' meaning it will always be shown in the template list when the ShowAll button is set to only show one member of each template group. Also, the Show All button now ONLY hides items in sub-groups (previously if groups were not used at all and Show All toggled the display, it was puzzingly only displaying one template at a time).

• Ensures that DTSTART tag is generated in timezone specification in iCalendar output file for timezones that have no DST rule (previously, that tag was not generated). Since Pimlical does not maintain historical information for changes in Timezones (only for DST rules), a dummy date of 1-jan-1970 is used for the DTSTART tag. Some iCalendar import routines insist on seeing this DTSTART tag.
• The Special menu item: Restore Original Preference settings now also restores the System Preferences (previously, it only restored the User preferences) and the program now also exits and without writing the calendar (in case preferences are corrupt, it's safer to do that).
• Includes path to Alarm File in error messages concerning alarm system (to help diagnose issues where Java is complaining that it can't play an audio file).
• Significantly improves reliability of network transfers in DirectSync by utilizing a much smaller buffer size.

New Features in this Release:

• Fix for an obscure issue with repeat specifications.

New Features in this Release:

• Local Contacts Dialog  and Contacts Edit Dialogs now have titles (for Contacts: identifies App and also if the list is filtered, and for ContactsEdit the name (or company name) of the contact being edited).

• FIxes two anomalies in the Local Contacts Display when using filters and categories. First, there was an issue if All categories were selected after having deselected one or more categories. Second if a filter was invoked when not all categories were selected, the filter was being ignored.
• Avoids complaining about alarms set in the past if (a) it was a template being edited, or (b) there is at least ONE alarm set in the future.
• Fixes a new issue with setting a repeat date on the 31st of the month (this issue first appeared in V-3.5.01).
• Fixes a relatively new issue where the list of upcoming alarms might omit some items not being displayed in the current view.

New Features in this Release:

• Fixes a new issue in V-3.5.25 whereby category selection was not working properly in Menu | Options | Category Management.
• Changes the default Port number for network sync (PortNumberForNetworkSync) to 8139 as 8000 was an issue on some user devices due to it having been used by some spammers (which then resulted in that port number being blocked).

New Features in this Release:

• Adds preference from P/A, IgnoreAlarmsOnHiddenItems which can be set to TRUE to ignore the alarms on items that are hidden due to a preference or filter setting (Note that this preference in P/A previously only ignored alarms on items hidden because of the category they were in).
•  

• Fixes some issues in the method of handling timezones in the header of the exported ICS file for better compatibility with other third party apps (in particular, ALL timezones used in the exported file are now included in the timezone header information, and timezones that have no Daylight Savings Rule are now also exported).
• Includes fix (already in P/A) that if a timezone is added with no DST rule, it will properly pick up the first locale that has no DST rule and a matching offset (previously, it would add it as a new entry).
• Fixes an obscure issue where if a filter is set to either Higher or Lower for priority and the item has no priority at all, it might be displayed (if no priority, it should never be displayed if filtering by priority).
• Fixes several issues in AutoSync (file paths were not correct, wrong status was returned, Null Pointer Exception on overwriting empty contacts database, etc. - but ONLY when using a Network/File Path (instead of Dropbox) to sync desktops (network/file path is not supported by Android yet). Note that using AutoSync with a network path is still a preview feature at this point.
• Fixes messages in AutoSync to identify the target as "Server" rather than "Android Device" (AutoSync uses much of same code as DirectSync, so the prior messages were confusing when using AutoSync).
• Fixes a NullPointerException error in AutoSync when overwriting a completely empty tasks database.

New Features in this Release:

• Addresses an obscure error in an iCalendar Export file created by third-party App Timecase which failed to set up the Timezone header properly and which Pimlical (a) did not properly flag as an error and (b) then caused the event to not be imported as a HomeTimeZone event when the designated locale matched the HomeTimeZone locale.
• Fixes problem of the iCalendar Export File not generating the Timezone Header Information for every timezone used in the file (previously, it only output the home time zone).
  
• Fixes an obscure error in the Menu | Special | Import Date List routine whereby an extraneous, trailing space in the Repeat: specification would cause an exception error.
• Fixes a very obscure issue in preferences - if you manually enter a ridiculous value into a preference like DayStartMinute (that in Pimlical is set by a clock to prevent invalid values), you can not fix the preference in Pimlical because you get a NullPointerException when Pimlical tries to process the invalid time.
• Fixes the Days-till-due-date/Days-past-due values so that only past-due Floats with normal status use today's date as the reference. Otherwise, Floats now continue to display the number of days from the start date to the due date (so in looking at completed floats in the past, it continues to show how many days in advance (or late) the item was completed relative to its due date). Previously, completed floats in the past would still use today's date and show the completed float with a very large negative value.
• Fixes the name of Pimlical in Windows Task Manager (now says Pimlical Advanced Calendar instead of This is the main program etc.
• Fixes problem of not always selecting the correct contact in the LINKS dialog for the CALL button (could select wrong contact or cause a NullPointerException error).
• If the Import Date List feature encounters a category tag with no category specified, an error message is now generated (previously, this would cause a NullPointerException error).
• If records are found with Invalid DatabaseID's (Menu | Special | Display Record Counts shows records in the Other category), those records are now updated with the Local Calendar DatabaseID, and the record is identified in the regular Audit Trail (Pimlical_{OS}_AuditTrail.txt).
  

New Features in this Release:

• The upcoming alarms list which shows future occurrences of alarms on floating events (presuming they are not completed/canceled) now caters to the FloatDays Action Tag (previously, the upcoming alarms list would show such an event as having an alarm on a day that would in fact actually be skipped by the time that float caught up to that date). Note that there are other vanishingly small end-conditions that are not really feasible to manage for this list (example: you have a repeat filter which changes category selections or invokes a custom preference file, and the category that an item is in is now affected by the preference NoAlarmsOnTheseCategories or by the preference: IgnoreAlarmsOnHiddenItems (!).

New Features in this Release:

• Now also allows the use of the Delete key to delete the currently selected task in the Tasks View.
• Includes note in Registration dialog about uninstalling and reinstalling Pimlical to change the User Name (as this is a frequent question).
• Fixes an obscure issue with the use of groups and sub-templates when only non-group and primary templates were being displayed whereby a null pointer exception could be generated under some conditions and prevent the use of templates...

New Features in this Release:

• Fixes an of using the arrow (cursor) keys to move the highlight bar up and down in the Tasks Dialog. Under some conditions, pressing the Edit/Note/Delete buttons would reference the wrong task. Also fixes the issue of the arrow keys not working after canceling out of the Edit dialog from the Tasks dialog.

New Features in this Release:

• Fixes an issue with using the advanced repeat (Monthly by Date with a day of the week) to avoid advancing the date into the following month.

New Features in this Release:

• Fixes an issue in AutoSync whereby under some conditions it skips the sync because it thinks that nothing has changed (when it has).
• Now auto-refreshes the screen at the conclusion of AutoSync and avoids prematurely removing the AutoSync icon from the screen.

New Features in this Release:

• This corrects a 'show-stopper' problem for users still using the old Palm MDB databases on Java 7 - the code that normally writes out the calendar database was inadvertently left commented out in the V-3.5.15 release (!), so no items were stored in the database (only just reported now - as there are few users left on that combination apparently).
• Fixes an issue with the Birthday and Anniversary Action Tags, where a space could be inadvertently entered by the user and that space was causing the Android Java library to crash in P/A (Interestingly the Oracle Java library in P/D has no problem with that same code - but in case a future Java implementation used by P/D has the same problem as the Android version, this seems worth changing).
• Newly Created memos which are linked now use both the title as well as the uniqueID, so that links in events synced from Pimlical/Android V-3.5.14 or later are now also properly displayed in P/D (this change is backwards compatible, so existing memo links are still ok). Existing links to newly created memos are not retroactively updated - but if you go back and re-link the event to the same memo, it will now display the title in the memo selection list.
• Fixes an issue in AutoSync whereby under some conditions it gets invoked on every launch of Pimlical.

New Features in this Release:

• Fixes issue of being unable to edit the repeat parent of an irregular repeat series (was causing a NullPointerException error).

New Features in this Release:

• Includes a new preference: PortNumberForNetworkSync. A few users have run into cases where some other app is using Port 8000 for network access, or where an AntiVirus program found a virus trying to use port 8000, and then completely blocked that port from all applications. If you see an unexpected: IOException: Address already in use: JVM_Bind (this might, but not necessarily, be this problem). If you do change this preference, make sure you also change it in ALL devices that you are DirectSyncing to. Pick a number in the range 1024-49151 (probably try something nearby like 8399 etc.).

• Fixes issue in DirectSync no longer displaying the results of syncing the Memos and Contacts databases.
• Pimlical now fetches the DirectSync and AutoSync documentation directly from the Pimlico Website (previously, it was embedded in the program itself - with this change, the documentation can be updated dynamically at any time).

New Features in this Release:

• Adds new preference: TimeOfDayForAutoSync which if set to a value other than midnight (00:00) specifies a time of day at which an AutoSync is guaranteed to have taken place today (regardless of the AutoSyncFrequency setting). So if you set the AutoSyncFrequency to 1d, you can ensure, for example, that Pimlical AutoSyncs no later than 9am today by setting this preference to 9am.

• When AutoSync is invoked manually, Pimlical now skips the tests to see if the databases have changed - this addresses the issue of (a) immediately invoking AutoSync after making a change and having it missed, and (b) dealing with an unusually slow update on the dropbox servers.
• Fixes an issue in Local Memos and Contacts whereby the routine that detects and fixes duplicate ID's was not properly writing out the database with the corrected ID's.
• Updates the installer to include an information pane for a Windows Installation reminding Users to exit Pimlical/Desktop if it's running, and also to cover upgrading from a really old version of P/D, etc.
• If AutoSync is invoked manually, but no databases are selected in the preference: AutoSyncAction, Pimlical now complains about the configuration problem.

New Features in this Release:

• Fixes the default value for the ContactSort preference built-into the program - under some conditions when the preferences were being reset or re-initialized, the invalid value there could result in a spurious error file or dialog stating ERROR: Configuration Problem, Invalid setting for preference: CompanyNameOrder - that error message has now also been updated to reference the correct preference (ContactSort).
  

New Features in this Release:

• Fixes an issue with AutoSync erroneously skipping the sync stating that nothing has changed, when in fact something has changed in the local database (this can happen in the prior releases if the database is saved or Auto-saved after those changes were made).

New Features in this Release:

• Removes the restriction (that had already been removed in P/A), that if you tell AutoSync to Synchronize the contacts and/or memos databases and those databases were never created, then it automatically treats the Synchronize option the same as an overwrite from Server to Desktop and creates those databases. This eliminates the need to set the AutoSyncAction preference to overwrite if those databases don't exist.
• Changes default setting of DaysToKeepDeletedRecords preference from 7 days to 30 days as it is more likely that some users may not be regularly AutoSyncing some of their devices.

New Features in this Release:

• Sidesteps a Java drawing bug in the Day/MultiDay views (vertical bars redrawn wrong, etc.) when AutoSync is running (Java miscomputes the screen size and part of the screen is temporarily mis-drawn).  The fix is not 100% perfect, but with this fix most users will likely not even notice the minor mis-draw that remains.

New Features in this Release:

• Adds a new tag, <Short:xxxxxx> for the Import Date List command (Menu | Special) which allows you to specify the text to use for the Short Description field in a calendar record.

• Now avoids generating a spurious error file complaining about being unable to delete its own lock file when in fact there was no lock file to delete.

New Features in this Release:

• Pimlical/Desktop now supports purging old records into a separate history database when handling the new DAT format (no one had reported this issue after the database conversion took place). With this release, if you check the box to put the records in the history database, the records are placed/appended into PimlicalArchiveCalendar.dat (as they are in Pimlical/Android).

• The preference for handling the default sort for the Contacts database has been changed from CompanyNameOrder to ContactSort. This now matches the preference in P/A, and allows the preference to be set with a list option. Also, the local contacts database now properly obeys the 'Tempoary' and 'Permanent" sort criteria to match Memos and also how contacts are handled in P/A. Note that changing the order in the Contacts dialog now only changes it on a temporary basis. To set the permanent, default sort order, go into Preferences and set the value for the preference: ContactSort.
• Avoids NullPointerException error if you inadvertently attempt to Synchronize contacts when in fact the contacts database does not exist.
• Fixes issue of not displaying the summary dialog at the end of DirectSync if contacts and/or memos were also synced with the calendar.
• Fixes problem on iCalendar Export whereby under some circumstances, the date/time set in the tags: CREATED/DTSTAMP/LAST-MODIFIED had two 'Z's at the end of the UTC Date/Time Specification instead of one (i.e. a date/time was being exported as CREATED:20160723T063803ZZ instead of CREATED:20160723T063803Z). This was though an apparently a benign error as it did not affect the import of the file into any calendar application.
• Implements AutoSyncAction preference as in Pimlical/Android to control how AutoSync Operates. The default value is Synchronize, but it can also be set to Pimlical Overwrites Server or Server Overwrites Pimlical.
• Two new preferences, ContactCategoriesToSync and MemoCategoriesToSync have been added which parallel the function of the current preferences, ApptCategoriesToSync and TaskCategoriesToSync. Only those categories included in that preference will be synced. If the preference is blank, that is treated as if all categories are selected for syncing (To avoid syncing a database, use the AutoSyncOptions Preference).
• Popup Command Display Details now also manages tab stops embedded in text fields.
• When tapping the repeat specification in the Edit Dialog, the number of Future Occurrences is no longer displayed if the event has no explicit repeat end date (because there would be an infinite number of repeat occurrences). Previously, it reported the number of future occurrences prior to, or including, the last date in Pimlical's calendar (December 31, 2099).

New Features in this Release:

• Adds AutoSync. AutoSync can sync any number of desktops/devices running Pimlical Calendar either on demand or automatically at intervals using a cloud-based server such as Dropbox (in this initial release, only network-accessible devices and DropBox are supported). Note that DirectSync is still fully supported as another sync option. Make sure that the preference LatestUpdateAlwaysPrevails is set to True on all Platforms (older versions of Pimlical/Desktop defaulted to False, and that could cause floating events to be duplicated - since they would have been effectively modified separately on both platforms).
• The repeat legend in the Edit Dialog now displays the number of repeat occurrences prior to today and the number of repeat occurrences after today. These counts include exception instances to the repeat series and in the case of irregular repeat series (if the event was the parent of an irregular repeat series) all the child events of that irregular repeat series).
• Adds new item to the Special menu to reset the screen size/position tables. If changing monitors or screen configuration, use this option to forget the old screen/size configurations.

• Fixes an obscure issue on importing contacts from old Palm MDB Address database whereby the phone/email/address fields, while importing correctly, might not show up initially in the Contacts display list.
• Fixes incorrect title on dialog that displays list of duplicate id's when using menu | Validate Unique ID's in DB... Also updates that function to fix blank unique ID's and invalid database ID's.
• When specifying a duration value in preferences for a value that must be positive, Pimlical now automatically fixes the value regardless of whether the Before radio button was inadvertently selected.
• Fixes an issue in DirectSync related to the automatic importing of birthdays/anniversaries - namely after Direct/AutoSync, under some conditions, the birthdays/anniversaries imported from the contacts database would get lost and have to be re-imported.
• Fixes an issue of custom font names not always being reliably synced via Direct/AutoSync, due to an incompatibility in the way that font names were being handled under Windows Versus Android.
• If the preference CheckForNewSoftwareRelease is set to a value other than 0 (i.e. perform the check every X days), it will now skip the check if there is no network connection (previously it would display an error message if no network was available for performing the check).
• Fixes an installation problem on Windows XP and earlier windows-based systems using a language other than English (initial install dialog was not displaying in those circumstances).
• Fixes problem in memos that if you are filtering the display (say to only show recent items, deleted items or favorites, etc.) that if you exit the memos display and return to it while Pimlical is still running, the checkboxes do not reflect the current status of the filter (i.e. deleted records might display even though the Show Deleted checkbox was not checked).
• Fixes problem of losing the Only Show Next Occurrence attribute for repeat tasks when syncing tasks through a google calendar (this is not something that many users would be doing, which is why it had been overlooked for several years).
• Fixes a problem when syncing to a read-only calendar whereby certain exceptions to repeat series can cause repeated queries on every sync about deleting items in Pimlical that are no longer in Google Calendar.
• Includes updated DST rules for Israel (also corrects for the most latest information) that should be valid through about 2025. The online documentation for P/A now includes detailed information about the format of the Worldtimezones.txt file and explains how/why Israel (an unusual case) is setup the way it is.
• Provides more flexibility in handling timezones in iCalendar import (in particular, allowing custom tags inside the timezone definitions, and also ignoring redundant VALUE=DATE-TIME tags inside DTSTART/DTEND statements).
• If an attempt is made in the Edit Dialog to set the start date of a normal, floating event or task to a past date, a dialog now appears informing the user of the problem (you can not set a start date in the past on an active, floating event or task), and also suggests a workaround if the user want so take advantage of the right-click offset feature (see tip when hovering mouse cursor over button).

New Features in this Release:

• Fixes a problem in DirectSync when trying to do a sync overwrite from deskto to device and the device has either a completely empty memo database, or no memo database at all.
• Fixes an issue in reading Google Calendars (possibly on with Mac Java libraries) whereby corrupt entries (with invalid dates) could sneak into the Pimlical database and cause problems.

New Features in this Release:

• Fixes a problem in Menu | Special | Validate Unique IDs in DB, when there is no contacts or no memos databases (previously, Pimlical might try and read the old Address/Memopad databases and then generate an unexpected SQL database error).

New Features in this Release:

• Adds a Pencil icon to the Edit dialog underneath the Description label. If you tap that icon, Pimlical opens up a large edit window with the description field displayed (similar to tapping one of the Edit buttons for custom fields in the Advanced Pane).

• Fixes a reported NullExceptionError on Mac OS version when reading Google calendar and there are items in the database with no modification date set (this might be just a historical problem, and might not necessarily be uniquely related to the Mac OS version).
• When a new contact is created in the Local Contacts database, Pimlical now sorts the new item into the correct position (previously, it was left at the end of the list until the list was next sorted/displayed).
• Fixes an issue with how the uniqueID's are created in P/D vis-a-vis syncing items to P/A - in particular, P/D was still generating old style uniqueID's - which under some circumstances (such as managing irregular repeat series) could result in the link between parent and child events getting broken because P/A was modifying the uniqueID's for compatibility.
• Adds ifCategory command to template drawing routines - this statement is true if an item is not solely in the Unfiled category (you can also use ~ifCategory to test for an item that is only in the Unfiled Category). Use this statement to only display the category for an item if it is not in the Unfiled category.

New Features in this Release:

• Fixes an issue when switching to a different timezone table - in particular a table that no longer has definitions for entries in the current calendar database (or templates). This version ensures the calendar and templates are written first with the old table so that at least the timezone offeset is preserved (as well as the rule IF the rule is present in the newly imported table).
• Fixes issue with Irregular repeats whereby deleted instances of the irregular repeat series were still showing up in the Repeat Dialog as active instances.
• Fixes issue with Irregular repeats of not consistently retrieving all the pending field changes in the Edit dialog, prior to creating the irregular repeat instances.
• Fixes issue of the Edit dialog not consistently identifying an event as the parent of an irregular repeat series.

New Features in this Release:

• Fixes an issue in DirectSync whereby under some circumstances, the new preference DoNotSyncItemsPriorToDate was not filtering out items prior to the cutoff date from the file returned to Pimlical/Android (so the archived items would mysteriously "reappear"
• Fixes an issue in the timezone handling whereby under some circumstances, Pimlical would treat a Daylight Savings Rule as being in the Southern Hemisphere rather than Northern Hemisphere (so the on/off of DST would get reversed with the result that the resulting display timezone could be off by one hour in the wrong direction).
• Fixes an issue in the use of the entire 450+ Olson Timezone database whereby the file was not being copied to the correct folder for installation.

New Features in this Release:

• Uncaught Exception Error files now have the proper .error extension (prior versions were still using a .txt extension).
• DirectSync now specifically checks that the calendar database being read from P/A matches on the major and minor versions and will put up an error message if they differ.
• In the initial install dialog, the checkbox indicating that you are still using the old Palm MDB databases is now always displayed if you are using a version of Java prior to Java 8 (previously, that checkbox was only displayed if you also checked the box to reinitialize preferences, but that was not really intended). Note that you must check this box in order to have the preference SynchronizeWithPalmOS set to true (otherwise it will be set to False).
• Includes an obscure fix covering recurrence rules in iCalendar format that have been created by some calendar applications (and which could potentially cause a read fault on the calendar).
• Restores behavior of prior V_3.3.8 that pressing ESC key unselects any selected items in display.
• Ensures that any changes to category settings get written out when the OK button is tapped in the Category dialog (this was only an issue when running on Mac OS and user invoked the Quit PimlicalApp menu command from Finder (which bypassed the normal close sequence in Pimlical).

New Features in this Release:

• Fixes issue with the ShadedDates preference. Pimlical/Desktop now manages this in the same was as Pimlical/Android. The ShadedDates preference now only handles the dates to be shaded - any color specification from past installs (if present) are ignored. To set the color to use for the Shaded Dates, use the preference: ShadedDatesColor in the [Colors] section of preferences.

New Features in this Release:

• Adds new Query dialog when importing icons that allow more control over the icon import (if duplicate icon ID's are found, you can now either (a) assign a new, unique ID, or (b) skip that icon).  Also, some 100 new icons have been added to the icon collection (and yes, a future release does plan to organize the icons for more intuitive access - most users do not choose to re-organize the collections themselves, so obviously that would be helpful to those users).

• Fixes an issue with installing on older Windows XP systems whereby Pimlical's initial install dialog was not displaying and error messages like Wrong number of system icons or Preference object in cache is of wrong type etc. were occurring).

New Features in this Release:

• Adds Backup button to the preference dialog to force the backup of all preferences (this will write out the backups regardless of the MaximumBackupFrequency Preference and when the last set of backups were taken).

• Fixes issue on Linux versions where the menu | Help | Reference Manual... command was failing because of case-sensitivity in Linux systems on the filename for the manual.
• Works around new bug in Java (perhaps windows version only?) whereby pass-word protected memos (with the password feature enabled) were being displayed even if the user canceled out of the password dialog.
• Fixes issue of the Backup/Restore of preferences still referencing the old PimlicalDBs.dat filename instead of the new SystemPreferences.dat filename and not properly creating backup copies of preferences.
• Fixes an issue whereby Pimlical was encountering a NullPointerException when writing out the new SystemPreference.dat file.
• Adds more robust error checking for corruption in date/times of events and fixes them.
• Clicking on the [X] at top right of the Installation Dialog now acts as if the OK button was hit - previously, a user doing this would end up bypassing the installation of new files (and could result in an error message about the wrong number of System Icons, or other installation-related problems).

New Features in this Release:

• Fixes an issue with the new preference DoNotSyncEventsPriorToDate whereby an answer of Yes on an overwrite from Android to Desktop  (which should preserve items in the desktop database) was under some circumstances causing the items to be deleted anyway.

New Features in this Release:

• Incorporates some fixes for installation defaults and some other issues raised in only very obscure configurations.

New Features in this Release:

• DoNotSyncEventsPriorToDate preference now queries user if they want to preserve items prior to the cutoff date when overwriting from Android device to desktop. A response of  Yes will preserve items in the desktop database prior to the cutoff date, while a response of No will result in a complete overwrite.

New Features in this Release:

• Fixes an issue in new preference: DoNotSyncEventsPriorToDate, whereby items archived in P/A were apparently still causing the items to be removed from P/D, even though they ended prior to the preference's cutoff date.
• Now displays an appropriate error message if an invalid filter name is typed into the preference: StartupFilter (previously, no error message appeared and Pimlical just switched to using the Default filter).
• When exiting, the normally empty Runtime_Errors_Windows_XXXX.error file is now properly deleted. It is only preserved if an error condition was written into it (Note: this works under Windows, but may not work on Mac OS or some Linux distros).

New Features in this Release:

• Implements new preference: DoNotSyncEventsPriorToDate (which was actually documented in P/A help file in description of menu | Archive function, but not implemented till this version). This sets a cutoff date for syncing items - any items in P/D that end prior to this cutoff date (i.e. a non-repeat item with an end date prior to the archive date, or a repeat item with an explicit end repeat date that ends before the archive date) will be ignored in both P/D and P/A. This makes it possible to keep old archive items in the current P/D calendar, while keeping older items in a separate archive calendar in P/A, where it is desirable on slower devices or devices with limited memory to keep the current calendar as small as possible.

• When syncing with Google Calendar (via Android Calendar), exceptions to repeat series are now treated in a manner identical to how Pimlical handles them - in particular, the exception is not considered to be part of the repeat series with respect to modifications made to the repeat series itself. So if you modify the repeat series, any exceptions will not be updated (there are arguments that can be made on both sides of how to handle this condition, but for Pimlical users, it's probably more important to handle exceptions through google calendar in a manner consistent with how Pimlical has always handled exceptions). This also fixes some issues in prior versions with unexpected duplications or omissions of instances of a repeat after exceptions have been made.
• Fixes a sync problem related to a repeat floating event that had been created from a non-repeat instance of a repeat floating event - in particular, there was an internal field that links the non-repeat instance to the original repeat float that was not being cleared out, and so the repeat float was getting confused with a repeat instance. The symptom (which may be easier to understand!) was that a floating event would mysteriously re-appear even after being deleted or marked as completed, after a sync.

New Features in this Release:

• Fixes an upgrade issue involving System Preferences where under some conditions, Pimlical will not read the old PimlicalDBs.dat file with the result that system preferences get re-initialized (if you had this issue previously, delete SystemPreferences.* and relaunch Pimlical).
• Fixes issue of iCalendar import not managing entries where the end date appears before the start date, and where the start date appears after a repeat specification which included exception dates.
• Fixes issue of iCalendar import discarding events with duplicate ID's, when in fact with some calendar apps, those events were actually just created as reminders (with a custom tag for that calendar app). This version now re-assigns a new UniqueID to those events, as otherwise, if the reminders appear BEFORE the actual repeat series, the repeat series itself would have been discarded as a duplicate event. Also the skipped events were only mentioned in the summary message in Debug Mode - now they always are mentioned.

New Features in this Release:

• Fixes issue of not properly recovering after the removal of null entries in the calendar database (prior versions ignored this issue, but 3.4.8 removes them - but not in the best way - this release leaves the null entries and puts a default message into the description field - that way the program also recovers properly.
• Fixes issue of program still using PimlicalDBs.dat file on new install (rather than new SystemPreference.dat file). 
• Fixes issue of losing the checkmark on monthly repeats of appointment types only in a filter.
• Fixes NullPointerError that can occur under some relatively rare conditions when writing SystemPreferences.dat file.
• Fixes an obscure read error on the local calendar (related to timezone setting).
• Fixes issue on Completely clean installation of not using default sizes for the resizable dialogs (Preferences, Display Results, etc.).
• Fixes issue on completely clean installation of getting spurious error message about the old Palm Databases.
• Fixes issue on completely clean installation of not properly checking for both SystemPreferences.dat as well as PimlicalDBs.dat when setting up the checkbox for re-initializing that file (should only be checked if both files are missing).

New Features in this Release:

• Import All button in Menu | Options | Change Timezone now imports some 400+ Timezone definitions covering the entire world (this is the complete Olson Database of timezone definitions). The Timezone routines now permit any number of locales even if the definitions are functionally identical.
• In the Month view, clicking on a day in the main view now updates the selection day in the left navigation pane to show the selected day.

• When syncing items back and forth, Pimlical now avoids confusion over the Google/Android calendar prefixes used by Pimlical (A_ and G_) and ensures they are identical on each platform (previously, the G_ prefix could appear in P/A and that could cause an entry for the G_ category in category lists, etc.).
• In the Edit dialog, the repeat button now also indicates if the current repeat series has any exceptions present.
• Updates the message in the About dialog to specifically look for error files that have a .error extension (previously, error files had a .log or .txt extension, but that was causing confusion with other files that were not error files).
• In the Day+ view, when day is changed by tapping on a different day, the date navigation pane in the left panel is now also updated.
• Fixes new issue in recent interim release whereby a floating event with a due date in the future, but which was past-due, would appear in today's schedule rather than on the future, display Date.
• Fixes an obscure issue in DirectSync with floating events that should eliminate the issue that just a few users have seen with a rogue floating reminder that keeps on mysteriously re-appearing in P/A immediately after syncing with P/D.
• Fixes a problem of potentially writing preferences to a custom preference file no longer in use (problem was that name would be used IF the preference file existed, even though the filter was no longer marked as having a custom preference file).
• Speeds up launching and exiting of Pimlical by rewriting all the prior java-based routines to read and write the PimlicalDBs.dat database with optimized, custom routines (the PimlicalDBs.dat file can still be read, but it is now written and re-read as SystemPreferences.dat). This change was primarily made so that the SystemPreferences.dat file is compatible between the Desktop and Android versions. Filters are now written with a .FLT extension (when importing filters, the file open dialog will display filters in both the old format (*.FIL) as well as the new format (*.FLT). 

New Features in this Release:

• Speeds up selection of repeat exception options by providing separate buttons in the Repeat Exception dialog along with graphics.

• The icons that identify past-due floats and tasks (circle and square respectively with an exclamation mark inside them) now respond to a direct click in the main view in the same way as a click on undated floats and tasks (i.e. it marks them as completed) - previously, a tap was bringing up the edit dialog. Also, a right-click on any of those icons brings up the Date picker to assign a new date to that float or task (this has always been true, but apparently may not have been documented).
• Sets button insets to zero in the Contacts dialog of just the Mac version because Mac buttons are always too big and this bring width of dialog down significantly to work better for lower resolution Mac screens.
• Fixes an obscure issue in Google Sync: if you have a read-only calendar that for some reason Pimlical would normally update (if it were read/write) and this is immediately followed by another calendar that is not read-only, then you can potentially get a (benign) Forbidden error message from Google. This could also result in some other obscure error messages, such as the complaint that items were being updated in more than one calendar (another thing that has been reported by a couple of users in the past year or two).
• Fixes problem of not providing the correct Olson Database definition for events in UTC (was picking up a comment in the Worldtimezones.txt file) which would result in a complaint from Google when creating/updating an event with times set in UTC.
• If the local calendar is completely corrupt and the cache file is also corrupt, Pimlical now renames PimlicalLocalCalendar.dat to PimlicalLocalCalendar.bad - that way at least Pimlical will start up with an empty calendar, and the user can restore the calendar from the Backup menu, or using DirectSync to restore from Pimlical/Android's calendar.
• The feature of restoring the locking of the due date to the start date was only partially re-enabled in prior versions when the preference LockDueStartDateOnTasks was set to true (the due date was locked to the start date). When set to true, this version now also locks the Start date to the due date. Note that this does not require the SAME setting for the due date and start date - it merely ensures that any change to the due date OR the start date preserves the same interval between the start date and the due date.
• In the weekly view, the down-arrow drawn at the end of the line to indicate there are more items to display on that day for which there is not enough room is now better positioned (previously, it was so close to the right end of the line that the down-arrow was scarcely visible).
• Fixes problem in Local Contacts view of not displaying an item when filtering a display for a text string and filtering by category when multiple categories were present (in either the selection list of categories, or the assigned categories of the item) and the multiple category lists did not perfectly match (for example, you had three selected categories for display and the item with the matching text string was in only two of those categories). Also corrects a problem of not displaying an item when filtering by text string and just displaying the Unfiled category and the item was in the unfiled category.
• On iCalendar import, Pimlical/Desktop now matches import in Pimlical/Android which avoids reading items with UniqueID's that already duplicate existing items in the database (this assumes the iCalendar file uses the UID tag).
• Avoids a spurious query about saving the preferences stating that a change had been made when in fact no preference had been changed.
• Fixes problem of not being able to change the custom label for custom field 9 in the Local Contacts dialog.
• Redesigns both the Local Contacts and Local Memos Dialogs so they fit on smaller screens (especially for Mac's with smaller screens as the java layouts tend to be a lot sparser than Windows/Linux).

New Features in this Release:

• Fixes new in 3.4.05 issue of memos not getting synced properly into the desktop memos database (which in turn causes the memos to disappear from the Android memo database.
• Fixes issue of Google Sync running really slow - this was caused by the new, comprehensive logging of the sync which is supposed to only be done when the preference DebugMode is set to true, but in fact was always being done regardless. DebugMode should not normally be left set to True - it's usually only set when trying to track down some problem.
• Adds the three icons for irregular repeats, and an exception to a regular and an irregular repeat series (now matches Pimlical/Android).
• Legend in repeat dialog now includes a count of the number of irregular repeats that were generated from a repeat parent.
• Fixes problem of children of an irregular repeat parent sometimes being marked as an irregular repeat parent themselves (problem was more obvious with the new system icons).

New Features in this Release:

• Fixes new problem of the installation dialog appearing every time Pimlical is launched (on Mac and Linux versions only).
• Shrinks the sizes of buttons in the contacts dialog so the screen fits on an 800x600 display (also looks better on Mac).
• Displays the last modified date/times adjusted to the current, local timezone rather than in UTC in the messages and Sync log.
• Fixes an issue in reading google calendars with the preference UseGoogleExtendedProperties set to true, and having extended properties inserted by some other calendar application with a private designation, when there was no shared property present - this resulted in a NullPointerException error, and the event in question was not read).
• Fixes an issue in DirectSync of handling memo conflicts - the conflicting memos are now properly written to both platforms if the preference LatestUpdateAlwaysPrevails is set to false.
• Fixes an obscure problem with the Only Show Next Repeat feature when the repeat event in question is in a different timezone that would cause the event to shift into a different day (in such cases, the event might have previously shown on the Next or prior instance rather than the current instance).
• Switching the DebugMode preference is now immediately recognized (previously, it might not be acted on right away by Pimlical).
• Ensures that all the logging information previously only recorded internally is now put in the GoogleSyncLog.txt file if the preference DebugMode is set to true.
• When syncing with Google Calendar, if the event was deleted in Pimlical after the last modification to the event in Google, then the event is deleted from Google (previously, if the event had been modified in Google calendar after the calendar was last synced, the Google event would replace the deleted Pimlical event).
• Pimlical now generates comprehensive log of the sync with Google Calendar (if DebugMode is set to true) to help diagnose any syncing issues.
• Fixes an obscure issue with exceptions made in Google calendar and synced to Pimlical - previously, the exception would generate a duplicate ID in Pimlical and could subsequently result in the exception getting unexpectedly deleted. Pimlical now forces Google Calendar to manage exceptions in a manner that is compatible with Pimlical to avoid that issue.
• Includes a warning note in the Review Exception Dates dialog (where you can remove exceptions to repeat events) when a google calendar is being handled as due to a limitation in Google calendar, it is not possible to remove exceptions that were created in Google calendar in this dialog (you have to undo exceptions made in Google calendar in Google Calendar).
• On a past-due floating event or task, the number of days shown as past due (in brackets) now properly reflects past-due from todays' date (previously, it was showing the number of days from the display date).
• Fixes an issue with the 3rd/4th5th alarms not being properly recognized in the up-coming alarms list and not consistently triggering alarms.
• Fixes an issue with a past-due repeat task with a display date in the future - such events now will appear in today's schedule and also cause any alarms associated with them to go off on today.

New Features in this Release:

• Adds new preference (although this was in P/A previously): DefaultBackgroundColor - this defaults to White (which preserves prior behavior) but can now be used to change the default background color in all views).
• Scan for duplicate ID's in Menu | Special now scans the new contacts and memos databases for duplicate ID's (and assigns new ID's to duplicated items).
• RGB Slider dialog now allows you to tap the button displaying the numeric values and enter the values directly from the keyboard (much faster than fiddling with a mouse when you know what values you want to use).
• Installer now supports installing under a standard Windows Account. Previously, attempting to install under a standard account ran into problems because the Install Dialog never appeared and as a result, files were not updated, and a clean install would fail. Of course, the installer still has to require you log in as an administrative user (because standard users have no access to C:\Program Files....).

• Cleans up the resolution of conflicts in the Calendar database (when each matching item was independently modified after the last sync) to match how memos and contacts are handled. First, the old preference SyncCalendarPrevails is now ignored in favor of using the preference: LatestUpdateAlwaysPrevails. If set to True, then the conflict is automatically resolved in favor of the item that was most recently updated. If false, both items appear in both databases and a notation is made on the sync log of the conflict. Also includes much better logging of the synchronization process to help diagnose issues.
• Fixes an issue in DirectSync, whereby the date/times of the last sync for the calendar, memos and contacts databases was inadvertently being adjusted to the current time zone - that date/time stamp (like the creation and modification date/time stamps) should always be recorded in UTC. This could have caused some obscure issues previously with memo or contact items not being recognized as conflicts (if the user's current timezone was East of GMT) or some items being spuriously identified as conflicts (if the user's current timezone was West of GMT). I.e. if the modification was made within X seconds of the last sync, and the user's current timezone was more than X seconds distant from UTC, there would have been a potential issue.
• Adds support for nickname in local contacts (present on Pimlical/Android - inadvertently omitted on Pimlical/Desktop in prior versions).
• Fixes problem in new memos and contacts databases of creating a new item and then updating it before the database was ever written (such as by hitting the DONE button in memos) - problem caused was that (a) the updated information would be lost and (b) a spurious error message would be generated.
• Fixes problem of launching custom run-time commands from custom alarms (i.e. using the Exec button) - problem was that the newly-introduced {Desktop}-{/Desktop} tags which are used to separate out platform-specific custom alarm/command strings was not being stripped out of the command prior to submission to the operating system. This feature (which has always been in P/D) allows you to launch ANY application or data file (which in turn should launch the associated application) by checking the Exec checkbox and selecting a file (you can also right-click the field to edit it manually - this would allow you to enter a web-browser address etc. to open a web page when the alarm went off, etc.). Also avoids trying to execute the command string as an alarm file if the Exec checkbox has JUST been checked.
• Fixes problem of the left pane in main views getting clipped when a new alarm appears with a longer description - this was a java bug, but it's now side-stepped by automatically truncating the text to fit the existing size of the label, thereby avoiding the layout change (what should have happened in the prior version is that the split-pane would be resized and redrawn to accomodate the longer text, but truncating seems like it's obviously better).
• Fixes problem of trying to access the new contacts database even if the preference SynchronizeWithPalmOS is set to true (provide that is set to true and java 7 is installed, Pimlical will use the old Palm Address.mdb database).
• Updated preference note to indicate that the preference EditDialogQuickReturn also applies to using poup commands on the event selection list (i.e. if you delete an item using a popup command, the program returns to the main view rather than just updating and re-displaying the event selection list).
• Fixed the default call template (setup for Skype) so it now works with the latest release of Skype (Skype requires country code, so this default command string provides +1 for USA numbers). This command string though would normally have to be customized by the user for their particular use).
• Fixed cosmetic issue with the pinned dates list (the dropdown box was not always auto-sizing itself properly to display the dates, and it was not being hidden on startup if there were no pinned dates).
• If the preference or calendar file rename fails (Anti-virus software or perhaps windows indexing?) steps in and locks the file that Pimlical is renaming, thereby causing the rename operation to unexpectedly fail (!!) - Pimlical now attempts to rename the file again in one second (at which point the intefering task should have hopefully finished interfering!).

New Features in this Release:

• Fixes a cosmetic display issue in Day/Day+ views that if some large, custom fonts are displayed for events, the scroll bar appears and in just a few cases the last end-of-line icon can be hidden underneath the scroll bar.
• When installing Pimlical/Desktop to support really old, legacy Palm devices (that you have to use PalmHotsyncSetup.exe for so you can switch the file extensions to .DB from .MDB), Pimlical now checks to see if the old legacy .DB databases are present and if they are, avoids copying in the empty MDB databases into those folders).

New Features in this Release:

• Fixes problem of displaying record count when the memo database is completely empty.
• Fixes problem of not applying permanent sort to memos when memos are first displayed (although the drop-down list was properly updated to reflect it).
• Names of Audit trail file now appears as Pimlical_Windows_AuditTrail.txt (or Pimlical_Linux... etc. - Making filenames in a consistent format across platforms).
• Error files now all use a .error extension so they are immediately distinguishable from other files (previously, it was .txt then .log but those are also both used for other purposes). Also the error filenames now include the platform name.

New Features in this Release:

• Includes new Memo handling with significantly more functionality, and replaces existing memo folder with separate text files with a single DAT file which results in significantly faster performance when handling large memo databases (and also greatly speeds up syncing). Pimlical will prompt to convert the existing database when accessing memos for the first time with this new version. Adds filtering/sorting functionality similar to the contacts view with favorites/recent view, etc. Note: you must match this version of Pimlical/Desktop with Pimlical/Android 3.4.x if you use DirectSync and ensure that memos have been migrated to this new database format on both platforms prior to the first sync.
• Adds menu items to Backup Menu to restore the contacts and memos databases from prior backup copies. 
• Adds new preference: LockDueStartDateOnTasks which defaults to true and restores the prior behavior on tasks where the start and due dates were locked together and could not be separated - if set to false, this restores the behavior of V-3.3.05 where the start/due dates could be set to different dates.
• Enhances the Repeat Yearly/Monthly by Date rules to handle advanced repeats like the Black Friday case - you can set the repeat to occur on the first specified day of the week after the designated repeat occurrence. Example, Black Friday is the Friday after Thanksgiving - since the earliest that Thanksgiving occurs is the 22nd of November, you can set the repeat to repeat on the first Friday on or after the 23rd of November. Cyber Monday would be the first Monday on or after the 26th of November. Note that not all calendar applications support this type of repeat (for example, Google calendar can display an event like this, but won't allow the user to edit it).This feature is now also supported in iCalendar import/export. If you pick two or more days of the week to repeat on, Pimlical will pick the earliest, selected day of the week  (it does not repeat on each of the selected days). See the online Manual for Pimlical/Android for more information and a useful table to make it easier to determine what day to pick to follow a repeat set with a ByDay type rule.

• Fixes problem of the automatic backups of the local contacts database not being created properly. 
• Adds the past-due task and float icons that Pimlical/Android was already displaying for floating events or tasks where the due date is today or on a prior day (i.e. indicating this is something you definitely want to address today).
• Fixes a recent issue whereby the links dialog was not displaying contacts from the new contacts database.
• When removing deleted records from the database, Pimlical now explicitly indicates how many records were removed from the contacts and memos databases (previously that information was only provided for the calendar and tasks databases).