This section below 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 and any prior versions you may have skipped over when upgrading.

New Features in V-3.7.x of Pimlical/Android

• 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 will in future also seamlessly support OneDrive, Box, Google Drive, pCloud and Egnyte as well. Note that DirectSync is still fully supported as another sync option (and is still the preferred Off-Cloud sync solution)
• Many more minor features and fixes - see Revision History below for details.
  

New Features in this Release:

• Uses Android OS AlarmClock function for its alarms instead of RealTime Clock as former appears to be more reliable. This will cause the AlarmClock icon to appear on the status bar at top right - see FAQ's: Android Version: http://www.pimlicosoftware.com/pimlicalandroidfaq.html
  for information on how to remove that icon if you prefer.
  
  

• Fixes new issue in V-3.7.14 of not playing alarm sounds if Preference SpeakAlarms is set to false.
• Fixes issue of generating spurious error message about being unable to play alarm sound because the Done or Snooze button was hit the instant that the alarm started to be spoken (preference SpeakAlarms set to True).
  
• Fixes obscure (but benign) problem of generating spurious NullPointerException error rather than just  properly reporting that a WiFi connection is not available. Also caters better to devices that are really SLOW to establish a WiFi connection.
• Addresses some obscure refresh issues on certain devices (timing issue) when exiting from the Edit Dialog (especially when preference EditDialogQuickReturn is set to True).

New Features in this Release:

• Fixes problem of not reliably displaying an expired, snoozed alarm when the Pimlical notification icon is tapped in the status area.
  

Fixes and New Features in V-3.7.12 (NOTE: Be sure to pair with V-3.7.x of Pimlical/Desktop)New Features in this Release:

• Avoids generating spurious error message about not being able to play the alarm sound if you have spoken alarms enabled AND dismiss the Alarm dialog (either with done or snooze) WHILE the text of the calendar event is still being announced.
• Fixes issue on iCalendar import where the event was always also being assigned to the UNFILED category.
• Fixes issue on iCalendar import where it was complaining about a VTIMEZONE block not having a DAYLIGHT section (when in fact there was no DST in that locale).

New Features in this Release:

• Fixes issue of not providing proper color contrast in WeekView date headers when a light color was chosen (it was hard-wired to white, but now obeys general contrast levels to determine whether to use black or white). Also now draws today's date using the proper preference (TodayWeekMonthNumberColor).
• No longer writes the contents of the sync log file into the PimlicalAutoSync.Log file when Preference DebugMode was set to True (not really necessary and could result in that log file quickly ballooning in size if DebugMode was set.
• Fixes new issue (in V-3.7.09) in third alternate weekview that was causing the date header for Saturday to appear blank.
• Fixes obscure screen redraw issue in Day+ view when portrait and landscape number of days is different  and screen is rotated from portrait to landscape mode (specifically, when rotating from an orientation that had more days to an orientation that had fewer days).
• Fixes issue in landscape mode with later OS versions that allow pinning of the Home/Back/Overview buttons (Pimlical was reserving space for them in landscape mode even if they were not pinned).
  
• Adds support for Priority Policies on Do Not Disturb setting, so if you filter for Priority AND have included Calendar events as part of your priority notification categories, P/A will now allow the alarm to sound (previously, it only allowed alarms if filter was explicitly to Alarms or All).
  
• Tweaks the test for a "dark" color to more closely approximate how the eye responds to intensity of colors (specifically a color is considered "dark" if:
  1.    ALL three RGB components have a value less than 185, or
  2.    The Red and Green components are both less than 50 (i.e. any shade of blue or near-blue), or
  3.    The Green and Blue components are both less than 50 (i.e. any shade of Red or near-red), or
  4.    The Blue and Red components are both less than 50 and the Green component is less than 185 (Due to sensitivity of eyes to green, it needs to be a bit darker than the other components).
  

New Features in this Release:

• Fixes new issue in V-3.7.09 of not sounding alarms as side effect of new Preference (AlarmsIgnoreDoNotDisturb) not being handled quite right. Also tied spoken alarms into the DND system preference setting (i.e. if alarms are to suppressed during DND, then spoken alarms are to be suppressed as well).

New Features in this Release:

• Adds new preference setting: AlarmsIgnoreDoNotDisturb (default value is FALSE). If set to TRUE, Pimlical's alarms will sound/vibrate even though Do Not Disturb is set. With default setting of FALSE, no sound or vibration is made unless alarms are permitted during Do Not Disturb (although the alarm dialog will still appear and AutoSnooze. Previously, the Do Not Disturb setting was completely ignored by Pimlical.
• Adds three new preference settings to help setup colors when user wants to implement a 'night' mode for Pimlical:
      ViewSeparatorLineColor - specifies the color to use for the line(s) that separate days/weeks/months in Views (default is Black).
      WeekMonthNumberColor - specifies color to use for the date in the weekview, and the month numbers in the Month View (default is black).
      TodayWeekMonthNumberColor - specifies the alternate color to use for WeekView date and month view numbers when the date is Today (default is Maroon).
• As part of the 'night' mode accommodation, the WeekView now uses the preference ReverseHeaderColor to set the background color for the date banner in the WeekView.
  
• Fixes some minor cosmetic issues in the display when the preferences ItemBorderThickness and GridBorderThickness are set to large values (previously, Pimlical was not catering to the fact that the borders might be thick enough to overlap part of the item display).
  
  

• Avoids error message from a benign error condition when tapping on Pimlical Alarm Notification Icon after Pimlical's memory has been appropriated by the Android OS.
• Fixes issue on some newer phones where Pimlical was always reserving a blank space at bottom of display for the BACK/HOME/LAST buttons, even when they were not displaying (when changing visibility, Pimlical needs to refresh display to recalculate new screen size).
• Fixes an issue when the preference EditDialogQuickReturn is set to True (default is False): under some conditions, the screen would not refresh immediately so a recent change would not seem to have taken effect (although it had in fact).
  
• Changes the way AutoSyncFrequency is handled on startup and in Preferences: first, launching Pimlical no longer resets the AutoSyncFrequency interval; second, you now have to actually change the value of AutoSyncFrequency in order to have it reschedule starting within five seconds of the change (previously, just looking at the value in Preferences was enough to trigger the rescheduling).
• Now displays both the Snooze notification and AutoSync notifications separately (previously, only the most recent would be displayed).
  

New Features in this Release:

• Includes improved error messages in Contacts and Memos Apps.
  

New Features in this Release:

• Fixes issue of retrying AutoSync too rapidly on some types of faults in AutoSync (such as not having an internet connection, or connection timed out error etc.). Now just defers to next AutoSync Interval on failures like that.
• Improves efficiency of requesting permissions by making it clear all three permissions are needed to proceed.
• Fixes issue of Read Calendar Permission/External Storage Permissions not being explicitly requested (a NEW requirement in OS8.0) resulting in Android calendars not being visible on some OS8/8.1 devices.
  
• Automatically defers AutoSync to next Interval if there is no network connection.
• Changes all references to 'internet connection' to 'network connection' as it is actually a network connection that Pimlical is testing for - not access to the internet itself.
• Changes Alarm Behavior when either (a) the number of times the alarm has auto-snoozed exceeds AlarmSoundRepeatCount, or (b) the alarm triggered during a phone call and the preference AutoSnoozeDuringPhoneCall was set, or (c) the preference UseNotificationWhenAlarmTriggers is true. Previously, the alarms would be auto-snoozed, which meant that every X minutes (as defined by AlarmSoundRepeatInterval), the device could turn on and a new notification was posted (the alarm dialog would not appear, but having the device power on and make a sound was obviously undesirable behavior). Note that the default value of AlarmSoundRepeatCount is 100,000 which effectively means that alarms would continue to be auto-snoozed every X minutes "indefinitely". So if AlarmSoundRepeatCount is 2, the Alarm dialog will appear at the alarm time, and once more after an Auto-Snooze. When the second alarm dialog is dismissed, it auto-snoozes one more time, but on that third time, no alarm dialog appears, and a notification is posted, along with the notification sound/vibration. No further alarm activity occurs. The user can use the notification to see the Alarm Dialog and act on the items there...
• Works around CloudRail issue of not properly finding lock files in AutoSync, thereby allowing conflicts to potentially occur.
• When tapping on Pimlical Alarm notification in notification bar long after alarm went off, Pimlical now displays a dialog showing what alarms had been set (previously, nothing happened if too much time had passed and nothing was displayed).
  

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.
• Fixes new problem that the function to clear the Last Access Dates in contacts was now setting the last-access date to the current date/time.

New Features in this Release:

• Fixes a few obscure issues with Preference Names that were causing a few sort anomalies in the preference list.
• Fixes another issue in AutoSync that if Pimlical was active (i.e. user had dialog open, etc.), and the preference TimeOfDayForAutoSync was set to a value other than 0, and Pimlical had not yet synced before that specified time of day, it was still saying it would try again in 2 minutes, when in fact it was trying again in 5 seconds.

New Features in this Release:

• Adds two new functions to the System (previously called Debug) menu: View Error Files (which displays all the error files), and View Log Files (which displays all the Log Files, including the DirectSync and AutoSync Log files).
• Now sorts each section of preferences alphabetically by Preference keyname. This may initially be discomforting to old users, but there are now so many preference settings that sorting them is really mandatory...
  

• Fixes the default values set by the Set Default button which previously was setting some default values different from the default values in the default preference file on installation.
• Now displays a couple of preferences that previously did not show up in the preference list (like BackupLocalMemos).
• No longer displays the start/end times of an appointment in the Day/Day+ views just because the start or end time was outside the default range for timeslots (as defined in DayStartMinute and DayEndMinute). They are now only displayed if either time does not fall on a timeslot boundary AND the preference includeDurations is false.
• If AutoSync is set for automatic operation (AutoSyncFrequency not 0), it now triggers that interval after the launch of Pimlical thereby avoiding annoyance of having AutoSync running right away and not allowing full access to calendar, contacts, etc.
• Fixes an obscure issue with contacts and memos whereby they may get unnecessarily copied back to the server even though it was not required.
• Fixes an issue in the CloudRail libraries (used in AutoSync) that could cause an internal fault in CloudRail that then caused an Exception Error in AutoSync.
• Previously, when synchronizing in AutoSync, triggered off the timer (but not when invoked manually), Pimlical would compare date/time stamps on files in order to determine if the server had been updated AFTER the last synchronization and if not, would skip the synchronization process. With this release, the optimization check is always performed regardless of whether AutoSync was manually or automatically invoked.
• Fixes an issue in the AutoSync log files where Pimlical would report erroneous figures for copying records to the server for contacts and memos, even when nothing had changed.
• Fixed issue in AutoSync that if Pimlical was active (i.e. user had dialog open, etc.), while it was saying it would try again in 2 minutes, in fact it was trying again in 5 seconds.
• Addresses issue with notifications in Android OS8.x which under some conditions was causing a Failed to Post Notification Error.
• When purging records, now checks for the Action Tag No Purge and avoids purging any record with that tag.
• In Contacts, when you tap on the location icon, Pimlical now launches a mapping application to mange the address (previously, it was hard-wired to invoke Google Maps) - this now allows other mapping applications (Waze, uber, etc.) to be selected, and also matches how the location icon works in the calendar portinon of the app.
• Fixed problem with WidgetFontSize preference name (recorded internally as WidgetFont).
• Fixes issue of Voice Entry command set on command bar or gesture causing an Undefined View Label error.
• Fixes an obscure race condition on some devices which could cause a view not to immediately refresh on exit from Edit Dialog or Event Selection List, when using the preference: EditDialogQuickReturn set to True (default is false).
  

New Features in this Release:

• Adds a new SetDefault button into the preference change dialogs that will reset a preference to its initial, default state. Also, a long-press on an item in the preference list now displays the default setting for the preference value.

• Ensures the internal, default preferences set the correct default value for the preference: AutoSyncPath.
• When AutoSyncFilePath is changed, Pimlical now automatically resets AutoSync Authentication (so a new login is performed to the new cloud server).
• Fixes a potential issue in AutoSync when invoked automatically from a timer. Previously, it was possible for a second AutoSync session to get launched on top of prior one causing odd things to happen.
• 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/

New Features in this Release:

• Significantly improves reliability of network transfers in DirectSync by utilizing a much smaller buffer size (apparently the Android OS was failing to manage larger buffers properly!).
• When a file transfer fails in DirectSync due to network problems, P/A now ensures that the original database file does not get overwritten by a corrupt file (previously, this could result in a truncated or empty file in P/A).
• Ensures that if the user attempts to dial a phone number accessing contacts via the Widget, before P/A has granted permission to access the phone, that it now requests permission (previously, tapping on the phone icon was just ignored).

New Features in this Release:

• Applies fix to Google's licensing library software, that was causing an Uncaught Exception Error (Service Intent must be explicit) when Pimlical invoked Google's licensing check (an issue only on the Google PlayStore version).
  

New Features in this Release:

• Fixes an issue in V-3.5.44 where the change in permissions handling could result in a spurious complaint about the application not being licensed (esp. if there was no internet connection as it was incorrectly, repeatedly looking up the license, when in fact that should have only been done once...).
• Fixes issue of reporting that the Local Calendar File was not written because it was empty when in fact it was not in use (there was a place in the program where it tried to write the local calendar even though the preference LocalCalendarSelected was set to False - which should avoid any attempt to write the local calendar).
• Fixes an issue in handling Android calendars whereby under some conditions, the alarms might appear to all be set at event time when the cached calendar file had just been read.

New Features in this Release:

• Changes the way Permissions are handled again. Pimlical now will require the three main permissions (Access to external storage, access to contacts and access to the Android calendar) on initial launch. Phone permission is requested when needed or accessing contacts (and can be denied by the user).

New Features in this Release:

• Fixes a new issue in V-3.5.42 which was causing Repeat Filters to duplicate (as side effect of the fix to run  repeat filters on startup.

New Features in this Release:

• Fixes an issue in V-3.5.41 whereby Pimlical was requesting a Permission to access the Android Calendar when in fact it ONLY needed to write to the local calendar.
• Fixes an issue if the preference SecondsToAutoSnooze was set to 0s (not usually a good idea as it can result in the battery being drained down too fast) whereby the alarm dialog would instantly disappear when a button was tapped and it would be snoozed for the standard autosnooze interval instead of the value in the designated button pushed.
• Changes the behavior on requesting the permission for Accessing Contacts (necessary if the primary email address is to be used as the ReferenceID which is preferable for the vast majority of users) so that the user better understands WHY Pimlical is requesting this permission (even if the user does not plan to access contacts).
• Changes the behavior if the user inadvertently DENIES access to external storage (the hard-wired Android OS dialog requests access to "photos, media, and files" and it may not be clear to the user that this is really a REQUIRED permission, so Pimlical asks again if the user denies access and explains why it's needed...
• Now checks for invoking an automatic repeat filter on startup (previously, it might take as along as a minute for the repeat filter to "kick in".
• Fixed an issue in the licensing of the Direct Download version whereby you sometimes had to go back a second time in Menu | About to see an acknowledgment that the program was licensed.

New Features in this Release:

• On Android OS 6.0 and later devices, now handles Permissions according to the new OS scheme. On install, it no longer requests permissions, but WILL request them at runtime. On a Clean install (i.e. Pimlical is not currently installed), Pimlical will request permissions to access external storage, the calendar (if you want to use Android calendars), phone (if you intend to have Pimlical dial phone numbers), SMS (if you want it to send SMS messages), etc. You must authorize access to external storage, but everything else can be denied and Pimlical will still run (but obviously can't invoke functions for which permission has been denied). For example, if you deny access to the calendar (Android calendar), then Pimlical can only access its local calendar. On a reinstall, the prior permission settings are retained.

New Features in this Release:

• Fixes obscure issue of invoking a filter by name that no longer exists (for example, because a command bar function referenced a filter that no longer exists, etc.) - which was defaulting to the FIRST filter in the filter list, rather than the more reasonable choice of the DEFAULT filter, and which was also not logging an error file for the condition.

New Features in this Release:

• Fixes a new issue in the Day+ views in V-3.5.38 where a side effect of the update was that the timeslots in the DAY+ view would not always align horizontally.
• Also fixes a long-standing issue in the Day/Day+ views that if the Font chosen for the TimeScreenFont preference was LARGER than the font used for the display of text in that view, the Time Slot times would be truncated because the slots weren't tall enough.
  

New Features in this Release:

• Incorporates changes in the Alarm System to address the issue of "Deep Doze mode" in the Android OS. Pimlical will now force the Android OS out of Doze mode (previously, in doze mode, the Android OS would ignore Pimlical's alarms).

• Pimlical now requests MORE memory from the Android OS when launching. On most devices, this should result in a near doubling of the Heap Size (see menu | about), and that should mean that the scrolling region in the List View will be correspondingly larger.
• Ensures that the AutoPurge action tag no longer applies to repeat series. This was a potential issue for users wanting to use Daily Repeat Floating Events and not have the instances pile up if they were not completed on that day.
• Fixes an issue in the Day/Day+ views whereby under some conditions, an event in a timeslot after the normal end of the day and at 11pm or later would not display fully.
• Now avoids redundantly resetting internal Alarm Clock when it has not changed and Pimlical is first launched.
• Updates some Preferences with helpful notes about using that preference setting.
  

New Features in this Release:

• Ignores any ACKNOWLEDGED tag in the Alarm Section on iCalendar Import (its presence was causing some events to not get properly imported that followed an event using that tag in the Alarm block).
• Fixes an unexpected UncaughtExceptionError that can occur sometimes when Pimlical is launched via Widget to look at contacts or memos. 
• When the preference DaysBackToRead is set to a value other than the default of -1 (read all), Pimlical now includes exceptions to repeat events (previously they could be skipped) - as a recent change to Google Calendar was causing a problem with missed exceptions.

New Features in this Release:

• Ignores any ACKNOWLEDGED tag in the Alarm Section on iCalendar Import (its presence was causing some events to not get properly imported that followed an event using that tag in the Alarm block).
• Fixes an unexpected UncaughtExceptionError that can occur sometimes when Pimlical is launched via Widget to look at contacts or memos. 
• When the preference DaysBackToRead is set to a value other than the default of -1 (read all), Pimlical now includes exceptions to repeat events (previously they could be skipped) - as a recent change to Google Calendar was causing a problem with missed exceptions.
  

New Features in this Release:

• Fixes issue of tapping the 00 button when using the Alternate Time Picker (Default) when preference AltTimePickerAutoClose is set to False not clearing the final digit of the display.
• Fixes a problem in the Filter Dialog whereby the priority and urgency settings would sometimes get reversed when the filter was recalled for editing.
• Fixes an odd, new issue in the List view whereby items that should display did not (as if the number of items permitted in that view was limited).
• Fixes an issue with long-pressing items directly in a view to bring them up for editing. Older versions of the Android libraries had a bug whereby a Scroll/Fling would always be followed by a long-press, so there was protective code in there, but this code is no longer needed and was interfering with the interpretation of long-presses with the newer OS 4.1 libraries.
  

New Features in this Release:

• Fixes a new issue that appeared in V-3.5.32 whereby a spurious error message could get generated from the automated backup routines.
  

New Features in this Release:

• Fixes some obscure, potential issues with new behavior in the Android OS 4.1 library routines that were causing stability issues (in particular, if the read on the system preferences failed because the Android OS was prematurely terminating Pimlical, Pimlical now ensures that it does not write out the truncated/reset system preferences).
• Fixes an issue on first "launch" of Pimlical on a day not always displaying today's date when filter is set to display from today's date.
  

New Features in this Release:

• Restores prior behavior on startup (at some point recently, the Fast Startup display got side-stepped, and there were some anomalies on startup when the startup view was set to an explicit view with today's date). Sometimes the prior date/display appeared instead, and on rare occasions hitting left/right button moved to yesterday/tomorrow on startup when the display was showing some other date. The Fast Startup View is now always displayed on menu | exit and when the BACK button is hit in a main view, while the calendar database is re-read. The HOME button does not use the Fast Startup View if the calendar database is still intact in memory (but will otherwise). While reading the calendar in the background, the Fast Startup View provides the appropriate view, with a rotating circle at top centre to alert the user to the fact that the calendar is still being read in the background (and during that time, you can not edit any items on the screen).
• Fixes an issue of not always saving preferences when a change is made to the permanent Contact Sort via a long-press on the Sort button in the Contacts Dialog.
• The 00 button in the alternate Time Picker (the default Time Picker), now obeys the preference AltTimePickerAutoClose and won't close the dialog if set to False (default value is True).
• Fixes a display issue when displaying timed, floats/tasks and the preference HideFloatIcon is set to true.
• Fixes an issue in the Help & Usage Tips menu (only when displaying the global font selection checkboxes) that under SOME conditions, the code to prevent the user from checking more than one box did not get activated, resulting in possibly unexpected results.
• Provides better reporting of uncaught exception errors
• Provides partial workaround for new behavior in list view with OS 4.1 libraries whereby the screen can be blank when there is insufficient memory for the specified page size (a combination of the number of days in the list view and the size of the font in that view).
• Fixes the issue, mostly seen on Samsung phones, where tapping OK in the Edit Dialog when the software keyboard is displayed results in a blank space as if the screen had been resized to use the space reserved for the soft keyboard.
• Fixes a new issue with the OS 4.x libraries whereby rotating the screen caused the app to be relaunched with problematic side effects (alarm dialog re-appearing, corruption of system preferences, etc.).
• Fixes an obscure issue when there are calendar names that look identical except for a difference in case (prior version was subsequently looking for the first match with a case-insensitive search).
• Changes the behavior of the Find function so that if the current filter has the sort criteria of Date (Find Only) as the first item in the sort criteria list, that sort prevails (previously, the Date (Find Only) sort criteria was overridden by the Preference FindUsesReverseOrder. Also, when the CLEAR button is tapped in the FIND dialog, the event selection list position is cleared so that the list always displays from the top regardless of the most recent item viewed/selected.
• Fixes an issue whereby the first Filter in the Filter list would inexplicably get selected - particularly after using menu | Select Calendars.
• Fixes an issue in menu | Select Calendars when both Android calendars and the local calendar is being displayed, and one or more Android calendars are not selected, and one or more categories are not selected - under some conditions, only the Android Calendars would be selected for display in the filter.
• 
  

New Features in this Release:s

• Includes an alternate method of invoking SMS messaging from the Contacts section of Pimlical. With the new RCS standard, Android OS8 and some OS7 versions are not displaying all apps that would normally handle SMS messaging. With this change, all apps should be included.
• Due to changes in the Google Playstore, supporting older OS versions back to OS 2.3 is no longer feasible. Users of the Playstore version with devices that have OS 4.0 or older (2.x, 3.x) will need to continue to use their existing V-2.3.24, or they will need to switch to the Amazon Market version or Direct Download version. However, those versions will also require OS 4.1 starting with the next V-3.6.x release. Users who have automatic update set could run into this issue (it's advised to shut that off and not update Pimlical).
  

New Features in this Release:

• Adds new popup command (for both single and multi-select) to toggle the state of the private/secret flag. Some users may find this useful for hiding items in outlook when syncing with Outlook. Note: this popup command will need to be added to the preferences: PopupListCommandsForEvent and PopupListCommandsForMultiSelect.

• 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:

• Avoids complaining about an alarm being set in the past when a template is being edited.

New Features in this Release:

• Fixes another issue related to the feature of restoring lost preference file from the most recent backup. 
• When "exiting" Pimlical (using Menu | Exit) - the temporary list of additional categories in the memos and contacts app is now cleared (avoids issues if copying a different database file into Pimlical while it's running - at least menu | Exit would clear out any previously cached list of temporary categories).
• 
  

New Features in this Release:

• Adds new preference: EMsInTabStops which defaults to 8 Ems (Em here is the width of a lower-case 'm' in the current font/size) - use a smaller value to tighten up table columns or larger to space them  further apart).
• Adds feature into MemoImport function (which imports text files into memo database) to allow all items to be forced into a specific category (enter category name and tap SELECT button to do that, or just tap PRESERVE button to preserve the original category designation (if any).
• Adds documentation and three preference items to default preference file (the internal support for these preferences has always been in P/A, but apparently, they did not get properly documented): ContactListDescriptionFont, ContactListPhoneFont, ContactListAddressFont which adjust the size of the description, phone and address fields in the main contacts list.
• Adds a test (that was in P/D) for editing an event when ALL of its alarms were set in the past. In that case, a warning "toast" message appears when exiting the Edit Dialog.
• Fixed an obscure issure in the Repeat Rule & View pane of the Edit Filters feature which could under some conditions cause the default preference file to get reset.
  

• Now caters to Android OS unexpectedly terminating Alarm Thread just before it was about to exit,. which could unexpectedly cause the Alarm dialog to mysteriously re-appear if Pimlical is invoked within a minute or so after a valid alarm as triggered.
• Fixes issue of Memo Export converting all spaces to underlines (probably no longer necessary), and then 'fixes' the issue caused by that prior version, by changing underlines to spaces on import if there are no spaces in the filename (which should correct the change made by the prior version).
  
• Fixes issue of selecting certain categories in the local calendar and finding out that Android calendars would then be de-selected (under certain conditions).  In general, it's always better to edit the filter to accomplish this, but because the editing of filters was a function added much later in Pimlical, the original menu function is now redundant, but has been left in there for compatibility.
• Fixes an incompatibility in the way filters are handled between P/A and P/D with respect to the meaning of "higher" as applied to priority and urgency. P/D was correct in treating priority 1 as higher than priority 5, while P/A was treating 'higher' as meaning a higher number and therefore treated priority 9 as the highest priority. Note that existing users filtering on priority or urgency will have to reverse the filter settings to achieve the desired result.
• 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 an issue in some views where the '~' (hidden) and '*' (force display) flags in front of the dateline did not appear if there was not enough room for the long form of the date to be used.
• Fixes another issue related to priority and urgency - if there is an explicit priority (or urgency) set in the filter, then items with no priority (or urgency) are always hidden (previously, they might have displayed). 
• Fixes problem with the ~~Birthday Action tag in call/action templates - previously, under some conditions, the day of the month would be the day before the birthday.
• Changed the function of the preference NoAlarmsOnHiddenItems to ignore alarms on items hidden for ANY reason, and updated the description to reflect that change (previously, only items hidden because they were in hidden categories were hidden. Note that if you are currently FORCING the display of hidden items (H/S button in Event Selection list set to S-how), then the alarms WILL sound on those items.
• Fixes a NullPointerException error in AutoSync when overwriting a completely empty tasks database.
• When changing the status of an item to Completed/Canceled/Deferred, the alarms are now removed from the item (this is consistent with what happens when you change status via popup command).
• 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).
• Fixes an obscure display problem with events that span midnight and which repeat on the spanned day and which were not displaying the evening instance on the spanned day (for example, an event from 23:00 to 01:00 that repeats daily).
  

New Features in this Release:

• Fixes issue in Memo Import whereby the memo database could be written improperly.
• Fixes issue in Memo Import of importing an 'extra' memo with no title due to odd appearance of an empty TXT file (which looks like some Android OS bug?).
  

New Features in this Release:

• Includes more diagnostic information about the preference reset issue, a new flavor of which appeared on some phones when upgraded to Android 7.0.
•  
  

New Features in this Release:

• Fixed issue on snoozed alarms where under very rare occasions a snoozed alarm might appear twice in the list.
• Fixes problem in Memo Import of text files whereby it was still hard-wired to reading memos from the PimlicalMemos folder rather than the selected Folder (symptom: filename read, but no text of memo).
  
• Fixed new issue in V-3.5.21 whereby equals sign was being treated like a tab code in the note field.
• Includes the preference: IncludeTagsInICSExport which was inadvertently omitted from the Preference File Template. Normally,  Pimlical generates custom iCalendar tags for its unique features (useful if you are going to import the exported iCalendar file back into Pimlical. However, you may want to set this false if you are exporting to some other calendar application (since the tags would be useless anyway).
• Fixes a very obscure issue whereby under some conditions a snoozed alarm might not trigger properly (resulting in the debug log of the error condition: savedTabs[0] Time does not match alarm Trigger Time).
  

New Features in this Release:

• A long press on a date in the Pimlical Date Picker now displays the day of year as well as the week of the year.
  

• Added some internal debug/diagnostic functionality.
• 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.
• In menu | Preferences | Restore | Reset, you can now only pick either to restore timezones from Worldtimezones.txt or or from the master list (Worldtimezones_all.txt). Also, the legend for System Preferences was changed to SystemPreferences.dat (previously had the old name of PimlicalDBs.dat which is no longer used for system preferences).
• Moves old debug Function15 to Function16 (used only at direction of Tech Support).
• Fixes very obscure Null Pointer Exception Error in refreshing the Detaills screen of calendar when Android OS was ressurecting Pimlical after having removed its memory.
• Fixes a NullPointerException error if user attempts to synchronize contacts (AutoSync) when there is no local contacts database on the Android device.
• Changes the size of the location field so the fontsize matches other fields in the Edit Dialog (previously, it was in the same font size as the Where: label which is unnecessarily small).
• Fixes a spurious syntax error in the ShadedDates preference when a date specification in YYYYMMDD format had a month of 12.
• Fixes UncaughtExceptionError if user starts with completely empty contacts database, creates a new contact and taps on the label button to select a different label value.
• 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 new problem introduced in V-3.5.14 whereby if there is only one memo linked to an event, tapping on the link icon brings up the entire memo list rather than just the one linked memo.
• 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.
• Avoids spurious NullPointerException error when requesting all the repeat occurrences of a deleted, repeat event.
• Fixes an obscure error condition if the table of DST rules in the cached System Preferences is corrupt and forces re-read from Worldtimezones.txt file (previously, it would not automatically correct this error condition).
• Fixes issue of inserting a new event on a day that also had a spanning event from a prior day, appearing for just the first time in the wrong order (the spanning event was treated as being at its start time, as opposed to 00:00 on the day it was spanning into). This problem only appeared one time, as it was immediately corrected when the display was refreshed.
• Fixes issue of setting a null date for the preferences FirstWeekOfThisYear and FirstWeekOfNextYear (previously, null date was not set and a spurious error file was generated instead).
• If the Event Selection Dialog was open when an alarm triggered and the Edit button pressed, the selection list is now cleared to avoid any confusion over any possible update to an item in that list from the Edit Dialog.
• Fixes a problem with saving an event as a template when the event has a custom font - prior versions were not translating the font size into a generic index into the preference ListOfFontSizes, so the fontsize was getting mis-converted when the template was subsequently inserted.
• When an alarm triggers during a telephone call, and the preference: AutoSnoozeDuringPhoneCall is set to true and the preference UseNotificationWhenAlarmTriggers is false, PImlical now ensures that the alarms are properly rescheduled (under some conditions, previously, the alarm would not return as a snoozed alarm, and in some cases, the following alarm might get dropped as well).
• Fixes NullPointerException error if you attempt to invoke Menu | Select Calendars | Import when the Pimlical/ExportedCalendars folder does not exist, and now automatically creates that folder for the user.
  

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:

• Includes preference MemosStartupView which was inadvertently left out of the Preference file - this allows you to set the startup view to be ALL memos, or just Favorites or Recent.
  

• Corrects several errors in the handling of user conflicts with AutoSync (trying to edit a contact while AutoSync was syncing contacts, or launching AutoSync while a contact was being edited, etc.). Same issue existed in memos. Pimlical now properly informs the user to wait until AutoSync completes, or defers AutoSync until the user has finished editing the item.
• Fixes an issue of not managing the preference AutoSyncAction properly which would result in a spurious error file (getString()_Android_V-3.5.18-G.error) or possibly not preserving the last preference setting properly.
• Sync log now identifies the type of Sync operation (overwrite, synchronize).
  

New Features in this Release:

• Includes workaround for the new issue in Samsung's OS 6 release which causes exception errors based upon an arbitrary limit on alarms that they set in their version of the OS (Only an issue on Samsung phones that updated to Samsung's latest Android OS release).
  

New Features in this Release:

• Fixes an obscure exception error in the Alarm handling as a side effect to a new fix inserted in V-3.5.14.
  

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:

• More room has been opened up in the Edit dialog for the editing of the memo text. The window title has been removed, and the Memo Title is now permanently displayed, along with a toggle button that alternately turns on/off the display of the Create/Modified lines and the two large button lines.
  

• Newly Created memos which are linked now use both the title as well as the uniqueID, so if more than one memo is linked, you can see the title in the memo selection list when the link icon is tapped.
• 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 Java library to crash in P/A (Interestingly the Oracle Java library in P/D has no problem with that same code).
• Fixes an issue in DirectSync/AutoSync when user inadvertently enables syncing on non-existent memos/contacts databases (previously would cause a NullPointerException error when trying to update the log file).
• Fixes an issue in AutoSync where an odd error condition could result in Pimlical constantly retrying to sync - also could occur if user invokes AutoSync manually just seconds before AutoSync was going to be automatically invoked.
  
• Ensures that the summary of the number of contacts and memos appears in the concluding dialog of AutoSync (under those conditions where the dialog is displayed).
• If the user never set the preference RegisteredUserName, Pimlical/Android now uses the ReferenceID to create UniqueID's for events, contacts and memos (previously, it would default to the generic PimlicalUser. If you sync with P/D, it's a good idea to set this to your RegisteredUserName you are using in P/D (but this is not required).
• Updates the documentation in the online manual on memos for all the new, recent features.
• When detecting a "tap" that the Android OS reported as a FLING at the end of a SCROLL operation, Pimlical now uses the precise time that the finger first made contact with the screen to determine whether or not this was the spurious FLING that sometimes is reported at the end of a Scroll operation by the Android OS (the Scroll itself also being spurious as far as that user is concerned). Also, if DebugMode is set, Pimlical will log into the audit trail file FLING events that it converted to taps or long-presses along with diagnostic information - this should help track down issues that some users may be having with moving their finger or holding it down too long.
• Several internal changes were made in the handling of alarms to avoid complex race conditions when the user was modifying an alarm on an event that was within seconds of triggering the alarm dialog.
• Fixes an issue in AutoSync whereby under some conditions it skips the sync because it thinks that nothing has changed (when it has).
• Fixes an issue whereby a memo created after a memo was deleted was not causing it to be sorted into the correct position. Also now always forces a re-sort whenever a memo is edited if the sort was by date.
  

Fixes and New Features in V-3.5.13 - interim release

Fixes and New Features in V-3.5.12

New Features in this Release:

• Includes a new Send The Link button in Menu | About's New Release dialog, to invoke user's email app with the TO and Subject lines already pre-filled to request a download link to the current release of P/A. This also identifies the version the user is currently running, and also checks to see if they have the Direct Download version installed (and if instead they have the Google or Amazon versions installed, they will be told to go back to the Playstore or Amazon Market to download the latest release).
• Adds new preference: TimeOfDayForAutoSync which if set to a value other than midnight (00:00) specifies a time of day by 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.
  
• Adds new preference: AutoSyncNotificationVibrates which defaults to True (to preserve existing behavior). Change this to false to suppress vibration when AutoSync is triggered. Also, the vibration is now always suppressed when AutoSync is invoked manually from the menu (i.e. it'll only vibrate when triggered automatically by the timer and when this preference is set to true.
• When a FLING gesture is being converted to a tap/press (because Android frequently screws up the interpretation of screen gestures), Pimlical now uses the Android OS threshold value which (at least in Android 6.0) can now be set by the user in the Accessibility section of system preferences. There, the user can pick values of short = 500ms (1/2 second), medium = 1s or long = 1 1/2s, to distinguish between a tap and a long-press. The prior version had that set that at 1/4 second which was very short and a few users were finding their taps were too long and being treated as long-presses. 
• 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 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.
• 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 Android OS V-5.0 (possibly 5.1 too?) bug whereby the OS copy/cut/paste command bar only appears the first time after the memo function is invoked.
• If AutoSync is invoked manually, but no databases are selected in the preference: AutoSyncAction, Pimlical now complains about the configuration problem.
• Fixes issue of putting the DirectSync and AutoSync functions on the command bar but not having them operate properly or display the correct icon.
• Avoids the creation of spurious error files by AutoSync complaining that the Memos/Contacts databases were not written because they were empty.
• Fixes problem of not always automatically creating the PimlicalApp/PimlicalAutoSync path in dropbox when invoking AutoSync for the very first time from Pimlical/Android.
• Fixes NullPointerException error when clicking on the repeat parent icon in an event selection list (which normally displays the number of prior and future occurrences of the irregular repeat series).
  
  

New Features in this Release:

• Fixes a crash that was still occurring in V-3.5.07 whereby unchecking the Float checkbox and then rechecking it right away could cause a NullPointerException error.
• Removes the scan/fix routine for duplicate ID's in the Contacts database from the main Menu | Debug command, as both contacts and memos have their own routines that are accessible from their menus. The Menu | Debug command now only scans the calendar database (appts/floats/tasks).
• Fixes an issue with the preference: IgnorePrivateEventSetting whereby if set to True, there might be circumstances where the event would still appear as a private event.
  

New Features in this Release:

• Fixes issue in Edit Dialog that if you uncheck the floating checkbox for a task, if you then go back and re-check it (changing your mind and deciding to make it a float after all), the tasks checkbox will also be checked - it's now cleared.
• When checking the Tasks Checkbox in the Edit Dialog, or unchecking the Tasks Checkbox, or unchecking the Float checkbox when the tasks checkbox was checked, Pimlical now resets the category to UNFILED to ensure an Appt is not inadvertently left in a Tasks Category and vice-versa.
• Ensures that the preferences ApptCategoriesToSync and TaskCategoriesToSync can be properly managed when the preference MultipleCategorySelection is set to false (previously, it only displayed radio buttons instead of checkboxes and did not display the options to select ALL or None.
• The prefererences ApptCategoriesToSync, TaskCategoriesToSync, ContactCategoriesToSync and MemoCategoriesToSync are now all treated consistently - if All categories are selected (or if no categories are selected which is an invalid setting), the preference is set to (All). This fixes several minor inconsistencies, and also avoids inadvertently creating a category with the name (All) which could potentially happen under some unusual circumstances
• Fixes an obscure crash that can occur in the Edit Dialog when repeatedly changing a float to an appt to a float to a task etc.etc. (not likely unless user is pretty confused :).
• Fixes an intermitent and relatively rare issue with tapping on the screen immediately after launch and getting an empty Event Selection List (when there was obviously events being displayed on that day).
  

New Features in this Release:

• Changes the timeout for running an unlicensed version of Pimlical/Android from 15 seconds to 60 seconds as some users with large databases were having difficulty getting to the About dialog quickly enough to see what their ReferenceID was.
• Ensures that the new menu commands AutoSync and Recent Updates automatically appear in the menu (since the menu is a preference setting, and updates never change preference settings, the problem is that when a new menu item is added, by default it's hidden and not displayed. Whenever a new menu item is added, Pimlical automatically forces the display of that menu item for as long as Pimlical remains on the same minor version as when the item was added).
• Avoids generating a NullPointerException crash, if you use the special feature to remove old DateBk6 custom alarms from the alarm field (i.e. a long-press on the custom alarm field in the Edit Dialog) on an event which does not have any custom alarm set.
• 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 under certain circumstances in the prior release).

New Features in this Release:

• Fixes new issue introduced in V-3.5.03 whereby AutoSync was not getting properly initiated automatically based upon the AutoSyncFrequency preference setting.
  

New Features in this Release:

• Adds several new preferences to hide fields in the Edit dialog that you don't personally use to reduce clutter (HideGroupFieldInEditDialog, HideMeetingFieldInEditDialog, HideCustomAlarmFieldinEditDialog, HideFontFieldInEditDialog, HideIconFieldInEditDialog).
  
  

• The Calendar line in the Edit dialog is now no longer displayed if there is only one calendar available anyway (reduces clutter). 
• Updates to all the online help files to include new preferences and features.
  

New Features in this Release:

• Works around an Android OS bug (which seems to have gotten much worse in Android 6.0 and with higher Rez screens) whereby the OS reports a FLING operation when it should be reporting a long-press. This can cause a long-press on the main screen (such as on the time column) to be interpreted as a Tap (because Pimlical already fixes the flaw of the OS reporting a Fling rather than a tap, but it was not yet then sorting out a tap from a long-press). With this fix, most screen gestures are now being fixed up by Pimlical so they act like they are supposed to(!).
• Cuts down on the repeat frequency for AutoSync if some error is encountered (i.e. if you have no internet connection, Pimlical/Android will not re-attempt a connection until the next scheduled time for AutoSync occurs). Increases the repeat frequency if the server is just busy (i.e. has a lock file). Also fixes a problem whereby on relaunch of Pimlical, it was performing an unnecessary AutoSync.
• Fixes issue of the new RecentUpdatesCutoff preference not being present in the default Preferences.def file.
• Improves error reporting on corrupt data or preference files (previously, an Out Of Memory error would be reported without any direct indication as to what the actual problem was).
• Fixes issue of menu command Cancel Sync still appearing as Cancel GSync (This menu command now cancels google sync as well as AutoSync).
  

New Features in this Release:

• Adds new filter attribute to specifically track the desired number of days in the Day+ (Multiday) view when the device is in landscape mode. The existing filter attribute now only applies when the device is in portrait mode. The separate settings are displayed in the Repeat Rule & Views pane when editing a filter. If using a long-press on the button in Menu | Views, Pimlical will update the appropriate filter attribute depending upon whether the device is in portrait or landscape mode when the menu is invoked.
• Adds a new menu item, RecentUpdates, which displays all events and tasks in the calendar that have been updated or created since the cutoff Date/Time (as specified in preference: RecentUpdatesCutoff) in reverse chorological order (so most recent item at the top). This includes items that have been inserted into the database via AutoSync, etc.
• The menu Item Cancel GSync, has now been changed to Cancel Sync and this now cancels ALL sync methods (Google Sync, DirectSync and AutoSync). If Syncing to dropbox hangs (because the internet connection, while present, is not responding), you can use this to avoid having Pimlical get stuck waiting. Although Pimlical will eventually reset the dropbox flags, if you want to resume AutoSync immediately, you might want to just manually review the status of lock flags in the dropbox folder.
  
  

• Avoids NullPointerError on Dropbox Autosync when there is an error connecting to DropBox.
• Ensures brief message appears if attempting to invoke Autosync when there is no network connection available (or there is some undefined fault on accessing the network).
• When a new version is installed which updates major and/or minor version, the calendar database is now immediately rewritten - this avoids an issue if you invoke DirectSync before the database is updated - since Pimlical/Desktop will then complain that the calendar database is in the old format (and in fact, that could be a legitimate issue if the database has not yet been updated prior to the first sync after the update).
• 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.
• The preference SyncDefault has been renamed to AutoSyncAction to avoid confusion (SyncDefault controls DirectSync in P/D, while AutoSyncAction controls AutoSync in all platforms).
• The preference ContactsRecentItemsCutoff has been changed to RecentUpdatesCutoff as this preference now applies to both memos and the new menu item Recent Updates.
• 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.
• Ensures that the time of the last AutoSync is immediately written out to the system Preference file (as otherwise, under some conditions, such as an unexpected failure, or battery exhausted/restart, the date/time could get lost - which could result in unexpected behavior).
• When tapping the repeat icon, 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).
• Fixes a very obscure issue with alarms that could potentially cause one or more subsequent alarms to get lost: if the next alarm to go off is a snoozed alarm, and if there are no other alarms, and if you issue a command to that associated event that would cause Pimlical to remove the snooze on that alarm (i.e. marking it complete/canceled/deleted), and that command is issued less than 45 seconds before the snoozed alarm would normally go off, Pimlical fails to reset the alarm sequence, and subsequent alarm(s) might get lost if there was no further activity in Pimlical (which would normally reset the alarms anyway).
  

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).
• Adds support for tab codes in the Note field. Tab stops are set at an interval equivalent to 8 Ems which appears to be reasonably compatible with how tabs are displayed in P/D (so that formatted tables in P/D should then also display the same way in P/A). Not all virtual keyboards have a TAB character (SwiftKey does for example) and if Android reformats the screen to display the online keyboard and the edit field in a compact mode for the landscape display the tab stops are not expanded - but will instantly re-appear when the keyboard is dismissed.
• A tap on the regular repeat icon in the Event Selection List (or the irregular repeat parent icon) 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 children of an irregular repeat series.
• Adds new popup command: Share Calendar Event. This popup command will share either one event or in multi-selection mode, multiple events with any application that can handle file attachments - in most cases you would likely select an email application, but any application that presents itself in the subsequent selection screen can be used. The events are written into a standard iCalendar file with the filename Pimlical_Calendar_Events.ics. This file is also stored in the Pimlical folder on the Android device.
• The popup command: Share Event Text is now available in the Multiple Selection List of commands, so you can share (export) any number of entries as plain text.
• Adds new popup command: Compare Calendar Events. This command can only be used in the Multiple Selection List and when exactly two items have been selected. Pimlical then compares the two items and displays all the differences. This is helpful when diagnosing issues with events that appear to be duplicated (but are they really exactly the same? Or is there some subtle difference that the user was overlooking?).
  
• Adds new Preference: AutoSnoozeDuringPhoneCall which if set to TRUE will automatically snooze any alarms that trigger during a telephone call. Default value for this preference is false (which preserves the existing behavior).
• If the preference GoogleRefreshInterval is set to the value -1, then whenever the native Android calendar database is updated, an immediate refresh will take place of the calendar and the database rescanned for any new/changed alarm settings. This feature presumes that the Android OS properly notify Pimlical that the calendar database was updated. Earlier versions of the Android OS did not handle this reliably, however it appears that the latest iterations of the Android OS are now doing this.
• Includes support for Samsung's proprietary addition to the Android OS for their multi-window feature, so Pimlical can be opened in a multi-window display.
  
  

• Includes check for a user trying to rename the Unfiled category (which makes no sense and is something the program should explicitly prevent).
• Fixes a problem with birthdays/anniversaries in the local contacts dialog when home timezone is East of GMT (under some conditions, the birthdays were getting changed to the prior day).
• Fixes problem of three action tags (AutoPurge, NoAlarmOnReminder and NoVoiceAlarm) not being written out as tags into the note field of the Android calendar and as a result, the tags would eventually disappear and the functionality of the tag thereby lost. This was not an issue with the local calendar.
• Avoids an obscure interaction issue which can cause some error files to appear (problem is mainly cosmetic - but it was possible for Pimlical to proceed with redrawing the screen on an internal Android OS request when it was in fact reading the database at the same time).
• Avoids the remote possibility of missing the rescheduling of an alarm when the Android OS is desperately short of memory and ends up prematurely destroying Pimlical to use its memory for other tasks).
• Avoids displaying the default left or arrow icons on the first and last command bar buttons if those buttons are then remapped to some other command that does not by default display an icon.
• Fixes problem with changing Duration values in preferences (None in the Advanced Time Dialog was not recognized, and under some conditions, a Class-Cast Exception Error and Error File were being generated).
• Avoids generating error file on checking for new version when there is no internet connection.
• Eliminates spurious error files generated when Pimlical was attempting to redraw the screen while the floating advance was reorganizing the database).
• Fixes an issue of custom font names not always being reliably synced via Direct/AutoSync.
• Fixes issue of changing PimlicalAlarmHandling preference to None and not killing any currently scheduled alarm.
• Includes a workaround for what appears to be an Android OS bug in the handling of the Do Not Disturb feature - this workaround will suppress the speaking alarm if the alarm sound volume has been set to zero. This should avoid spoken alarms unexpectedly breaking through a Do Not Disturb. This problem has been seen on some Samsung/OS 5. devices (but does not appear for example on Nexus6/OS6).
• Fixes default value for the ShadedDatesColor preference which was inadvertently using hexadecimal instead of decimal values, which resulted in the color being defaulted as black(!) instead of light green.
• 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 problem of not being allowed to select multiple Android calendars for the NoAlarmsOnTheseCategories and ImportCategories preferences.
• Fixes an issue of using custom fonts in the birthday or anniversary templates - due to a recent change in V-3.4.22 in the way that template fonts are handled (to address the issue of auto-sizing fonts across different platforms), the font size of the template was lost and the imported text would typically appear in a tiny font.
• Fixes a benign OutOfBoundsException error that can occur in the Contacts display under some conditions if there is only one contact displayed and it is deleted.
• Removing all deleted records now also removes deleted contact records inserted into the primary calendar database (i.e. birthdays/anniversaries).
• 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.
• Fixes a problem with corrupt entries in the local calendar that have no uniqueID assigned whereby it was not possible to delete the item (typically the item had no description/no text too).
• 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).
• Cleans up the StringsList preference handling so that one can leave just a single item selected in the list (instead of seeing if just one item is selected, Pimlical now keeps track of whether the user was using the Up/Down buttons previously).
• The preference FingerSlipThreshold now treats ANY negative number as a request to replace that value with the number of pixels equivalent to about 1/10th inch (2.5mm) based upon the current screen resolution. Previously, if a user put in a value of -2, -3 etc. no complaint was made and the value would result in there being no threshold value of any kind which would not work well for most users (unless they never moved their finger even one pixel when tapping a button!).
  

New Features in this Release:

• Adds ifCategory and ifActionTags commands to the screen template drawing routines (these commands were already in P/D).
  

New Features in this Release:

• Fixes intermittent issue in using the Edit function from the Alarm Dialog when the Alarm triggered and the Alarm Selection List was (or had been very recently) displayed (on exit from the Edit function, the selection list displayed was not the expected list). This release simply returns to the main view on exit.
• Fixes a cosmetic issue on deleting an instance of a repeat series from an Android calendar when the local calendar was also being displayed. Until the next refresh of the calendar, Pimlical would in some circumstances display two instances of the repeat on the next occurrence (although the second occurrence was actually a 'phantom' and not actually a duplicate of the event in the database.
• A long press on the custom alarm field will now remove a prior custom alarm that was imported from the old DateBK6 program (previously, any custom alarm set by DateBk6 could not be removed and could cause problems on an Android platform).
• Fixes an obscure issue related to the use of custom font sizes in templates whereby on occasion the inserted text would be in an incredibly tiny font because the conversion between generic and actual font sizes (based upon the ListOfFontSizes preference) was not being managed correctly when Pimlical was launching (as opposed to just being reactivated).
• Now includes a check for corrupt entries in the local 'dribble' file database (previously, only the main database was being checked) - in particular, a corrupt date entry could cause Pimlical to fail to startup).
  

New Features in this Release:

• Includes check for Exceptions to Repeat events read from Google calendar to ensure they are valid calendar records (some corrupt records in the Google calendar database would end up tripping prior versions of P/A).
• Avoids a spurious error message warning about an item being in a hidden calendar (could occur previously with an event originally in an Android calendar saved as a template and inserted when that calendar no longer exists).
• Fixes an exception condition of inserting a template created from an Android calendar that either (a) no longer exists, or (b) which came from a different configuration of Android calendars.
• Now re-sorts the contacts database when a new contact is entered (previously, the new contact was put at the end of the database).
• Fixes exception error when changing timezones and using the old Palm/Datebk style time picker (UsePimlicalDateTimePicker = true and UseAlternateTimePicker = false).
  

New Features in this Release:

• Fixes an issue that first appeared in V-3.4.19 due to an editing error where two lines of code got unexpectedly juxtaposed - this could result in seeing preferences reset (help dialog appearing with the usual startup configuration with the checkboxes for setting a default font size), which in turn could result in all kinds of unexpected behavior.
• Fixes problem of going into menu | Select Local Calendar and not having the current, local calendar always marked as the default selection.
  
• Also fixes the spurious creation of an error file complaining about a "class-cast" issue in preferences.
  
• Now prevents the user from setting a repeat end date that is prior to the start date (which would be of course meaningless).

New Features in this Release:

• 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 doing that would be helpful for most users). Note that to use this new icon collection, you need to go into menu | Preferences | Restore | Reset and then JUST check the box to reset the User Icons file (you might also need to force-stop Pimlical and relaunch it).
  
  

• Fixes informative message when Deleting/Removing/Removing Blank Memos (previously the message was the same one used for contacts but needed to be more generic now that they are used with both databases).
• Includes an obscure fix covering recurrence rules in iCalendar format that have been created by some calendar applications with respect to yearly and monthly repeats by Day (and which could potentially cause a read fault on the calendar).
• Fixes an issue of using menu | preferences | restore | reset and selecting to reset the User Icons - under some conditions, the old cached versions of icons might still be used.
  
• The message that concludes the export of templates now includes the path and filename of the exported template file (at present: .../pimlical/PimlicalTemplateExport.dat).

New Features in this Release:

• Adds support for dialing phone numbers from Location Field. If you put a phone number into the location field, you can now dial that phone number directly from the Event Selection List by tapping the Telephone Icon (previously, you had to go into the Edit Dialog to dial a phone number that was stored in the location field). If the location field contains less than three letters, it is assumed to be phone number and will display the telephone icon in the list and main view instead of the location icon (map). You can also put multiple phone numbers into the list separated by commas and prefixed with labels in square brackets (such as: [Work] 512-555-1212, [Home] 512-555-1213, [Fax] 512-555-1214 and you then get a pick list to select the number to dial).
• Adds a Backup Preferences Now button to the Preference dialog. Preferences are normally backed up automatically by Pimlical (but no more frequently than specified by the preference MaximumBackupFrequency) but this button forces an immediate backup regardless of that setting. If you have just made a vast number of changes to your preferences, it's probably a good idea to backup them up right away.
  
  

• If you put a phone number into the location field, you can now dial that phone number directly from the Event Selection List by tapping the Telephone Icon (previously, you had to go into the Edit Dialog to dial a phone number that was stored in the location field). If the location field contains less than three letters, it is assumed to be phone number and will display the telephone icon in the list and main view instead of the location icon (map).
• Fixes issue of the Backup/Restore of preferences still referencing the old PimlicalDBs.dat filename instead of the new SystemPreferences.dat filename.
• When clicking on an item in an Event Selection list to bring up the Edit dialog, if you cancel out of the Edit Dialog, the selection list is positioned so that item is still visible (previously, if you canceled out of the dialog, the tapped item might not be visible in the list on return).
• Adds more robust error checking for corruption in date/times of events and fixes them.
• In the Pimlical Time picker (UseAlternateTimePicker = true - the default), selecting a timezone no longer resets the time back to the default value - the currently set time is preserved.
  

New Features in this Release:

• Fixes issue of the last access date/time displayed in the contacts selection list displaying 12/31/2099 as the date/time.
• Fixes obscure issue in the date/time displayed in the Recent Contacts list whereby the time might not have been properly adjusted for daylight savings when using DST rules appropriate for the Northern Hemisphere.
  

New Features in this Release:

• Fixes cosmetic issue of still displaying warning about DebugMode being set when the preference EnableDebugLog is reset from True back to False (debug mode is in fact cleared, but the warning message is spuriously displayed for a while).
• If non-completed floating events are present in the calendar with a display date prior to today and the advance of Floating Events is turned off (which of course is a weird situation and most likely the result of a user error in setting the preferences) - Pimlical will now display those events in today's schedule in the day/day+ views (previously, they could display in the Month View for example, but not the Day View which was puzzling and inconsistent in spite of the inconsistent preference settings).
• Fixes some internal licensing issues in the DirectDownload version that would normally only surface when a user had copied the Pimlical folder from one device to another device where the new device has a different (and unregistered) RegistrationID from the prior device.
  

New Features in this Release:

• Fixes problem of not properly formatting addresses in contacts section when using popup command to share a contact as a Text File.
• Fixes an issue on some Android configurations where the triggering of the AutoSnooze feature is significantly delayed by the Android OS (probably due to some badly written backround service that is tying up the Android Message queue for far too long). Although the Alarm dialog may stay on the screen for too long, the interval to the next snooze will still be correct because P/A adjusts the snooze interval for the alarms based upon the discrepancy between when the autosnooze feature should have triggered versus when it was actually triggered by the OS (If preference EnableDebugLog is set to true, the discrepancy is always logged into the log file).
  

New Features in this Release:

• Adds feature to spoken alarms to delay speaking the list of events some number of seconds after the preamble (Preference: AlarmPreamble). End the preamble with a comma to make the delay one second (end with two commas for two seconds, etc.). This gives you a chance to silence the alarm before something is said loudly in public that was not expected (Calendar Alarm: Time for your Daily Enema) <g>.
  
  

• 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.

New Features in this Release:

• Fixes an obscure issue in reading repeat specifications from an Android calendar item when there are multiple exception dates or a timefield is included on the exception date (this has only been seen on certain devices).
• Fixes an issue on editing of a repeat series with exceptions in an Android calendar, whereby the instances of the repeat series that should have been suppressed from display, were re-displaying.
• When a template is inserted, if the template is a floating event with a due date, the due date is now updated to maintain the original offset from the start date (i.e. if the due date in the template is 2 days prior to the template's start date, then the due date will be still be 2 days prior to the date on which the template was inserted).
• Fixes issue of long press on status icon to toggle status (such as marking a floating event as complete) in the Event Selection List sometimes resulting in the appearance of the Edit Dialog (This is an Android bug, but it seems that OS 6.x needs a new workaround for that bug).
• 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 issue of program still using PimlicalDBs.dat file on new install (rather than new SystemPreference.dat file). 
• Fixes NullPointerError that can occur under some relatively rare conditions when writing SystemPreferences.dat file.
• 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 a compatibility issue between the desktop and Android versions of the SystemPreference.dat file.
• Fixes issue of losing the checkmark on monthly repeats of appointment types only in a filter.
  

New Features in this Release:

• Incorporates some new fixes for reading/writing calendars efficiently and catering to the 'rename' problem.
• Fixes an obscure read error on the local calendar (related to timezone setting).
• 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.
• If there are no backups available, a message to that effect is now displayed when the Restore button is tapped in Preferences Dialog.
  

New Features in this Release:

• Fixes issue in V-3.4.08 of not properly handling the import and export of filters and templates in the new format. Also now makes it transparent to the upgrading user - if the files in the new format are not found, Pimlical can read the files in the old format. A long press on the Import Filter button will now look for filters with the old .FIL extension (the new extension is now .FLT) and those can be imported instead.
• Fixes issue of switching EnableDebugLog preference on/off and causing problems with DebugMode preference sticking...

New Features in this Release:

• Pimlical/Android can now optionally use the complete Olson Database of timezone definitions (see Menu | Preferences | Restore | Reset).
• The Menu | Preferences | Restore | Reset function now allows selective restoration of the Timezones database (both the standard as well as complete set of timezones), the icon database and the system and user preference settings.
• Android version now implements the alarm preference: AlarmSoundRepeatCount.  This preference specifies the maximum number of times that the alarm dialog will be automatically snoozed (default value is 100000 to preserve existing behavior). The notification that an alarm triggered is, however, left in the Android notification area (and can be pulled down at a later time to display the alarm dialog and manage those alarms).
• Significantly 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 makes a big difference for users with a lot of custom templates and filters.
  
  

• 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.).
• Fixes an issue with all views drawn after a screen refresh or on startup not always catering properly to the height of the command bar (so that the bottom portion of  the view was covered by the command bar).
• In the Edit dialog, the repeat button now also indicates if the current repeat series has any exceptions present.
• If you change the Starting Timezone of an event to All Time Zones, Pimlical now automatically sets the ending timezone to All Time Zones (this avoids issues with the duration field as it would make no sense to not have both timezones set to All Time Zones).
• Memos and Contacts View now enforce the use of the permanent sort when the view is invoked - previously the permanent sort was only used after Pimlical had been forced-stopped or after booting up. Also when bringing up the permanent sort, the radio button for the current permanent sort is selected as the default (previously, the current temporary sort was provided as the default value).
• A long-press on the ALL+ button in memos and contacts no longer removes the temporary sort (there was no reason to do that as it's just the filters that need to be cleared when using a long-press to display all items).
  
• Fixes new issue in a recent interim preview whereby the function to create a new template using the [+] button in the template dialog would cause a NullPointerException.
• Fixes issue of not properly sizing user icons on buttons when a dialog was first accessed (was failing to properly preserve the button size for future use). On installing this version, you WILL see the wrong (smaller) size icon on the button just one time, but then not again unless preferences get reset, etc.).
• Changed the meaning of the preference MemoTextLines to limit the number of displayed lines to that value, rather than always display that number of lines (even when the memo was shorter). Also if the preference is set to 0, the display is tightened up a bit as the visual padding is no longer needed.
• When using a template (set for an Android calendar) that was created from an event that was formerly part of a regular or irregular repeat series in an Android calendar (this issue is not relevant in Pimlical's local calendar), you can now use that template to create additional irregular repeat events without seeing the message about the limitation in Google Calendar. You can not, however, use that template to create a new regular repeat series, as Google Calendar can not handle the creation of a repeat series from a non-repeat event that was previously an instance of a repeat series.
• Repeat Exceptions dialog now displays the number of exceptions present for the repeat series.
• 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 a NullPointerError exception condition that could occur when using the Set Link to File popup command and navigating to a folder that is completely empty.
• The default color selection palette for background colors now matches the foreground palette with the exception that white and black are swapped around (note: this does not affect your existing preferences - it's only relevant if you reset them back to the 'factory default' setting).
• Fixes a problem with timezones when the current timezone is set to All Time Zones, and the appointment is in an Android calendar - previously, the time would shift because the appointment was not getting adjusted in a manner compatible with the way the Android calendar handles timezones. By setting the CurrentTimeZone preference to All Time Zones, you effectively disable all timezone adjustments (so that all events display at their native times. This has always worked in the local calendar, so this fix now allows this to work with Android/Google Calendars.
• If Preference DebugMode is set to True, the dialog that handles durations will also display seconds - this is rarely needed and caution should always be advised when setting a value in seconds as in many cases it won't have the desired effect (it can be useful, for example, in getting the alarm dialog to dismiss very quickly - say by setting a value of 5s for the preference SecondstoAutoSnooze).
• Memo title in the memo edit dialog is now displayed in the color set in preferences for displaying the title in the main selection list. Since it then becomes obvious if a memo is protected, the prior popup warning about protection no longer appears.
• 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 right after syncing with P/D.
• Fixes issue with the mysterious "Pink" buttons (a new issue in Android 6.0 - Marshmellow).
• 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). 
• Fixes an obscure issue with using timezones in quick entry templates - the quick entry templates were being read before the timezone table was read with the result that some timezone information could get lost or spurious error messages generated.
  

New Features in this Release:

• Adds new preference MaxLinesForNoteDisplay which defaults to 4, but can be set to any value to constrain the note field from unlimited expansion when handling really long notes. In the Edit dialog, you can tap the Note icon in the left margin next to the note to force the field to temporarily expand to display the entire note, or tap it again to return it to the number of lines constrained by the preference setting.
• Speeds up selection of repeat exception options by providing separate buttons in the Repeat Exception dialog along with graphics.
  
  

• Moves the location field down in the Edit dialog to just above the Group Field. The logic for this is that it moves the note field up making it more convenient for users who frequently update the note field. The location field is typically only edited once on the initial creation of the note, and since it is also displayed in the Event Selection List, the need to look at it in the Edit Dialog is clearly lower in priority.
• Fixes issue of not being able to use these three menu commands: Exit, Show Alarm List, Sync Now as gestures  (previously they were only available to use on command bar buttons).
• Forces sentence-capitalization in Daily Journal entry dialog.
• Avoids reading memo files that were completely empty (considered a potential problem on some devices).
• Updates preference templates to include the Undo Edit command which was put into P/A V-3.2.04, but was inadvertently missing from the preferences (so most likely no one noticed it was even available!). You may need to go into preference MenuCommandsAndOrder to enable the display of this menu command.
• Ensures that in the Repeat Rule & View pane when editing a filter, that when the Date Picker is displayed for the start/end dates, that the and None and Week buttons are hidden - as tapping the None button can cause problems (as it makes no sense to have a repeat without a start date!). Also now checks for an invalid Date in the filter and ignores the repeat specification (previously this would cause a NullPointerException error).
• Also avoids displaying the legend about the special Monthly repeat type in the Repeat Rule & View pane when editing a filter and the filter has no repeat set yet.
• 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.
• Avoids querying user about discarding changes in the Memo Edit dialog when cancel is pressed and the only difference is in the number of trailing spaces and end-of-line codes.
• Ensures that the alarm icon is drawn in the event selection list and main views if any one of the five alarms is set (in theory, if any alarm is set, the primary alarm must be set, but in reading alarms from other calendars, etc. this can not always be guaranteed) - the alarm itself would go off properly anyway - this was just an issue of displaying the alarm icon.
• Fixes problem with changing instances or deleting repeat events in an Android calendar, especially on second or subsequent exceptions where Pimlical was updating the repeat series itself which then in turn had the unexpected effect of causing Google's Android Sync software to remove all the attributes from any prior exceptions (yet still maintaining the items as exceptions!!). Note that because of this, if you edit the repeat series in Pimlical, Pimlical will only apply those attribute changes to the repeat series itself, not the exceptions. However, on syncing the item into Google calendar, any exception events will be automatically updated as well with any changes (this is consistent with how Google calendar itself operates). But for repeat series in the local calendar, a change to the repeat series never affects any previously created exceptions.
  

New Features in this Release:

• Fixes issue of sometimes not writing out database with the updated Last-Access date/time stamp (which in turn would mean that the Recent Items list might sometimes not include an item that had in fact been accessed recently).
• The repeat button in the Edit dialog now displays a legend if an item is (or was) an exception to a regular repeat series.
• Avoids an Android OS bug whereby a long-press on a command bar button caused the Android OS to report a scroll event (!!) to Pimlical which in turn was causing a brief tap to be processed on that button as well (Pimlical now just ignores the spurious scroll event).
• Fixes a spurious verifyFieldDescriptor() error message that was caused by a now-deprecated field in the calendar database.
• Fixes an obscure fault in Menu | Backup | Restore Everything, when a file with the name PimlicalLocalCalendar.dat was located in the Pimlical Folder (generated a File not Found error on the restore). Obviously, this file is normally in Pimlical/PimlicalCalendars, but if it was manually copied to the Pimlical folder for some odd reason, it would generate this unexpected error.
• Fixes a somewhat obscure problem where Pimlical will read a custom preference file (that was not deleted) even though the filter currently was not marked as having a custom preference file. Under those conditions, updates to the default preference file were being inadvertently written to the custom preference file (that is no longer actually in use) and so the settings seem to "not stick" (this had been reported as an issue seen by some advanced users that were presumably using custom preference files AND subsequently resetting the filter back to not using a custom preference file). At one time, those files were automatically deleted when the checkbox (Save Custom Preferences with Filter) was unchecked, but that code was removed, hence causing this issue - that code has also been restored as it is appropriate to clean up the Pimlical folder with files that are no longer needed.
  

New Features in this Release:

• Fixes issue in memos of not consistently handling the optional display of the on-screen keyboard depending upon preference setting, and also ensures that the text area is selected for the top/bottom of memo button (as well as find function).
• Fixes issue of informative messages in memos section not displaying (such as mentioning there were no more matches, etc.).
• The Created and Modified dates displayed for memos are now adjusted to the user's current timezone (previously in UTC).
• The created/modified dates displayed for contacts is now adjusted to the user's current timezone.
• Fixes an issue of importing memo text files that do not have the old [dts...] date/time stamp (i.e. re-importing exported memos, importing memos from some other source, etc.) - problem was that only the title was importing and not the main text.
• Going into menu | Select Calendars now forces the re-read/refresh of the calendar list and in particular forces the re-processing of the preferences that adjust the Google calendar colors (such as LightenGoogleColor).
• On importing memo text files, if there is no [dts..] date/time stamp (as will be the case going forwards), the creation and modification dates for th memo are initialized to date/time stamp of the file itself (in the filing system), or if not present, to the current date/time.
• 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).
• Addresses the problem of using the preference LightenGoogleColor which was not being applied in most cases - the correct way to handle this now is to go into Menu | Select Calendars, tap on the calendar to edit, tap on the color to edit the color and tap the Remove button, then on exit back to the main screen, the new value will be applied. Note that the colors in the Android calendar database do not match Google Calendar. Unfortunately, this is a liability of continuing to provide support for users on Pre-OS4.x Android systems - and is yet another reason why support for versions of the Android OS prior to 4.x will likely be dropped by the end of 2015. So if you don't like the default calendar colors, just pick the colors you do like as there is nothing to stop you overwriting the default google colors.
• Feature to remove deleted records from the local calendar now always removes deleted records (previously, it would only remove deleted records if the database had been marked as modified). Also includes Information dialog specifying number of records actually removed, and the backup/rewrite of the database only takes place if in fact some records were going to be removed.
• 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 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.
• If Android OS is 5.0, the memo dialog is now destroyed and recreated on every invocation in order to workaround the known bug in Android 5.x whereby the Command/Edit bar (for Copy/Cut/Paste etc.) fails to display.
  

New Features in this Release:

• Fixes problem of deleting This and Future Instances of a repeat series from an event selection list (by going into Edit dialog and selecting Delete) still displaying the event on exit from the Edit Dialog (event was properly updated - just wasn't removed from the display until it was refreshed).
• Any time a contact is updated or created, the last access date is now set to the current time. For example, after sharing a newly created contact from the native Android contacts app with Pimlical Contacts, you can then just go into the Recent list in Pimlical/Contacts and the newly shared contact will be at the top of that list.
• Works around OS alignment bug that was causing GoTo button in the Event Selection dialog to be mis-positioned.
• Adds sectionIndexing feature to Memos list so you can quickly move to memos that start with a particular letter.
• 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 an obscure issue on startup where Pimlical on occasion may report an exception error the first time around, if your startup view is one that includes the new animation feature (such as month or week views).
• Fixes issue of the day view not being fit to the screen right after first launch of Pimlical.
• If the preference or calendar file rename fails (Anti-virus software or perhaps some Android function?) 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 transition issue from old to new calendar database file format that could potentially cause a corrupt calendar database.
  

New Features in this Release:

• Names of Audit trail file now appears as Pimlical_Android_AuditTrail.txt (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.
• Fixes some minor internal issues with the database update which were causing issues during DirectSync.
• Fixes problem of sorting repeat items by Date in the Find Dialog when using a filter and the preference ShowInstanceDates was true (it was not sorting by Date/Time using the next/current instance of the repeat item, but rather just by the start date of the item). This is not as esoteric as it sounds - setting up a filter to show upcoming birthdays and/or anniversaries, starting from today is a useful function and immediately exhibited the problem in the prior version.
  

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 new preference: AnimateTodaysDate which makes it visually easier to locate today's date in all views (other than the day view where it's never an issue) by fading in all other days over a brief period of time (on the order of a second or so). The preference itself specifies the number of steps in the fading - with a value of 0 disabling this feature. The default value is 40.
• 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.
  
  

• Restores lost feature (which apparently no one ever noticed?!) of preserving the date header in the list view while scrolling, and also fixes the issue of scrolling up and having some "resistance" to the scroll when moving to a prior day.
• Fixes some obscure display issues in the main views that scroll (most noticeable in the day view) whereby the bottom of the screen was not being managed quite right.
• Changed the width of the vertical column that you move your finger to scroll in from 1/3 (of screen width) from left and 1/4 from right to 1/4 from both sides - seems to work better and be more consistent.
• The advance Time dialog now takes the current timezone into consideration when displaying the date/time for the associated item (such as setting an alarm on an event).
• Fixes an obscure issue when multiple links were displayed for an item whereby under some unusual conditions, the selected link would be removed rather than display the linked contact or memo.
• Makes it easier for novices to recover from a corrupt/mis-edited Worldtimezones.txt file - you can now simply delete that file in the Pimlical folder, and go into menu | preferences | DateTime Items and Pimlical will automatically re-install that file from the default copy embedded in the program.
  

New Features in this Release:

• Includes both the screen resolution and physical screen size in the About dialog (actually added in a slightly earlier version).
  
  

• Fixes issue of not displaying the correct Birthday/Anniversary year when event had Birthday or Anniversary Action tag with no explicit year followed by some other Action Tag (previously, treated it as if the starting year was 0).
• Fixes issue of editing a repeat event and then returning to the Event Selection List and not having that event displayed (only occurred in some circumstances in some views).
• The file/folder navigation list displayed in the Set Link To File popup command is now sorted with a case-insensitive alphanumeric sort (previously it was case-sensitive).
  
• Remember to set the preference FingerSlipThreshold to -1 to select an appropriate value for your device. 

New Features in this Release:

• Adds new preference EditDialogQuickReturn which if set to True results in the Edit Dialog returning directly to the main View rather than returning to the Event Selection List. Default value is false which preserves the existing behavior.
  
  

• Includes potential workaround for obscure error message in Alarm handling where it looks like Android OS loses track of some internal information (Pimlical now refreshes this on each alarm).

New Features in this Release:

• Has a new algorithm for addressing the issue of the user's finger slipping on the screen when attempting to tap that seems to work much better. To use this feature, set the preference FingerSlipThreshold to -1 (which is also now the new default value). Pimlical will then use the current screen resolution and screen size to set a default slip value of 1/10th" (2.5mm) which seems about right to catch all the errant slips that the Android OS interpreted as a Fling gesture when in fact the user was just trying to tap the screen. This threshold value can of course be set to any desired value, but by setting it to -1, a reasonable value is picked automatically for a new install.
• Fixes issue with new Set Link To File feature whereby the hyperlink seemed to get set but would subsequently get lost or not get updated properly.

New Features in this Release:

• Implements the Deferred status type in Edit and Find dialogs (it was already supported in filters). Deferred floats and tasks are not subject to the constraints of normal floats and tasks (i.e. cannot display on a prior date, etc.) and are often used for items that need to be done, but for which no date has yet been assigned yet (mostly useful when using filters, for examle, you can filter out deferred items normally, but also get a list of just those deferred events that need to be set to a schedule).
• Adds new Popup command: Set Link To File. This brings up a file navigator and allows you to select any arbitrary file in the local filing system and will then insert an appropriately formatted link into the note field (using the File:// tag). Links can be set to any file type, and when invoked as a hyperlink, the Android OS should prompt you for an appropriate application to be launched to manage that file. This function has always existed in Pimlical/Android, but only this release provides a convenient file navigator to select a file in the local filing system to link to (and also remove the link without having to edit the field). This is useful for attaching things like photographs, sound files. Remember that linking to a web page is simple (just Select All/Copy web address in browser, switch to Pimlical and paste into end of note field).
• When editing a contact, you can long-press the label in the Phone, Email, Address, or Custom Fields to move that item to the top position in the list (convenient for selecting the phone/address that appears in the selection list, etc.).
• Adds two new options that can be put on the command bar: left and right double-arrows that move to the previous or next week (unless you are in the month or multi-month views in which case it moves by a year).
  
• You can now create a new, empty local calendar by going into Menu | Select Calendars, unselecting all Android calendars (so there would be nothing to import) and tapping the blue [+] button.  You can quickly populate this newly created calendar using the Multiple-Select command in an event selection list of some other calendar and using the Copy and Paste functions.
  
  

• Clears up some inconsistencies between Pimlical/Desktop and Pimlical/Android with regard to dated and undated floating events and tasks by enforcing a much simpler rule. Changing the due date of a task no longer changes the start date and vice-versa. In other words, the start date and due date are now completely unlocked from each other. This also means that if you change the date of an undated float or task, it remains undated. While there are cases where it would be desirable to change these items in lock-step, there are equally many cases where a user would not want that to happen. If you change the start date of a float or task that is due in ten days to tomorrow - would you really want the due date to change? In most cases, you are viewing the start date as an advance reminder and would be only moving the reminder to tomorrow's date.
• No longer folds path strings specified using Http://, File://, Https://, www. or MailTo: tags in the description/note/custom/link fields (could potentially cause problems linking to a file where the path was case-sensitive). 
• Optimizes the deletion of a very large number of events in an Event Selection List (now some 10 times faster).
• Now ignores proprietary iCalendar Tags within the scope of an Alarm Block (previously, such custom tags would result in the alarm block not being properly processed in most cases).
• Now handles an iCalendar entry where there is a Yearly Repeat Specification that inadvertently omits the month of year and which also precedes the setting of the date and time (seen in some calendars created by other calendar applications).
• Now checks to see if there was a uniqueID for an event in an iCalendar import file and if so and there is an event already in the database, the event is not imported. A count of all such skipped records is provided at the end of the import and the audit trail file will include the description of the skipped entry (if DebugMode preference is set to True).
• Fixes a problem in the popup command list that was causing one or more items not to display when selecting/sorting those items in preferences. You may need to go into preferences, select PopupListCommandsForEvent and make sure you unselect an entry that just says Details (and only just Details) as that was as spurious entry from an older version of Pimlical/Android.
• Ups the default value of the preference: FingerSlipThreshold to 5 (used to be 1) as that seems to be a better starting default value.
• The hyperlink button in the Edit Dialog now supports a long-press which will always display a list of hyperlinks (even if there is only one) and also includes a Remove button to remove the selected hyperlink from any field where it might have been inserted (description, note, link, custom fields).
• When displaying the anniversary/birthday in an event selection list, it now properly shows the years based upon the date displayed for the event - in particular for repeat events the date shows the next instance of the repeat on or after the current date, and the anniversary/birthday should reflect that date (previously, if the repeat instance was in the past, the birthday/anniversary would have been calculated from that past date even though the date displayed in the event selection list was the next instance.
• When invoking a new filter, Pimlical now automatically clears the [S] condition (i.e. if all events/tasks are being forced to display, this condition is cleared as the new filter is applied so that events hidden by the newly applied filter are indeed hidden).
• When rotating the contents of a contact's phone/email/address/custom fields, the dialog now remembers its scroll position so the now top item is displayed (previously, the dialog would scroll all the way back to the top).
• The list of Local Calendar files is now sorted into alphabetic order, and the Restore list now excludes any files with _Updates as part of the filename.
  
• 
  

New Features in this Release:

• Optimizes the resolution of alarms for events in an Android calendar immediately after refreshing the database so as to avoid what could be a significant pause in the program if there were a large number of past events with alarms set (which obviously could not be potential candidates for an upcoming alarm as Android calendar events do not support Pimlical's post-start-time event alarms).
• Fixes a new issue in a fairly recent release whereby changing the status of an instance of a repeat series, when syncing to an Android calendar could cause duplicates under some conditions.

New Features in this Release:

• The feature in 3.3.01 of using generic font sizes has now been deferred to V-3.4 (because it introduces a new field in the database that can cause forwards-compatibility issues when syncing, using Widget, etc., so it has been deferred until 3.4 which resolves the forwards-compatibility issue).

New Features in this Release:

• Pimlical now makes it possible to select custom font sizes that look good on all platforms by storing custom font sizes for events (and templates) as a generic index into a table of fontsizes rather than as an absolute font size. This table is defined by the preference: ListOfFontSizes. So instead of indicating that an item is in 24 point, it would indicate that it is the 9th item in that table. That way, when the event is read on some other platform, the fontsize will be defined as the 9th item in that table which can be a different size. Typically, fontsizes selected in P/A are far too big for P/D (due to high resolution of phone screens vs. PC screens). By tweaking the values in these tables, you can ensure that fonts look good on all platforms. There is no restriction imposed on the number of items put in this table, but you should make sure that the tables have the same size on all platforms that you sync to. By default, the font sizes map to the same values. If you use custom font sizes that look good on Android, but too big on the desktop, you could, for example, try setting that preference on the desktop to something like: 6|7|8|9|10|11|12|13|15|16|17|18|20|22|24|26|28|30|36. Alternatively, if they look good on the desktop but too small on Android, you could change the Android table so it uses much larger pointsizes. Requires Pimlical/Desktop 3.2.06 or later. (Note: this feature now deferred until V-3.4.1).
• Advances can now be set after the event date - they will appear as negative values, so -1d means the "advance" reminder will appear one day after the event. Pimlical also automatically inserts the NK (No Kill) Action tag for the event (as otherwise the 'advance' reminder would disappear on the next floating update). This feature has always been supported in Pimlical/Desktop, but the user interface prevented the user from creating such advances in Pimlical/Android until this release (but synced, negative advances were handled properly by P/A).
• Adds new preference: DaysToShiftBy.  This applies to the List, Day+ and Weekly views. In those views, if this preference is set to a value other than 0, it specifies how many days by which the view should shift on the left/right screen gesture - previously (or now if this preference is left at its default value of 0), it would always move by the number of days in that view. In the weekly view, if there is more than one week displayed, then it will cause a shift by that number of weeks instead. This preference does not affect the left/right arrow buttons on the command bar.
  

Fixes/Changes in this Release:

• Fixes problem of not being able to set an explicit end date for a filter (when Fixed Date option is selected).
• This release has the first phase of the implementation of database forwards-compatibility for events, templates and filters. The second phase of this implementation will occur in a future 3.4.x release. With this change, it will be possible for an older version of Pimlical to read calendars, templates and filters from a newer version of Pimlical even if that newer version has a new file format with new features (currently such a case would typically cause Pimlical to crash). While Pimlical has always had perfect backwards compatibility, providing for forwards compatibility is obviously more challenging. The change is being done in two phases to alleviate the forwards-compatibility problem of implementing this feature (!). I.e. if this change were done in one phase, then if a user had Pimlical updated on Android automatically before they had a chance to realize they needed to update the desktop to be compatible, they would end up with an incompatible database and a crash. So phase 1 implements the feature of reading this new forwards-compatible database format, but the writing of this format won't occur until V-3.4.x. So by the time V-3.4.x is released, hopefully everyone will have this version which is already set up to read this new database format.
• Fixes issue of the Edit button in the Alarm dialog not always displaying the Repeat Exception Dialog when the item was a repeat event. When the Edit button is used on a repeat event, and if the user chooses Just This Occurrence or This and Future Occurrences, Pimlical will use the instance on today's date or that occurs next after today's date. In 99% of the cases, this will be what the user expects, but there are cases where it might not have been the instance that triggered the alarm. For example, the alarm might have been a post-start-time alarm from an earlier instance, or it might have been a future instance where the alarm preset was in fact greater than the time between instances, or it might have been an alarm that had been snoozed from an earlier instance. None of these are likely, but they can occur and in those cases, the instance that the Edit button addresses might differ from the one that actually triggered the alarm.
• Fixes new problem of resetting preferences by deleting default.txt, but then getting a termination message from Pimlical.
• About Dialog now displays number of records in the local database as well as the total number of records.

New Features in this Release:

• Adds new preference: FingerSlipThreshold with a default value of 1. This preference defines the threshold for inadvertently slipping finger on screen so that Pimlical can discriminate between a fling or scroll and a brief tap or long press that the finger slipped while performing. Increase this value if you find that taps or presses are being ignored (as likely instead of a tap or press, Android is interpreting it as a fling or scroll). This will become increasingly useful as even higher resolution screens appear and the Android OS continues to fail to properly update their internal threshold values based upon screen resolution (4k screens are coming!).
  

Fixes/Changes in this Release:

• Fixes problem of linking to a contacts in the local contacts database that has first/middle/last name fields all blank (the company name is now used in those cases) - previously in those cases, the command to display the links would show a blank entry.
• Fixes problem in Tasks View whereby the wrong template was being inserted/selected when the [Q] button was tapped in that view and the Template Selection List was being displayed.
• Fixes problem of deleting all templates from the Tasks View (the Event Selection List was not being redrawn after deletion and tapping on the screen which was displaying the main view could cause an exception error).
• Separates out vibration from alarm sound vis-a-vis the preference AlarmSoundPlayTimesCount being set to zero (so now, if it's set to zero, vibration can still take place if permitted by preferences - previously, if that preference was set to zero, it would suppress both the alarm sound as well as vibration).
• When displaying a category list from preferences, instead of displaying a 'Remove' button, the button legend now says 'None' to make it clearer that the button is not removing the category, but simply removing any categories from the preference setting so it remains blank (such as setting a category for the preference: ApptCategoriesToSync, etc.).
  

New Features in this Release:

• What may be a significant change for some users has been made in this release, to improve consistency by simplifying the rule on popup commands when applied to repeat events: Popup Commands applied to repeat events always affect just one instance of the repeat series and never the entire repeat series. To change the repeat series, you go into the edit dialog.  So popup commands like Delete and Advance always create an exception to the repeat series and apply the change to that instance. Previously, if the event selection list was created from a Find, Upcoming Alarms list, or group find list, the command would operate on the entire repeat series. This created problems for users as it was not immediately obvious in some cases whether a popup command would apply to the entire series or just one instance. In the case where there is a repeat event, but no specified day (as would be the case from a Find operation), the change is applied to first instance on or after today's date. If there are no more instances of the repeat, an error message appears on the screen and the command is ignored.
• Adds new preference LongDurationForMessages which displays popup messages (referred to internally in Android as "toasts") display for a longer period of time.
  

Fixes/Changes in this Release:

• Fixes problem of a repeat event, that had had exceptions made in the past, displaying both the regular repeat icon and the repeat exception icon on the same event in the main views (the event selection list did not have this issue).
• Fixes problem of not updating the event selection list after the Toggle Alarm command was used.
• When selection list is empty, a brief message appears stating that the list is empty (for example, after deleting the last match on a find function, etc.).
  

New Features in this Release:

• Adds Edit button to the Alarm dialog. If just one item is selected in the Alarm dialog, the Edit button will bring up the Edit Dialog so the item can be edited (provided that the alarm itself did not trigger over an item already being edited in the Edit Dialog). If other items are present, they are auto-snoozed for the default snooze interval (they can of course be easily retrieved using the Android notification feature).
• The alarm icon in the Alarm dialog now toggles all items from being selected to unselected (previously, it only marked all items as selected). With this new functionality, the None button has now been removed from the Alarm Dialog to make room for the new Edit button
• Adds GoTo menu item as optional function to put on the Command Bar. However, before rushing to set this option, remember that a long-press on the left-arrow button already performs that identical function and so you may want to reserve the button for some other function.
• Adds Pimlical Exit, View Upcoming Alarms, Sync Now and Refresh Calendars menu items as optional functions to put on the Command Bar.
• When adding dates to an irregular repeat series, the list of all the child events now displays the newly entered dates in chronological order (newly added dates appear after any dates that had been previously set, and are marked with an asterisk).
  
• System icons have been added to identify exceptions to repeat series () and children of an irregular repeat series().
  

Fixes/Changes in this Release:

• Fixes issue with group numbers that had a trailing or leading space (if created in a prior version that let the space slip through, they could then appear multiple times in the group selection list).
• When creating an irregular repeat series, the Repeat button in the Edit dialog is now immediately updated with that information (previously, it would not display the irregular repeat until the item had been closed out and recalled to the Edit Dialog).
• On-line manual has been updated for these new features and new sections have been added to cover the Date and Time Picker dialogs.
• If an item is both a regular repeat series and the parent of an irregular repeat series, then only the icon for the regular repeat series is displayed. The parent of an irregular repeat series displays this icon: 

New Features in this Release:

• Group names are now sorted alphabetically in the Group selection list (an issue for users who had a large number of group names).
• A long press on a day button in the Pimlical Date Picker now saves that date as the Pinned Date (as well as displaying the current week number for that day).
  
• A long press on the right arrow button on the command bar now goes to the Pinned Date (previously, it redundantly functioned like the left arrow button).
  

Fixes/Changes in this Release:

• Pimlical no longer enforces "sentence-case" on group names when displayed. Also prior versions were not checking for unique group names when the New button was used in the selection dialog for groups.
• Fixes an issue in the day view when the last item on the day was close to the last timeslot on the day, whereby the display of the last time slot was getting influenced by that item. Previously, the program would suppress the last time slot if the last item on the day ended on the precise time of the start of that last timeslot.
  
• Moscow timezone is now set to +03:00 (was +04:00 only through end of 2013). Since timezones are cached, you would need to go into menu | Preferences | Date/Time Settings and tap the Done button to refresh those settings.
• Fixes some system icons for compatibility with Pimlical/Desktop.
  

New Features in this Release:

• Adds Undo Edit menu command. This will undo the last edit and go to the Day View with that record displayed (if it was a repeat record, it goes to the first instance of the repeat series on or after today's date). If invoked a second time, it reverses the action (i.e. the restored record is replaced by the last edit that was made). You can only Undo Records in the current sesssion.
  

Fixes/Changes in this Release:

• When an alarm on a repeat event was snoozed past midnight and the preference SpeakAlarms was set to True, P/A was using the date of the next repeat occurrence - this version now starts looking for the repeat instance from the prior day (on all repeats except a daily repeat) and would now report the date of the original instance. This works in all cases except for daily repeats and cases where an alarm is snoozed across more than one day (neither is an issue that really needs to be addressed though).
• Adds line to About dialog to indicate number of error files found in the Pimlical folder. Also, all error files now have an extension of .LOG instead of .TXT.
• When the preference CalendarNamesAreUnique is set to false, there were issues in prior versions if the user attempted to set unique attributes for the calendars with duplicate names (the attributes could get applied to both calendars, etc.). In this release, if the preference is false, duplicate calendar names now have _1, _2 appended to the name to distinguish them.
  

New Features in this Release:

Fixes/Changes in this Release:

• When rebuilding category tables and processing category names, Pimlical now ensures that any spurious leading and trailing spaces are removed - under some conditions, some users were getting what appeared to be duplicate category names because of those spurious spaces

New Features in this Release:

Fixes/Changes in this Release:

• If an error occurred while reading the calendar, or performing some other activity in the background, the original error message was getting overwritten and lost - this release corrects that issue.

New Features in this Release:

Fixes/Changes in this Release:

• Under some startup conditions, it was possible that the Android calendars did not get read in prior releases - this issue is now addressed.
• When updating the end time of an event in the Edit dialog, Pimlical now no longer adjusts the end time when the end date/time precedes the start/date time - rather it first sets the end date to the start date, and if the date/time still precedes the start date/time, the end date is advanced by one day. But if updating the end date and the resulting date/time precedes the start date/time, the end time is now adjusted to match the start time. This seems to be less "annoying" when a simple mistake is made in closing the Date or Time Picker with an invalid date/time set as it is easier to fix the date than the time field. If you start an event at 8pm and then enter an end time of 7pm, the date is automatically advanced to the next day, so this makes it a lot easier to enter events that span midnight.
• When setting the start/date time of an event to the current date/time, Pimlical now sets the correct duration if it is a floating event (from the preference DefaultFloatDuration) - previously, a floating event would have had its duration set by the DefaultApptDuration preference.
  

New Features in this Release:

Fixes/Changes in this Release:

• Includes more comprehensive warning about the delete function on an event selection list when it is only going to delete an instance of a repeat series.

New Features in this Release:

Fixes/Changes in this Release:

• Fixes an issue with missing a very specific (but also uncommon) class of alarms.
• When adding new alarms in the Edit Dialog, the alarms are now immediately sorted into the correct order (previously, alarms were only sorted on exit from the dialog).
• The Advance Time Dialog now displays the proper instance date of a repeat event that has post-event time alarms set (previously, was displaying a later occurrence in the title).
• Advance Time Dialog now includes more comprehensive checks for invalid values (such as setting an alarm more than 28 days in advance of an event in a Google/Android calendar - since that is not supported in Google calendar, or setting a meaningless value in some cases - i.e. when used to set a duration etc.).
• Fixes issue when displaying upcoming alarms list and an item is deleted (previously, the list was not properly rebuilt to reflect the deletion).
• Fixes UncaughtExceptionError if just one or two digits is typed into the Quick Entry Edit window (and nothing else).

New Features in this Release:

Fixes/Changes in this Release:

• Small internal change in alarm handling to avoid possible timing problem of duplicating snooze alarms if Back button is pressed really quickly after snoozing alarms.
• Fixes an issue in the Advance Time/Duration dialog where adjusting minutes was not properly updating hours and updating hours was not properly updating days (when going over an hour/day boundary). Also now properly handles negative alarm values (so you can set an alarm that goes off after the start time (example: -1h30m would go off 90 minutes after the start time for the event). This feature is only supported in the Pimlical Local calendar.

New Features in this Release:

Fixes/Changes in this Release:

• Changes the test for including modified/updated contacts to treat a match on the date/time stamp as meaning that the item WAS updated (in theory, this should have no affect on anything, but some users were reporting that if they made the change to a contact and tried the merge/Update function in P/A within one minute of making the change, the change did not seem to propagate until later).
• Fixes another issue of using the Share function from some other calendar application when Pimlical Contacts was not running (was causing a Pimlical Has Unexpectedly Stopped Error message). Note: to use this function, be certain that Pimlical itself has at least been launched one time (if never launched, or force-stopped, the share may fail with a Unfortunately, PimlicalA has stopped error message.

New Features in this Release:

Fixes/Changes in this Release:

• Fixes problem in using menu | Restore Contacts (DAT) in contacts dialog (was falling into code to show deleted records only).
• Fixes issue of using the Share function from some other calendar application when Pimlical Contacts is already running (was causing a Pimlical Has Unexpectedly Stopped Error message).
  

New Features in this Release:

Fixes/Changes in this Release:

• Fixes issue of using the third Alternate Time Picker ( the default one with digital entry of time) and setting an invalid digit (i.e. 6-9) in the first minutes position (i.e. the tens digit) and then tapping OK button (previously, the invalid digit was set in the time).
• Incorporates better recovery from Android OS failure to rename file (also possibly caused by badly designed AntiVirus scanning routines, etc.) by first attempting to local the TMP file and if that is not present, the BAK file.
  

New Features in this Release:

Fixes/Changes in this Release:

• Fixes new problem with selecting contacts by category when the preference MultipleCategorySelection is set to False.
• Fixes issue of a user selecting multiple items and then inadvertently issuing a short tap on a selection list other than the undelete list - the event selection list would end up duplicating the item in the list.
• Adjusts the logic for the removal of the extra time slot at the end of the day to include an extra time slot if the event starts after the timeslot boundary (example: if item runs from 10:00 to 10:45, the last time slot (if 60m time slots) would be the 10pm time slot, but if the item ran from 10:10-10:45, then the last time slot would be at 11:00am. This extra 'fudge' factor is needed to avoid truncating the display on the last item.
  

New Features in this Release:

Fixes/Changes in this Release:

• Fixes problem with the new preference: PopupListCommandsForMultiSelect which was not being displayed properly and could result in some error messages. Check the preference out and make sure that at least some items are listed for display (most likely you will want all commands available to display).
• Fixes an issue with importing/exporting filters whereby default filter got unexpectedly marked as having a custom preference filter. You may want to export and re-import your filters if you had used this new command previously.
• Now displays a warning message if an attempt is made to use a popup command items in the Menu | Undelete list (they have to be undeleted first before applying a command).
• The First/Middle/Last name fields in the contacts edit dialog now support auto-capitalization of subsequent names in the same field.

New Features in this Release:

• Adds multiple select button() to Event Selection List Dialog. When tapped, selection boxes appear in the left margin of the Event Selection list so that multiple items can be selected. A long-press on any item and selection of another command then applies to all currently selected items (the long-press when in multiple selection mode does not select another item). Not all popup commands are available in multi-select mode (delete, all advances, toggle completion/cancellation and the Copy command are available). The preference list for items in multi-select mode is managed by the preference: PopupListCommandsForMultiSelect. A long press on the Multiple Select button always sets Multi-select mode and alternately toggles between selecting all items and no items.
• A brief tap on an item when Menu | Undelete has been invoked and multiple items are selected will undelete all selected items (if only one item is selected, the Edit Dialog is displayed as before).
  
• The color selection dialogs have been revamped for consistency and to make color selection simpler for the majority of users. When selecting an event color, a long press on the foreground or background swatches in the main color selection dialog (the one that shows the 16 palette colors) now invokes the Color Swatch dialog which allows direct selection of a color from a big selection palette. There is a button in that dialog to select the RGB color slider selection dialog for precise setting of colors. The calendar/category edit dialogs now invoke the main color selection dialog in the same way as you would select an event color (and again you can access the color swatch dialog and the RGB color slider dialog if you wish). For color preferences, the Color Swatch Dialog is displayed first (since it's unlikely that the main color dialog would be applicable), and again the RGB Slider dialog is available for precise setting of colors.
  

Fixes/Changes in this Release:

• A protective measure for older versions of the Android OS (display issue) has been removed - which was adding an extra time-slot at the end of the day. With this change if the last event on the day runs from 6-7pm for example, there will be no 7-8pm time slot (as would have been the case previously).

New Features in this Release:

Fixes/Changes in this Release:

• Fixes an obscure issue in the advancing of floating events for items in an Android calendar. Under some conditions, the update to the event could get lost and it would appear the advance was not working properly.

New Features in this Release:

Fixes/Changes in this Release:

• Fixes problem of memo files being unexpectedly truncated to 255 characters when an external text file is dropped into the Pimlical/PimlicalMemos folder as a way of importing a file into the memos database.
• Fixes an obscure issue of updating the modification date on a repeat, floating event when updating it to the next repeat occurrence in the floating advance routine (fairly benign - just caused an unnecessary sync of the event).
  

New Features in this Release:

Fixes/Changes in this Release:

• Fixes problem in Tasks View on certain newer versions of the Android OS whereby a tap on the Priority or Urgency buttons was causing an Exception Error.
• Removes the brief message about syncing a new calendar in menu | Select Calendars when tapping the Green Done button due to ongoing Android bug whereby the Android OS fails to remove the message from the screen (and in fact you have to force-stop the application to get the Android OS to properly remove that message!).
• Now handles the generation of timezone information in iCalendar export (menu | Select calendars) for the event start/end date/times in such a way that other calendar apps that properly handle the timezone information will preserve the original timezone information and also possibly handle floating times properly.. Google fails to handle the iCalendar specification properly and loses the original locale information (although it continues to be preserved in pimlical via the tag in the note field).
• Fixes problem on some versions of AndroidOS whereby using the feature to make an Exception of  This and Future Occurrences was resulting in the future occurrences not being recorded in the Android database (which would cause them to then disappear from P/A on thenext refresh).
  

New Features in this Release:

• Now supports multiple category assignments/searches in the Contacts section if the preference: MultipleCategorySelection is set to True.
• If the preference: MultipleCategorySelection is set to True, the category selection dialog (for both calendar and contacts) now manages the Unfiled category as a "special" category - in particular, if you select the Unfiled category, all other categories are automatically unselected. if you select any category other than the Unfiled category, the Unfiled category is unselected. This now matches how Pimlical/Desktop handles category selection
  

Fixes/Changes in this Release:

• Now forces a re-read on the database prior to advancing floating events (it's possible in prior versions that some of the issues that were occurring at the Float Advance Time were due to the database being in an indeterminate state due to Android OS memory management issues).
• Ensures that Floating Advance is always performed at Float Advance Time (under some conditions, in the most recent version, the advance might have been skipped at that time.
  
• Now addresses possible failure to re-read entire calendar file after low memory conditions have been present.
• When searching contacts, the custom vCard field is no longer searched (unless just the Miscellaneous field is checked) as it was causing more problems to scan that field than to exclude it.
  

New Features in this Release:

• Adds function in Menu | Debug to remove all duplicate records in the calendar database.
  

Fixes/Changes in this Release:

• When deleting a category a check is made that the category is also not in the list of exclusion categories for a filter (previously, only the categories in the inclusion list were scanned).
• When rebuilding the category tables, any categories used in the inclusion or exclusion list of a filter are now also included in the newly rebuilt list (previously, they had been ignored).
• Avoids generating an UncaughtExceptionError when a user attempts to use the iCalendar import function and yet had never ever saved any calendars in iCalendar format.
• When creating new events, the time of the event is now truncated to the nearest minute (previously it was rounded up to the nearest minute).
  

New Features in this Release:

Fixes/Changes in this Release:

• Fixes problem in iCalendar import whereby if the DTEND: tag precedes the DTSTART: tag (not something that programs usually do of course), and the event spans more than one day, the event does not import properly due to a spurious NullPointer exception error.
• If the operating system fails on renaming the PimlicalDBs.dat file, an attempt is now made to recover from the temporary file when re-reading that file (this issue was occurring sporadically in 3.1.14-G only).
  

New Features in this Release:

Fixes/Changes in this Release:

• Now includes a test for trying to make an event that was formerly an instance of a repeat series into a new repeat series in an Android calendar. While Pimlical has no such limitation, Google calendar can not handle this condition, so this is now flagged as an error if the event is in an Android calendar as it will cause a fault when the event is synced to Google calendar.
• When exiting the tasks view, the previous filter in effect is now re-applied (so that if the filter for example moves to Today in the DayView, that view will appear with today's date on exit from Tasks View). Previously, the filter was not re-applied.
• Fixes an issue in DirectSync - namely that advance reminders created from regular events were not preserving the original modification date of the target event - that could under rare circumstances result in a modification to that same, newly created, advance reminder on the other platform getting unexpectedly overridden (this is very similar to the issue that was fixed previously with the floating reminders created from repeat, floating events).

New Features in this Release:

• Adds new popup command to contacts screen to share a contact in vCard format.
  

Fixes/Changes in this Release:

• Has some internal changes to address obscure issue on some phones whereby alarms get auto-snoozed almost immediately. This fix, however, does present an issue if the user presses the Home button while the Alarm/snooze dialogs are displayed in that it might not cause the pending alarms to be auto-snoozed.
• Fixes an issue with filters whereby a task that has an advance might get included even though it should have been rejected based upon some attribute other than the date range test.

New Features in this Release:

Fixes/Changes in this Release:

• Clears up some inconsistencies in how the end date and time are managed in repeat filters. The end date for the filter is now set only in the repeat specification. The start/end times apply to each day on which the filter's repeat specification indicates the filter will run. Only if the filter's start time is earlier than the current time, and the filter's end time is later than the curren time will the filter be a candicate for being automatically invoked. If there are two or more repeat filters that conflict, an appropriate error message is now displayed identifying the problem filters. Only one filter should ever be a valid candidate to be run at a specific time.
• Fixes problem of a long-press on the repeat end date for a repeat filter that was not allowing the number of occurrences to be entered.
  

New Features in this Release:

Fixes/Changes in this Release:

• Includes a test for certain versions of the Android OS that can cause alarms to get unexpectedly auto-snoozed (i.e. instead of displaying the Alarm dialog, the alarms get almost immediately snoozed as if the preference for using the notification system was set).

New Features in this Release:

• Now supports the Share function in Android Contacts - so you can share a contact in the native Android contacts database with Pimlical's local contacts database.
  

Fixes/Changes in this Release:

• Fixes issue in contacts list whereby some attributes would not get refreshed immediately.
• Internal changes in English version to support upcoming German version.
• Avoids setting alarms at intervals other than one minute which could potentially result in an alarm being snoozed and then triggering again almost immediately.
• Addresses an obscure timing issue whereby an automatic database refresh on systems running OS 4.x or later might get missed because a database update occurred within the refresh interval of the last automatic database update. Note: The Android OS doesn't appear to broadcast the notification that the Android calendar database has been updated with 100% reliability, so this mechanism may fail to update on occasion anyway.
• Fixes new problem first appearing in 3.1.07 with feature of closing Date Picker when invoked from Month View - problem is that if you edit an event in the month view and try to change the month, it closes before a day can be selected.
  

New Features in this Release:

Fixes/Changes in this Release:

• Fixes a new problem in 3.1.12 where an AllDay event in an Android calendar was getting extended by one day.

New Features in this Release:

Fixes/Changes in this Release:

• Fixes problem of using the [+] button in the Template Dialog (to create a new template) that could overwrite an existing template under some conditions.

New Features in this Release:

Fixes/Changes in this Release:

• (Internal issue: Now uses custom, temporary filenames to avoid any possibility of a clash with the operation of the Pimlical Widget).

New Features in this Release:

• Adds new preference: BlankPrimaryKeySortsFirst which determines whether contacts that have a blank primary key sort before (True) or after (False) contacts that have an explicit primary key. For example, if you are sorting contacts by last name and the preference is true, then all the contacts with no name will sort ahead of the first contact that has an explicit  name, otherwise, if false, they would sort after the last contact that has an explicit name.
  

Fixes/Changes in this Release:

• When sorting contacts, Pimlical now uses the concatenation of the first/middle/last and company names (in the appropriate order) and only deals with a blank key when all those items are blank (with the first/last name sorts only using the company name if the first/middle/last names are blank and the preference SortByCompanyNameIfNameBlank is true. This more closely matches the way in which the native Android contacts app sorts contacts.
• A click on the Contact Icon displayed in the View dialog now invokes the Edit Dialog (same as if the Edit button was clicked) since a click on the contact icon in the selection list brings up the Edit dialog.
  
• Fixes issue on iCalendar file import whereby the CATEGORIES: tag was looking for a semicolon as the separator on multiple category names rather than a comma - this release now looks for a comma, but also supports a semicolon as some other calendar apps use the wrong delimiter (which is why a semicolon was used in Pimlical).
• Fixes issue of not displaying all the days of a spanned, repeat event, when the first day of the repeat instance is not included in the current view.
• Fixes the new Android OS 5.0 bug of not properly handling PorterDuff Color Filters which caused buttons to display with a pink background.
• Fixes an obscure issue in reading Android calendars whereby a CursorWindowAllocationException error could occur, which would then prevent proper reading of the Android databases.
• Fixes issue of user setting a start date/time for a repeat filter to after the end/date time for the filter (or an end/date time earlier than the start date/time). Also now sets the repeat end date to always match the date in the End Date button (so they always match - previously, they could be set independently which was confusing).
  

New Features and Fixes in V-3.1.08/09 - interim testing

New Features and Fixes in V-3.1.07

New Features in this Release:

• If you put the Filters function on the Command Bar, Pimlical will now display a red background on the command bar button if any filter other than the Default filter is filtering the current view - this makes it easier to realize that some other filter is currently in effect.
• If the Date Picker is invoked from the month or multi-month views, the Date picker will now close when a month is tapped (since there is no point in being forced to also pick a day to close the dialog in these two cases).
  

Fixes/Changes in this Release:

• To make it easier to test repeat filters, Pimlical now 'forgets' that an automatically-invoked filter was over-ridden or had previously run on today's date only when the green SAVE button is tapped in the Filter Edit Dialog (previously, the latch was reset on exit from the filter dialog, but this interfered with the feature of only allowing an automatically invoked filter to be invoked one time during each repeat instance, and the filter would not run anyway if it had run on the current day already). If an automatically-invoked filter is running and you manually switch to a different filter, the automatically-invoked filter will not be invoked again until the next repeat instance occurs. This avoids having Pimlical override the user's manual selection of some other filter when an automatically invoked filter is in effect (yes, this is definitely a feature for power users only!).
• Fixes a problem on repeat filters, whereby the end time for the filter was not being properly used to determine if the filter should run or not.
  
• Internal change for setting development environment for testing purposes only.
• Sidesteps bug in development environment that was interfering with usage by German users.
• Includes an alternate method of handling the coloring of buttons for Android OS 5.0 testing, since Android 5.0 broke the handling of PorterDuff Color Filters.
  

New Features and Fixes in V-3.1.06 - interim release

New Features and Fixes in V-3.1.05

New Features in this Release:

Fixes/Changes in this Release:

• Fixes issue of Menu | Restore Contacts (DAT) in the Contacts view not finding all the automatically created backup files.  Also now sorts the list in reverse chronological order, and includes the time (YYYY_MM_DD_HH_MM) so that backups on the same day are in chronological order.
• Ensures that on the Restore function, iCalendar files and vCard files are excluded (since they are text files that have to be imported).
• If the local calendar does not exist and the IMPORT button is used in Menu | Select Calendars, the program will now query the user if they want to create the local calendar and import the file (previously, the program just complained that there was no local calendar present).
• Fixes a problem on iCalendar import (in Menu | Select Calendars) where it was complaining about a missing iCalendar Tag when a blank line was found (possible if there was a blank, trailing line on the description field for example).
• On iCalendarImport, when corruption/invalid format/missing iCalendar tag is found, the program now continues reading the file in an attempt to recover as much information as possible (previously the program would not attempt to recover).
• The Export function in P/A now matches the export function in P/D and in particular matches how Google and some other calendars manage the DTEND statement with untimed events: untimed events specify the day after  the event actually ends (i.e. it ends on 11:59:59.999.... the night before). The iCalendar standard is vague on this point, but for consistency with Google Calendar and with Pimlical (that was already making that adjustment on import) it must be handled this way. This also ensures that iCalendar files exported from Pimlical/Android can be read directly into Google calendar without issues on untimed/allday events.
• Includes protection against allday/untimed events created on other calendar systems where the end date is not set to one day later (the end dates will be short by one, but at least it won't cause a problem in Pimlical when reading the file).
• Fixes problem in iCalendar Export with not properly formatting the description field in the vAlarm group (could cause a benign import error when items were re-imported).
  

New Features and Fixes in V-3.1.04 - Official Release

New Features in this Release:

Fixes/Changes in this Release:

• Fixes issue in filters that were setting two of the three values for the Due Date for Floating Events or Tasks (only one of the values was getting set).
• Fixes yet another issue in setting the start/end times on a repeat specification for a filter.
  

New Features and Fixes in V-3.1.03 - Final Release Candidate

New Features in this Release:

• The Restore button in Menu | Select Local Calendar command now includes manually backed up files as well as the automatically backed up files and they are now sorted in reverse chronlogical order (most recent first).

Fixes/Changes in this Release:

• Fixes another issue in the display of anniversary/birthday when target event is in following year, and age is set from the Action Tag.
• Fixes an issue with not being able to set the end time for a repeat specification on a filter. Also prevents invalid setting of an end date prior to the start date of the repeat specification for a filter.
  

New Features and Fixes in V-3.1.02 - Release Candidate

New Features in this Release:

Fixes/Changes in this Release:

• Fixes an issue with advance reminders of a birthday/anniversary in a future year displaying a matching age/anniversary in the Event Selection List, and also caters to the birth year being set either in the target event itself, or in the Action Tag.
• Fixes an issue of the advancing of floating events getting triggered if launched immediately after a refresh of the widget.
• Fixes several issues in handling repeat start/end date/times for repeat filters. Also clears the recollection of an automatically-invoked filter being manually overridden when exiting the Filter dialog - this makes it possible to test out the automatic invocation of filters more easily (a filter is only invoked automatically one time, as otherwise, you could never manually switch to another filter while a filter with a repeat specification was in effect).
  

New Features and Fixes in V-3.1.01

New Features in this Release:

Fixes/Changes in this Release:

• If an advance reminder is created for a birthday or anniversary event in a future year from the reminder, the age/anniversary is now calculated from the target event (i.e. if the person would be 50 in 2015, and the advance reminder was created in 2014, it will now display [50] as the birthday/anniversary - previously it would display [49]).
• If a WiFi connection is not available and Menu | DirectSync is invoked, an appropriate error message appears (previously, there was no indication as to what the problem was).
• Fixes an obscure issue with the preference: PutAdvanceInDifferentCategory failing under some conditions to update the calendar DatabaseID when the original item was in an Android calendar and the preference was set to a different Android calendar which would subsequently result in the item not being moved properly into the designated calendar.
  
• Version number was upped to 3.x to reflect match with Pimlical/Desktop major version.