This section below is for Users who want to know every single issue and fix that have been applied in all prior interim releases, as well as all the new features that have been added.

• In the RemoteServerList preference, the host address can now be specified along with a port number. By default, Pimlical connects via port 21, but you can change that by appending a colon and the port number to the host address (So use say www.pimlicosoftware.com:22 instead of just www.pimlicosoftware.com to attempt to connect using Port 22. This may or may not work depending on FTP host software etc. and most users will not need to specify a port number as the default will work fine). 
• The warning for creating an event in the past (which is a preference item) is now suppressed if the event has a status other than Normal.
• If the popup command Set Snooze Alarm is used on an event selection list invoked by the Menu | View Upcoming [Alarms] function, the alarm list is now immediately refreshed to show the new status of all upcoming alarms (previously, the list would have to be manually refreshed, to see the new snoozed alarm).
  
  

• Includes better diagnostics for corrupt/truncated files submitted for iCalendar Import (previously, a truncated file could under some conditions cause P/D to hang without identifying the corruption.
• Addresses some compatibility issues between UniqueID's generated from Pimlical vs. those generated from other calendar applications when importing or exporting iCalendar Files.
• Pimlical no longer automatically resets the direction to forwards for the Advance Repeat Specification when the button to setup the number of days offset is tapped.
• Pimlical no longer logs all the backups performed to the AuditTrail log file (it was cluttering it up with information that was not really useful), and skips the old/new value lines if both of them are blank.
• Now includes a test that the user is not attempting to rename the Default Filter (previously, there was only a test for attempting to rename or create a new filter with the name Default).
• Fixes an issue with the automatic removal of deleted records (in the routine that advances floating events) that exceed the threshold set by the preference: DaysToKeepDeletedRecords - previously it was only testing that the event had not been modified in that last number of days, whilst the original intent (now restored), was to use (as the latest date), the later of (a) the Modification Date, (b) the End Event Date, or (c) the Due date (of a floating event). 
• Includes a test now that the user is not creating illegal category names such as All or (All) which could result in confusion over their usage.
• Addresses an obscure issue with alarms - under some conditions, it looked like Pimlical might be displaying the Missed Alarms message box when an expired alarm was accessed through the Android Notification Bar, instead of displaying the Alarm Dialog.
  

• Adds new button in Menu | Debug | Clean Relaunch which performs the equivalent of force-stopping Pimlical from the Android OS and then relaunching Pimlical.
  
  

• When P/A is forced to relaunch due to the Android OS leaving Pimlical in a non-recoverable condition (usually after low memory conditions), P/A now forces a very clean relaunch of the App as there were some conditions under which AOS was forcing P/A into a loop, or leaving P/A with no option but to display an odd Template for the Event Selection List.
• Fixes an Uncaught Exception Error due to handling an event with corrupt start/end dates (which were not previously detected properly)
• Now properly detects events with corrupt start/end dates and ensures they are valid (if the end date precedes the start date, it will then be set to the start date).
• Avoids logging errors with corrupt events in Android calendars as there are just so many due to sloppy programming, that there's no point - only corrupt events in the Local Calendar are logged (and fixed).
  
• No longer permits DirectSync or AutoSync to be invoked during a telephone call (which can apparently lead to some conflict issues).
• No longer displays a redundant Done button when handling irregular repeats (as there is now a green check mark to close that dialog).
• Removes the [Delete] button in the Irregular Repeat Dialog if no irregular repeats have been set.
• Avoids a very obscure (and benign) exception error in the floating advance if it occurs when memory has been absconded with, EnabledebugLog is set to true, and it was also time to include all the "required info" in the log file.
• When entering longitude and latitude from Google Maps into the location field, if there was no comma between them, P/A was displaying a Phone Icon (thinking it was a phone number) rather than the Map Icon - Pimlical now automatically assumes a Map coordinate if the ° character is seen.
  

• In some circumstances, such as when removing a repeat specification from an event, the repeat status was left in a temporary state which could result in the event appearing to still have a repeat when in fact it had been removed.
• Fixes a new issue from V-4.4.15, whereby after rebooting the phone, there were some conditions under which the next alarm was not getting set with the OS (resulting in no further alarms sounding until Pimlical was manually launched).
• When updating the AuditTrail file (Pref: MaintainAuditTrail set to True), after an event was edited, the description field is now included (previously, it could be difficult to tell what event was being updated if the description remained the same).
  

• When the Android OS issues a callback to the AlarmReceiver, V-4.4.14 was displaying a message box with a message to that effect, but only if the callback WAS on a minute boundary (All P/A alarms are set on minute boundaries, which makes it simple for P/A to realize if the AOS callback was spurious or not). However, on a spurious callback, the screen was left blank. This release should now exit P/A under these conditions (screen will likely still light up on a spurious callback though - no way to avoid that).
• The Remove button to the right of the Font button in the Edit Dialog (when a custom Font has been set) has now been replaced with a red [X] button for consistency with the alarm and repeat lines.
  

• Fixes issue in prior release where the test for creating an event in the past was issuing a spurious warning on untimed events created on today.
• When using a Master Template with Call/Action Tags, Pimlical now supports the substitution of Call/Action Tags in any of that template's Subordinate Templates, using the same selected Contact. This is only supported for the local Contacts Database (not the Android Contacts Database).
  
  

• Fixes an obscure issue in the Alarm Handling Routines which could potentially cause a lost alarm under some unusual circumstances (related to the setting in the NextAlarmClock.txt file).
• Fixes an obscure issue in the Alarm handling routines which can potentially cause a lost alarm when reading a lot of events from an Android calendar in the 2am floating advance, after AOS has absconded with all of P/A's memory.
• When the preference AlwaysShowNewDay is set to True (default is False) and one of the the popup commands to change the date is used (Advance 1 Day, Advance 1 week, etc.), Pimlical only honors the preference in single select mode (it was invoked previously in Multi-Select mode), and in single select mode, it is only honored when the Event Selection list for a single day is being displayed (previously, it would switch the display on lists like the Upcoming Alarms List, Find List, etc. which would make little sense).
  

• A long press on the File Manager Menu item is supposed to generate a list of all Remote Servers with Local at the end, but previously, the last Remote Server in the list was being replaced by Local.
• Corrects issue with the optional warning about creating an event in the past that was complaining when inserting an event from a template using the Action Tag: ScheduleIn:0 (because events are inserted at minute boundaries -- so it might appear in the past by a few seconds).
• Removes the Menu | Debug | Create Calendar command as it is superfluous: a long press on Menu | Select Local Calendar + already provides that same capability (and with more error checking - for a duplicate/invalid name, etc.).
  
  

• Ensures that events moved from an Android calendar to the local calendar always have the temporaryUID field cleared (potential problem issue with AutoSync).
• When Android OS issues a spurious Alarm Callback to Pimlical, Pimlical now only displays the Alarms Missed? dialog if the alarm callback occurred at least a full second later than any alarm that P/A would set (as P/A only sets alarms on one-minute boundaries). Previously, the dialog was always logged in Debug Mode.
• Ensures the Targeted date is cleared after use (this is used when switching views to ensure the date that a user was looking at is displayed in the new view). Previously, this might have caused Pimlical to appear to have gotten "stuck" on a particular date when invoking different filters.
• (Note: this release has been compiled with latest version of Android Studio).
  

• Test Compilation with newer versions of Android Studio.
  

• When tapping on the Irregular Repeat Parent icon in an event selection list, Pimlical now displays a list of all the instances of the irregular repeat series, starting with the Repeat Parent. As with a regular repeat, tapping on a date goes directly to that day.
• When tapping on an instance of either a regular or an irregular repeat series, there is now a button Goto Parent Day that goes to the Day on which the parent event occurs in the Day View (or the first displayable occurrence of the repeat if a repeat series, catering to exceptions and a possible Advanced Repeat Specification).
  
  

• Ensures correct end of line icons are drawn for the four possible repeat types: Regular Repeat, Exception to Regular Repeat, Irregular Repeat Parent, and Irregular Repeat Child. Also fixes issue of long-pressing one of those types listing all the dates in the calendar.
• Fixes a relatively new and significant issue in AutoSync when synchronizing records - under more than one condition, the wrong events could be matched up.
  

• Ensures that a repeat event properly repeats on the last year of the calendar (2099) including up to the last day of the calendar (December 31, 2099) - previously, the very last repeat occurrence in 2099 was not being displayed.
• The repeat attribute to only show the next occurrence of the repeat is now ignored if hidden items are currently being displayed in the calendar. Previously, Pimlical would show there was something hidden on that day, but, puzzingly, there was no way to force Pimlical to display the item.
• Pimlical now properly preserves the repeat of an item repeating on the Last (as opposed to 4th) day of the month (Monthly/Yearly Repeat by Day) - previously when edited, the repeat could, under some conditions, unexpectedly revert to the 4th day of the month.
  

• The AutoSync feature to copy preference files using the AutoSyncName preference as a prefix was not working properly when syncing to a Remote Server (prefix was dropped from the filename).
• When handling the Debug command to remove duplicate records, if the preference MaintainAuditTrail is set to True, Pimlical also writes out a comprehensive list of every duplicate record into a file with the name ListOfDuplicateRecords.txt in the Pimlical Folder.
  
  

• Ensures that after editing a template or filter name, the master template and filters lists are immediately rebuilt and also written out into the SystemPreferences.dat file. This fixes a puzzling issue when using a template or filter name in the preferences TemplateNamesForCommandBar or FilternamesForCommandBar and then changing the filter name or template description and then trying to update those preferences with the new name/description. With this update, both the old and new name/description will still be displayed in the list, but the old name/description will disappear after it's unselected (and the updated name/description selected and moved into place).
• Displays an error message if the preference FilternamesForCommandBar references a filter name that no longer exists (previously, it created an Error file) - this is now consistent with how a missing name in TemplatenamesForCommandBar is handled).
• Avoids generating a spurious error file under some obscure conditions when renaming a filter.
  

• When creating a new memo, a default title of MEMO_YYYYMMDDTHHMMSS is created (as currently specified in the documentation, where YYYYMM... is the current date and time). This makes it quicker to just enter some text for a memo without having to fiddle around with specifying a title. Also when exporting memos, if a memo is found without a title, this same string is used for the exported filename.
• Documentation for memos and contacts has been updated to reflect recent changes in P/A in those sections - in particular for long-press on Recents and Find buttons. Also a brief tap on the Recents or Favorites buttons in memos and contacts, when already selected, now just removes that filter without resetting any other filters in effect.
• Removes redundant "Toast" message about advancing floating events when launching Pimlical.
  

• When deleting a master event, Pimlical now scans the entire database for any Subordinate Events that link to that Master event and will remove the link of that subordinate event (so it no longer displays [S])
• Fixes an error in AutoSync when using CloudRail Server and the preference SyncCustomPimlicalFolders is either blank or has the default string of PimlicalImages,PimlicalIcons,PimlicalLinks and one or more of those folders exists.
• Changes the function of the Preference: SyncCustomPimlicalFolders, so that if it is left blank, it no longer defaults to the default string of PimlicalImages,PimlicalIcons,PimlicalLinks as there should be a simple way to avoid syncing those custom folders even if they are present (without having to edit the AutoSyncOptions or DirectSyncOptions preferences).
• Fixes an UncaughtException error in the selection of some dates in the Pinned Date List.
• Menu | Debug function Last Toast Msg now remembers all previous toast messages (newest at top), date/time stamps each message and will purge older toasts if/when it exceeds some 10k characters.
  
  

• The Go To Display/Due Date popup command now applies a timezone adjustment before selecting the referenced date. If the event would be shifted to a different day based upon adjusting the timezone to the current timezone, previously, it would have ended up on the "wrong" day for actually displaying the event.
  

• The Pinned Dates feature has now been improved to include a list of all pinned dates that are also saved in the System Preference File (which now matches the behavior in P/D). A long-press on the right-arrow command button now displays a popup list of pinned dates (if more than one date has been saved), so you can select a date (tapping OK), or delete it (Tap Delete+) or delete all Pinned Dates (Long press on the Delete+ button). For backwards compatibility and non-subscribers, Pimlical also remembers the last tap on a day in the Pimlical Date picker and will display that at the top of the list with the legend (last) (unless the pinned date list is empty in which case Pimlical will go to that last tapped date. The pinned date list is displayed in reverse chronological order.
• Enhances the dialog that appears when a repeat icon is tapped in an event Selection list. It will now list all the dates on which a repeat event will repeat, along with the details about the repeat itself. This can be useful in verifying that an event with an Advanced Repeat Specification repeats on the expected days. A tap on a date in the list goes directly to that date in a main view.
  
• Adds new preference: WarnIfCreatingEventInPast which defaults to true. If you create a new event and the end date/time (if necessary, adjusted to the current timezone) is earlier than the current date/time, a brief warning message appears when you tap the OK button in the Edit Dialog. This is helpful in avoiding inadvertently slotting an event for 9am instead of 9pm, or creating an event on a past day instead of for today or a future date. Set to false to disable this feature. No warning is made upon editing a past event.
• Adds a feature to the Debug menu (Last Toast Msg) that really should be in the Android OS - namely the ability to recall the last "Toast" message that was displayed ("Toasts" are the brief messages that flash on the screen and then disappear). Also useful if the Toast Message gets truncated for display.
  
  

• Fixes an obscure alarm issue that could cause a missed alarm if the Android OS was (for some bizarre reason) issuing an onPrepareDialog() callback whilst Pimlical was in the middle of processing an alarm.
• Fixed an alarm issue in P/A (appeared recently) which appears to be associated with the display of a Message indicating that some alarm had been missed.
  
• When a subscription is not present and several features requiring a subscription are being used (such as special command bar buttons), only one Message Box appears and toasts are used instead unless more than 30s have passed (this avoids significant annoyance when a subscription lapses, or a ReferenceID unexpectedly changes, etc.).
• Fixes very obscure issue that the Event Selection List after being refreshed would unexpectedly not display the date of each item (such as on Find, Alarm list, etc.).
  

• Updates the advanced repeat specification with a significant enhancement. All repeat types except the Weekly repeat can now include a final offset to the calculated repeat date. For the Daily (with frequency > 7 to avoid bizarre end conditions that can otherwise occur), Monthly repeat by Date and Yearly repeat by Date, you can offset the final date forwards or backwards to select the first occurrence of a day (or selection of days) of the week on or Before/After the final calculated day. For the Monthly repeat by Day and Yearly repeat by Day types, you can offset the calculated repeat date forward or backwards by some number of days. This is far more powerful (and intuitive) than the current, limited Advanced Repeat Specification. Example: for the US Presidential Election day (usually, the first Tuesday that follows the first Monday in November), you would use a yearly repeat every four years on the First Monday in November and then use a Forwards offset of 1 day (to get to the following Tuesday). This resolves the issue of Election day being on November 8th, when the first Tuesday is November 1st (and why the first Tuesday in November wouldn't work). Your bank deposits your paycheck on the fifteenth of the month, but will deposit it on the prior Friday if the fifteenth is a Saturday or Sunday. So you set up a monthly repeat by Date on the 15th of the month, and then specify a Backwards offset to pick the first day of the week on or after the set: Monday/Tuesday/Wednesday/Thursday/Friday. So if the 15th falls on a Saturday or Sunday, it will move to the prior Friday, but if it falls on any other day, it will remain on that day. Or you have a party regularly set for the whole weekend before Canada's Civic Holiday - so you set up a Yearly Repeat on the First Monday in August, and then use a backwards offset of 2 days to get the event to appear on the Saturday before (even if the first of August is a Monday, and so the event ends upstarting on July 30th). The action Tag AdvancedRepeatOnlyInSameMonth can be optionally used to skip instances that were shifted into a different month. Note: Android/Google Calendar only handles the simplest case of these repeats, namely a day of the month (either monthly or yearly) with an offset to the first occurrence of one or more days in the week, which can handle the "CyberMonday" type cases. You cannot edit that in google, but that specific instance will at least display properly. None of the other advanced repeats will display properly in Google (and most likely not in anyother calendar app either), but a tag is written into the note field, so these events CAN round-trip through google unscathed and still display properly in Pimlical.
• When a Backup Everything is triggered (especially overnight at the end of the floating advance) and (a) a remote server is being used and (b) the Android device is charging, and (c) quite a lot of files were being backed up, the Android OS could shut off WiFi in the middle of the backup causing it to fail. This version now acquires a WiFi lock to prevent this from happening under those conditions. In some cases though, AOS may postpone the conlusion of the operation if the phone is in deep sleep mode.
  
• A long press on the Today+ button (in the Pimlical Date Picker) now pops up a dialog where you can enter a number of days to move forwards/backwards from Today (in red), or the currently selected day (in blue). Use a negative number to move backwards.
• The popup command Compare Calendar Events now additionally displays the number of days apart two events are (not necessarily events that you want to "compare" per se).
• The default setting for the preference PurgeUnusedLinksAndImages is now False (previously was True). The reason for this is that if invoked when there are different selections of calendars/categories, it can result in the unexpected purging of some links and images, so it's safer to set the default for this to False.
  
  

• Provides better navigation for selecting the year in the Pimlical Date Picker by using a custom selection list rather than an Android Spinner widget: decades are marked as well as the current year, and the selected year appears part way down in the dialog, so prior years can be easily selected. Also a long-press on the button displaying the selected year immediately sets the current year (which is why there is a + after the year in the button legend). When the current year is selected, the button is displayed with bold type.
• Changes the style of the dropdown lists again for the font/style/size selection to still display more information whilst maintaining better vertical separation, and use of radio button to show selected item.
• Fixes an issue in alarm handling when the preference AlwaysShowNotificationForAlarm is set to True: under some conditions, the initial alarm might not sound properly.
• Ensures that for events in the local calendar, the internal TemporaryUID field never gets used. This could get set under unusual circumstances (switching an event from Android to local calendar or using the preference: SyncAndroidCalendarsForDesktop) and would not get cleared out, leading to potential sync errors in AutoSync.
• The GoTo popup command now finds the first occurrence of a repeat event in the calendar - this ensures that a repeat event that uses an Advanced Repeat Specification, or where the first occurrence was excepted, is always displayable (previously, it might go to a date on which the event would not display anyway).
• Log file (PimlicalDebugInfo.log) now provides separate counts for events in each Android calendar as well as total, and also includes information on skipped and deleted records. fs
  
• The attempt at recovering a lost alarm (due to bug in AOS where it bizzarly goes to sleep instead of launching P/A) was flawed in prior releases - this release includes a new strategy to try and get the alarm to display (it'll still be late of course - P/A can't do anything about that, but at least later is better than never!).
• Avoids spurious complaint about no more repeat instances when scrolling through an event selection list and the preference ShowInstanceDates is set to True, and a repeat event is found with a repeat end date prior to today.
• When changing the preference DisplayWeekNumbers, Pimlical now immediately refreshes the Pimlical Date Dialog to include/hide the display of week numbers (previously, Pimlical only changed it on a fresh launch of the App). Also, the Pimlical Date Picker now includes both OK (Green check) and Cancel (Red X) (previously, the only way to close the dialog was to tap the desired date, which if already selected, was not that intuitive).
• Pimlical no longer attempts to wordwrap the final line of the description field in views that support the display of multiple lines (Day, Day+, List) and truncates it instead. In general, it's better to display as much of the description as possible on that last line in tight situations.
• When inserting a subordinate template, and the item is a Floating event or Task, Pimlical now correctly adjusts the due date so the new due date is the same number of days after (or before) the new start date for the subordinate event. Previously, it was not adjusted (or adjusted by the wrong parameter).
  

• In Menu | About, removes Widget Refresh date (date has been displayed by the Widget for some time).
• When moving items from Android calendars into the PimlicalAndroidArchiveCalendar (the preference ArchiveAndroidCalendar was set to True), Pimlical now ensures that the event is not marked as deleted (unlikely, but could confuse the user if that were the case).
• Pimlical now allows the end user to add new TrueType fonts for displaying events. To add a new TrueType Font (other font types may be an issue), just copy the TTF file into the ...Pimlical/PimlicalFonts folder, and the fonts will be immediately available for use. In Windows, for example, you can just copy TrueType fonts from the C:\Windows\Fonts folder into ...Pimlical/PimlicalFonts to use them (they must also be installed in Windows for all users, however). Remember that using custom fonts will be an issue for other platforms that you sync to (so you will likely want to include PimlicalFonts in the list of folders that is also synced to other platforms - preference: SyncCustomPimlicalFolders).
• Adds a new line to the Find Dialog to cover searching for a specific font (so you can find all events using a specific font).
• A long press on one of the font size radio buttons (LE/EQ/GE) in the Find Dialog now clears the selection without affecting anything else.
  
• Now applies the same recovery logic when the Remote Server operation ftp.storeFile fails due to an I/O Exception error that it applies when the Remote Server is unexpectedly disconnected (neither of these error conditions are caused by Pimlical - these are just random types of errors that can occur due to network problems, or bugs in the FTP Client Server software). 
• Passwords for the Remote Server can now include the question mark character. Note that the Vertical Bar ( | ) and comma characters are not permitted in password strings for the Remote Server. It is very unlikely, but still barely possible that some users might find that they have to re-enter their passwords for the RemoteServerList preference.
• Forces the File Manager dialog to be the full width of the screen.
• Displays the size of memos in the Memo list.
  
  

• In Menu | About, adds the build date of the APK file.
• No longer permits Beta Preview access/status in Release builds of APK file.
• Changes the style of the dropdown lists for the font/style/size selection to display more information (previously, the full font name was sometimes truncated, making it difficult to easily distinguish say Arial Narrow from Arial Narrow Bold.
• Cleans up layout of the Find Dialog (alignment and spacing issues).
• Duration value preferences no longer sometimes lose the seconds value.
• When entering a new contact, if the first/middle/last/company name fields are all blank and the user taps the OK button, an informative toast message appears and the contact edit screen is left open (at least one of those fields must be non-blank). Previously, the Contacts Edit Dialog was closing without writing a new contact record, causing the loss of whatever had been typed in to other fields.
• Corrects a relatively new issue when attempting to create a second new contact immediately after creating a contact - the [+] button was unresponsive.
• Now advises user they may need to set the system permission to install Unknown Apps for Pimlical to avoid being queried each time on upgrading.
• Avoids possibly generating a spurious Error Message on initial install dialog regarding SystemPreferences.dat (error was benign, but should not have appeared anyway). This also avoids a potential reason why the dialog to copy files on an initial install might not appear.
• Includes warning for memos that exceed 512k characters as there can be issued on some platforms if that limit is exceeded.
  

• Ensures that when archiving android calendars (ArchiveAndroidCalendar set to True) that the preference file is rewritten as under some conditions, it was losing the reset of the current local calendar and leaving it set back at PimlicalAndroidArchiveCalendar, although with the current contents of the local calendar.
  
  

• Avoids generating spurious Wait until database read message when tapping an event to bring up an event selection list under unusual conditions when pimlical instead needs to rebuild a working environment.
• Fixes a new issue in V-4.4.03 whereby the Recent Icons List was no longer being properly displayed.
  

• Long press on right-arrow button in the Icon Selection Dialog will now go the first page of icons if the current page is not the first page, otherwise, it will go the last page of icons (so it would then toggle back and forth between the first and last page of icons).
• Avoids generating an error file when Widget is invoked, but subscription has lapsed.
  
  

• The left and right arrow command bar buttons and buttons in the Event Selection List and Icon Dialog now display a + character as part of the arrow to signify that a long-press has an alternate function.
• Includes extensive code to combat a class of bugs/design flaws in the Android OS that were causing Exception Errors in Pimlical. Instead, the error condition is logged to the PimlicalDebugInfo.log file and Pimlical is relaunched.
• Avoids generating an error file when the Advanced Time Dialog is left on the screen for a very long time and other Apps are run (so Android OS has absconded with all of P/A's memory) and the user returns to that dialog and taps a button.
  

• When a repeat type is selected, there is now also a red [X] button to the right of the dropdown list which sets a repeat type of None and exits the repeat dialog (previously took two extra taps to do this).
  
  

• Fixes cosmetic issue of not removing the empty Event Selection List when a prior operation leaves it completely empty.
• Fixes typos in AutoSync differing versions message and includes note that this may happen on the first sync after upgrading.
• If you create a new appointment without presetting the time (i.e. you did not preset the time by tapping on a time slot, or are creating it in a view other than Day/Day+ where the time cannot be preset), and you then change the event from untimed to timed in the Edit Dialog, if there is an alarm preset, it will be applied right after setting the time. Previously, the alarm preset would not get applied because Pimlical created the event originally as an untimed event and by default alarm presets are not applied to untimed events. The new workaround to apply alarms to untimed events (See documentation on alarms) would also have circumvented this issue since the workaround makes it possible to apply alarm presets to untimed events. If an alarm was already present on the event, changing the time from untimed to timed, will not result in the preset being applied. This action is also taken with the popup command Change Time when the time changes from untimed to timed.
• When applying an alarm to untimed event, Pimlical now displays the time that the alarm will actually trigger (based upon the user's setting for the preference: UntimedAlarmTime). Previously, this information was not displayed.
• When changing an event from timed to untimed (either in the Edit dialog or with the popup Change Time command), any alarms that were set on the event are now removed. This avoids the issue of having a previous alarm on a timed event going off at an unexpected time (since the time for the alarm to go off would change from the prior event's start time to the value of the preference: UntimedAlarmTime.
• Improves the usability of the Repeat Dialog by eliminating a tap to setup repeats. When invoking the Repeat dialog and no repeat is set, there are separate buttons for every possible repeat type (so you don't have to tap the dropdown list and then tap again to select a repeat type).
• The panel for handling Exceptions to Repeat Series is now properly hidden for tasks unless the preference: RepeatTasksHaveNoExceptionsList is set to False (default is True).
• In the Repeat Dialog, now properly displays options for Fourth and/or Last week of month for the monthly-by-day and yearly-by-day repeats even though no repeat has been selected yet (previously, you had to first set a monthly-by-day or yearly-by-day repeat type to see those options displayed). To recap: if the event's day of the week is in the fifth week of the month, only the option to schedule on the LAST week of the month is offered, if the event's week is on the fourth week of a month that has a fifth week for that day of the week, then only the FOURTH week of the month is offered, and if the event's week is on the fourth week of a month that has no fifth week, then both options for LAST and FOURTH week are offered.
  

• If the preference AlwaysShowNewDay is set to True (default is false), Pimlical has always displayed the new day in an event Selection List (or view) so the user can confirm the movement. New in this release: a long-press on the left Arrow button in the Event Selection List always returns to Today's date, whilst a long-press on the Right Arrow button will return to whatever date was in effect prior to showing the new Day (in the current session - this is not permanently remembered!). This makes it feasible to quickly move several items on one day to other days without having to manually navigate back to where you were after confirming each move.
  
  

• Corrects issue that if the preference ShortTimesInDayView is set to True (default is false), AND DayStartMinute is set to an hour boundary, SlotInterval is set to an integral number of hours, and TwelveHourClock set to false, the time field was still showing the minutes (it should only be displaying the hours) and as a result overflowed the available space in the time column.
• When deleting an event, if the event has an Advance Reminder (meaning a floating event was created that targets that event and "down-counts" towards its start date), the advance reminder was also always being deleted. With this release, the advance reminder is only deleted if the status was NORMAL. If it has any other status (such as Completed, etc.) the advance reminder is retained (on the grounds that the user must have had a reason to change the status and it likely needs to be retained).
• Avoids generating error files in a couple of cases for what is not really an error condition, and instead logs the information into the PimlicalDebugInfo.log file.
  

• Fixes issue that after a backup everything was launched at the end of the Float Advance Time, tapping on the screen would sometimes be unresponsive.
  
  

• Fixes bug in the new feature (V-4.3.34) to remove dates from a repeat exceptions list that precede the Start Date or fall after the repeat end date of a repeat series (under some conditions, this could cause an exception error).Also moved this test to a point where the record is being saved (previously, intermediate date changes could result in some exceptions being unexpectedly purged -- i.e. inadvertently setting the start date to today while in the Edit Dialog, and then setting it back again to its original start date).
• Fixes a small cosmetic issue in the dialog that handles color selection for calendars and categories - if UseGoogleCalendarColors was set to false, the background color panel did not always match the layout of the foreground color panel, (issue was only really noticeable on tablets or in landscape mode).
  

• If an event has an alarm, a new Cancel button (Red X) appears on the right side of the first Alarm Line in the Edit Dialog. When tapped this button removes all alarms set on the event.
• A new preference has been added: ArchiveAndroidCalendars. If set to True (default is false), all selected Android Calendars at the time of performing a Backup Everything operation are archived into a local calendar with the name PimlicalAndroidArchiveCalendar. If an event is already present in the calendar, it is replaced by the potentially updated event (based on the modification date). These calendars are backed up on each archive action. You may find it preferable to use this preference instead of the current BackupAndroidCalendars preference which backs up each Android calendar separately and always overwrites (as opposed to this preference which always preserves entries no longer present in the Android calendars). Since Google does not sync older events to the native Android Calendar database, this will preserve those dropped entries where they can still be found on a search with the Find+ menu command (which searches all local calendars).
  
• The popup command Change Time can now set an event to be untimed (by clicking on the None button in the Set Time dialog (previously, this button was ignored).
• A new Debug command has been added: Create Calendar which displays an alert dialog so you can enter a name for a new, empty local calendar (an alert dialog appears to enter the new name for the calendar). The new local calendar is then selected for display.
  
• Adjusts the logic used to purge /PimlicalLinks and /PimlicalImages of unused links and images to only take place if the default Local Calendar (PimlicalLocalCalendar) is selected AND now performs this at the beginning of a Backup Everything operation (invoked by the system or by the user). Why? Because if the user has temporarily selected some other local calendar, we don't want to inadvertently purge these items just because Backup Everything got called whilst that calendar was selected. Some users with active multiple local calendars may not want to have this function take place at all. In that case, set the new preference: PurgeUnusedLinksAndImages to false (default is true). If true, this could purge images used in some other local calendar but not in PimlicalLocalCalendar. Regardless, remember this only purges the images from PimlicalLinks or PimlicalImages, which are typically copies of the original files stored there for cross-platform operability.
• A long press on the File Manager menu item, followed by selection of the Local Filing System or Remote Server(s) now always displays Done | MultiSelect+. Previously, on occasion, the MultiSelect+ feature was not available.
• In the Template Dialog, a long press on a Master Template correctly displayed the option View Subordinate Templates, but was incorrectly handling it as if it were the 3rd popup command on normal Templates (Link to Master Template).
• Adds a new preference: SetUntimedIfCanceled (default is false) which is similar in operation to the preference SetZeroDurationIfCanceled - in this case, if SetUntimedIfCanceled is set to true, then on marking the event as Canceled or Absent, the event becomes untimed and the original time of the event is placed in parentheses at the end of the description field. If toggled back to Normal Status, the time is removed from the end of the description field and used to reset the event's start time. The end time is then set based upon the default duration preference for Appts or floating events. This helps reduce clutter in the calendar. This action takes place if the change is made in an Event Selection List with a popup command or from the Edit Dialog.
  
• By moving the code from the nightly Floating Advance that performs the purge of /PimlicalLinks and /PimlicalImages and the handling of the AndroidArchiveCalendar to the BackupEverything routine (which runs in a sub-thread of the main UI Thread), Pimlical now avoids being unexpectedly force-terminated by AOS for taking too much time on the Float Receiver thread (this is yet another design flaw in AOS - if a broadcast receiver has only one recipient, AOS should permit that receiver thread to run until it terminates, it's only if there are two more Apps registered for a receiver that AOS needs to be concerned about an App taking too much time on that thread!).
  
  

• When changing the start date of a repeat series, Pimlical now removes any exception dates that are before the new start date for the series or after the end date of the series (if the repeat series had a repeat end date).
• Prevents an exception error occurring if a user edits a repeat series with the THIS AND FUTURE exception type and then removes the repeat specification in the Edit Dialog (obviously unclear why anyone would ever want to do that and which is why this issue has been in Pimlical for 15+ years but no one has ever reported it), but clearly P/A should not crash if a user attempts it, even if makes no sense to do that!
• Fixes issue of the options Only Show Next Occurrence and Reschedule from Checkoff Date not being available if a user lacks a subscription (it was intended to only suppress the display of the new feature to set a range of dates for creating exceptions to repeat events).
• Ensures that the argument to the Action Tag: ScheduleIn: removes the seconds value from the time (so the event is recorded on a minute event boundary, which is enforced by Pimlical so that alarms always trigger on a minute boundary).
• Floating Advance/Reminders now present a new icon - a float circle with the letter 'R' inside it (specifically a floating event that has a target event that it advances towards).
• Fixes an issue where the Template dialog might display a list where the list of templates was repeated (and if selected could cause an UncaughtException Error).
• The action of changing an event from Canceled/Absent status back to Normal Status when the preference SetZeroDurationIfCanceled is set to True now also takes place if this action is performed in the Edit Dialog (previously, it was only performed when the popup Toggle Cancellation command was used).
• Corrects issue in a recent update to AutoSync which could cause new records created on the desktop that were subsequently synced to P/A to be erroneously assigned a new uniqueID in P/A, which could then, on being autosynced back to P/D, result in a duplicate entry in P/D. This issue appeared as a side effect of a recent, major code update to support the new feature of syncing Android records in P/A as local records to P/D.
  

• Adds new popup command Search and Replace which can perform a search and replace operation (search is case sensitive) on either the description field or selected text fields (Description, Note, Location, GroupKey, and all 4 custom fields). The Popup command appears in both PopupListCommandsForEvent and PopupListCommandsForMultiSelect (so it can be used on a single event or multiple, selected events). There's also an Append button that just appends the entered text to the description field of all selected items. Any leading or trailing spaces on the search or replacement strings are not trimmed.
  
• A checkbox has been added to the dialog that handles the RGB color selection: Lock the RGB Sliders. When locked, a change to the numeric value of any RGB component (from a button tap) is applied to the other two components. If a slider is adjusted, the other two sliders are adjusted by the amount of the change. This makes it easier to adjust the saturation of a color without affecting the hue. When locked, the adjustment (by button or slider) is constrained so that no color value of < 0 or > 255 in any color is permitted.
• A brief tap on the foreground or background color swatch in the Color Dialog now brings up the RGB Color Selector Dialog directly (previously, a brief tap did nothing, and the only way to get to the RGB Color Selector Dialog was via the Color Swatch Selection Dialog, with a long-press on the foreground or background color swatch).
• The popup command Paste (which pastes items from an internal list created by using the popup command Copy Selected Item or Copy ALL Items in List) now displays a new event selection list of just those newly pasted items. This makes it possible after inserting the items to have them exclusively selected, so you can then make changes (such as moving to a new date, changing the category, font or color, etc.), or delete them if they were inadvertently pasted.
• Corrects the issue of the new feature to clean up the Pimlical/PimlicalLinks and Pimlical/PimlicalImages folders of unused links and images was not catering to paths created on a different type of platform and then synced to that platform (i.e. a link set on an event created in P/A being processed in P/D in Windows after syncing, or a link set on Windows being read on Linux, etc.). This also caters to the issue of different file path separators used on different platforms (i.e. forward slash in Android, backslash in Windows).
• Fixes issue of having a subscription and failing to properly change the default value for the preference BackColor1 from {255,255,255} which is "pure white" to {255,255,254} which is "near white" that won't get overridden as a default background. When changing the background color, this could inadvertently cause the foreground color to get lost if set to the pure white.
• The refinements in handling colors for events (tap and long press on color swatch to bring up swatch selection or RGB Color Selection), locking of RGB colors, etc. are now all available when setting Calendar Colors.
• 
  
  

• Fixes an issue in the Color Selection Dialog whereby selecting Pure White {255,255,255} as a foreground color or Pure Black {0,0,0} as a background color could get changed to the default foreground or background color.
• Corrects issue in the popup command Copy ALL Items in List which was reporting the total number of items in the internal list rather than just the number of items in the current Event Selection List.
• Fixes issue of using popup command Shift Times Forwards/Backwards not handling untimed items properly (it should only adjust untimed items by days).
• At conclusion of AutoSync, now relaunches Pimlical to ensure that all databases are immediately refreshed to the screen.
• Speeds up AutoSync when mode is set to Server Overwrites by removing test for uniqueID's (except when debug mode is set) as it should not really be necessary (unless the calendar on the server is corrupt, etc.).
• Increases the indent in the first column in the Appt/Float/Tasks displays when editing a filter for better aesthetics.
  

• Adds new preference: ReminderPrefix which allows the user to automatically prefix the Event description of an Advance Reminder with some text. The default is to have nothing. Using a prefix may be especially useful when sharing an Android calendar with a non-Pimlical user (because it would be less obvious that this is an advance reminder as opposed to the event itself on that calendar). The prefix is applied when the Advance Reminder is created. For example, you could set it to something like: Upcoming:, so you would see [12]Upcoming: Bridgeton Symphony Concert, when the concert was 12 days away. Previously, you would only see [12] Bridgeton Symphony Concert in Pimlical and in another calendar App, you would only see the Event Description itself, whilst now you would see Upcoming: Bridgeton Symphony Concert.
• Find and Find+ can now search for items based upon the Font Size (less than or equal, equal or greater than equal) for items that have a custom font size set. If the preference ListOfFontSizes is not properly matched across all platforms with regards to the table length, custom font sizes can get unexpectedly corrupted or changed. This command makes it possible to find those items and display an Event Selection List at which point the Change Font popup command van be used to fix them, or just to change all items in one fontsize to another size. 
• If multiple items are selected on the Change Font popup command and there are two or more different font names, an alert dialog appears allowing you to set the entire selected font (Change Font) or just the fontsize (Change Size Only), the latter leaving the fontname untouched.
  
• The preference UseNotificationWhenAlarmTriggers is now a subscription feature, which if set to True (default is false) will also create a notification in P/A, and that in turn will cause a notification to appear on a paired Smart Watch. Previously, the only way to get notifications on a watch was to forgo the full-page alarm system on the phone.
• If the Widget Refresh sees that P/A is active (doing a backup, etc.) - the Widget now skips the refresh cycle completely rather than attempts to reschedule - should be safer and avoid potential conflicts with P/A.
  
  

• Ensures that if the user long-presses a command bar button after AOS has absconded with all of Pimlical's memory (i.e. user returned to Pimlical after a long period of time) that Pimlical properly relaunches itself to re-initialize everything (including re-reading preferences, calendar, etc.). When this happens, the button press itself is ignored.
• Whether to use the full-page alarm dialog or the notification system is now uniquely controlled by the preference: AlwaysShowNotificationForAlarm. Previously, the preference UseNotificationWhenAlarmTriggers had to be set to the same value. That latter preference is now ignored for non-subscription users (see section above for new, subscription only, usage of this preference).
• When modifying multiple items with a popup command on an event selection list, the warning message about all alarms being in the past is now completely suppressed (since it's not really useful when processing multiple items). It's also now suppressed when finishing the edit of a template (since the template date is not relevant).
  

• If the Widget filter has a custom preference file attached to it, then at the conclusion of the Widget Refresh, Pimlical restores the prior filter in effect. However, it was not catering to the possibility that the filter that was being restored itself did not have a custom preference file, in which case, Pimlical should re-read the default preferences. It was doing that, but Also generating an unexpected Error File complaining about a missing custom preference file (at which point, it then did the right thing and re-read the default preferences). It also failed if the filter being restored was marked as having a custom preference file, but the custom preference file had been deleted or was not present (for example, the filters were restored from the .FLT files, but the custom preference files were not restored).
• The overnight floating advance now includes a cleanup of no longer used file links and images stored in the PimlicalLinks and PimlicalImages folders. Files that are no longer referenced are now deleted (and logged into the PimlicalDebugInfo.log file). Note that the original file (which was copied to PimlicalLinks or PimlicalImages) remains untouched.
  
  

• Fixes an obscure issue related to the conversion of font sizes from a generic size (based upon an index into table of fontsizes) to a true font size for that platform (previously, an item could unexpectedly get the generic size set as the true font size.
• The font preference: ListOfFontSizes has been expanded and modified to provide a better range of choices for font sizes. It is also now aligned with an updated font table in P/D as well. If you use custom fonts and sync to other Pimlical Calendars, make sure that this preference has the same number of entries on all platforms, otherwise, problems can arise when fontsizes are synced back and forth. 
• Includes a voodoo fix from V-4.3.29 to work around what appears to be a new bug in the Android OS whereby it fails to reliably resize a dialog when the on-line keyboard is invoked as the user taps on an Edit Field - this fix has now been applied to the Contacts Find and Contacts Edit dialogs.
• Fixes obscure (but new) issue of AOS issuing a spurious alarm callback to pimlical when the next alarm was at a very different time. Under these conditions, Pimlical attempts to display an Alarm warning the user about something odd going on with AOS and alarms, but fails to clear an internal flag that then prevents Pimlical from rescheduling any further alarms. At this time, this issue has only been see on one of the Beta Tester's phones (so it could be a problem either with that specific phone, or with some other third party app??).
• Changes the default name of the Modifier and Creator fields to use the AutoSyncName preference (previously, it used the ReferenceID). This change was made because the AutoSyncName is modifiable, and is also different on every platform (so it makes it possible to tell on which platform an event was last modified or created).
• # The AutoSyncName preference, if it has not been provided by the user and is blank, is now defaulted to {Android Model}_#### where {Android Model} is the Android Model Name (as provided by AOS) and #### is a semi-random four digit number.
  
• (Internal: Added flag: FLAG_UPDATE_CURRENT to all Pending Intents, checked saveInstanceState to supposedly avoid stale intents).)

• Fixes new issue in prior V-4.3.29: If you run Backup everything, with the preference BackupEverythingUsesDateTimeStamp set to True (default is false), and are not using a Remote Server for backup, and your PimlicalBackups folder is completely full, V-4.3.29 was using the wrong name to pre-delete the oldest backup copy in the folder which could result in endless error messages being generated.
• Fixes another new issue in prior V-4.3.29 - during changeover from old backup file name format to the new backup file name format on local filing system (i.e. BackupEverything vs. All) or when using Remote Server (BackupEverything vs. {devname}_All, the choice of the oldest backup file could be incorrect because the sort routine was not always correctly finding the embedded date in the backup filename. Also caters to moving backup files from local to remote or vice-versa (i.e. if a remote backup file that had the device name is moved to the local ../PimlicalBackups folder - items will still be sorted correctly).
  
  

• Corrects a new issue: the checkbox for displaying subordinates in the Template Dialog was getting unexpectedly cleared on every refresh of the dialog. Now, the checkbox is only cleared on the first entry into the Template Dialog.
• Adds a new preference: AllowWidgetToRunBeforePA (default value is false), which, if set to True, allows the Widget to run even though Pimlical/Android has not yet launched. It will also allow the widget to run and refresh whilst the Event Selection List dialog is open on the screen. Most users can probably safely set this to True to gain a more frequent refresh of the Widget. However, the potential for some obscure conflict to occur can not be completely ruled out, and if that happens, setting it back to false is advised (and contact Tech Support if so). Will likely have the default changed to True in the next release if it appears that all potential conflicts have been side-stepped.
• Fixes new issue in the Internal File Manager of copying or moving a file either to or from a Remote Server to the local device (or from Remote Server to Remote Server and simultaneously providing a different name for the file on the target device (previously, it was attempting to access or store the original or target file using the wrong  name).
• Fixes new issue in the Internal File Manager of using Open or Share on a file on a remote server.
• When using the internal File Editor (Long-press on Open+ button), if the file was retrieved from a Remote Server OR if the file had an extension of .log or .error, it was copied to the local device with the name Temp.Txt, the text is not editable (but can be copied), and the title displays View instead of Edit.
• Avoids creating error files when AOS unexpectedly invokes the Widget to setup buttons when the Widget Preference shows that it was not installed(!).
• Fixes error in Icon Restore function whereby it was not always looking for the backup file in the correct directory (since the new update that with a subscription present would put the IconArchive.dat file in the ...Pimlical/PimlicalIcons folder, rather than the main Pimlical folder).
• Avoids launching the Widget for Refresh if either an alarm is being processed, or if the nightly floating advance is active (avoids conflict with running Backup Everything at same time Widget might be refreshing). Previously, the Backup everything could run twice because of anomalies from the conflict.
• Internal File Manager dialog now scrolls so it can be used in landscape mode.
• Includes clearer information message when Menu | BackupEverything finds that Backup Everything is set to use a Remote Server - at this time a direct Restore from the backup on a remote server is not supported (you would need to copy the folder to the local device with an Android File Manager).
• The filenames used for Backup Everything with Date/Time Stamp on a Remote Server have been changed from BackupEverything_{DateTimeSize} to {AutoSyncName}_All_{DateTimeSize}, to distinguish between backups saved by multiple devices.
• Fixes an obscure problem with the Widget when it has to create a new Widget Filter, that could result in a problem updating the System Preference File with the filter.
  
  

• Works around bug in Android OS (this is new apparently? And the fix involved shuffling code around that should make no difference whatsoever!) whereby raising the online keyboard would on quite frequent (and seemingly random) occasions fail to resize the screen properly, with the result that the dialog buttons were left hidden behind the keyboard at the bottom of the screen (requiring the user to dismiss the keyboard in order to access the buttons).
• Avoids a very obscure issue which was causing BackupEverything not to run at the conclusion of the floating advance when (a) the preference AlwaysShowNotificationForAlarm was set to True and the Android OS notified P/A that the system clock's time had changed (this was found because one user was constantly getting bogus Time Change notifications from the Android OS).
• Avoids an obscure issue that could cause Exception Errors on the floating advance, when AOS had absconded with Pimlical's memory and the Android calendar was being updated.
• Improved some error messages and tests in the Licensing Routines, and expanded functionality of Menu | Debug | Internal Reset to include a few more items.
• On very rare occasions, the original Subscription status may not have been re-read over an unusual restart from Android OS, so the dialog that appears complaining about the Subscription status (currently displaying just Not Now or PayPal) now includes a button Check Subscription which will re-read the subscription status, and avoid repeated complaints if in fact the user had a valid subscription.
• The feature to attach error files and log files to an email (Menu | Help & Usage Tips | Email Tech Support), now copies all those files to the folder: /Pimlical/ErrorAndLogFiles and then attaches them to the email. This avoids the problem of email programs being unable to attach files directly that are in Pimlical's Scoped Storage area (due to restrictions AOS imposes on other Apps accessing those files, even when launched from Pimlical - clearly an App should have the ability to grant such a permission if it chooses!).
• If the user is using AutoSync, syncing preferences or BackupEverything, and never set a custom name (to identify the device) for the preference: AutoSyncName, Pimlical now provides a default name using the Device's Model name (as reported by Android OS and displayed in Menu | About) plus a number representing the low four digits of the number of milliseconds since the app was last launched (to further ensure there's no clash if the user is syncing to a RemoteServer with more than one identical devices) resulting in something like: Pixel_10_Pro_3425. Previously, the name was defaulted to AutoSync_{Platform}_{time_milliseconds}, if left blank. This preference is automatically globalized across all custom preference files.
• Made a slight adjustment to the Permissions to ensure that Android OS was not confused by requests for triggering alarms at the exact time, by not requesting the permission Schedule_Exact_Alarm on AOS-13 and later (where Use_Exact_alarm is used instead - unknown if this is even a problem...).
• When Android OS fails to notify Pimlical in a timely manner about a set alarm (threshold is 20s), a message box now appears indicating that some alarms may have been missed.
  

• Avoids issue with alarms being prematurely terminated due to bug in AOS where it issued an unexpected (and erroneous) onPrepareDialog() callback to the main activity, whilst an Alarm Dialog was displaying in a separate activity (callback sent to wrong activity by AOS?).

• When inserting a Master Template, but the checkbox is set to display subordinate templates, a brief "toast" message now appears: Subordinates NOT included because they are currently displaying as a reminder. 
• The checkbox for displaying Subordinate templates was (in V-4.3.26) remembering the prior setting, but it appears to be better to automatically clear it on entry (due to the fact that if checked, subordinate templates are not included if the Master is inserted).
• Removes a test that could potentially result in skipping the automated Backup Everything in either (a) the unlikely case where an Alarm was still displaying when the nightly floating advance was performed, or (b) AOS was in the process of terminating P/A, but then subsequently generated an unexpected (and bogus) callback to P/A to handle a change of the System Clock and then terminated the sub-thread before it could properly conclude. It was this latter bug in AOS that was seen recently.
  
  

• If you are in a phone call and have the preference AutoSnoozeDuringPhoneCall set to True, and an alarm triggers, Pimlical will now Auto-Snooze the alarm but (as in V-4.3.26) ensures that (a) it does not play any notification sound, and (b) vibrates if vibration is called for and available on the device. This change means that the snoozed alarm will appear in the upcoming alarms list (and re-trigger after the phone call ends) provided that the preference: AlarmSoundRepeatCount value is not exceeded.
• In DirectSync, if you have more than one IP Address in the preference: HttpAddressesForSync, and select an IP Address when there is no WiFi or internet connection, you now get the same message as you get if there is just a single IP Address in that preference (previously, an error dialog appeared, but it indicated there was a file Transfer Error, rather than a missing Network/Internet Connection.
• Removes the restriction in Find function of combining a word search with boolean searches (previously you could not combine them both). So you can now search for Cat && Dog with a word search and only find events that include the word Cat and the word 'Dog' (and skip events that had say Hotdog and Locate).
  
• Removes a couple of obscure cases where an error file was being generated as AOS was issuing an onStop() callback when it had already absconded with all of P/A's memory (benign error condition that can be ignored).
  
• All logs (errors, warning, info) from both DirectSync and AutoSync are now written to the PimlicalDebugInfo.log file (presuming preference EnableDebugLog is set), so everything is in one file. Previously (for historical reasons), a good number of the logs were written to the Pimlical AuditTrail log file.
• Avoids triggering an automatic backup of files while DirectSync or AutoSync is running (could result in thread conflict which could cause the sync routines to fail).
• If the Recent Icon List is completely full and not write-protected (the recent icon list is protected if it begins with a .NoUpdate tag), and a new icon is accessed, the last icon in the list (the oldest) is dropped and the new icon inserted at the top. Previously, once the list was full, no further icons would appear in the list.
• If an alarm triggers during AutoSync or DirectSync, Pimlical now ensures that after autosnoozing all alarms that it does not try and re-read the local calendar by relaunching Pimlical (which could result in a further thread conflict).
  

• The final correction for this issue: If Backup Everything encounters an exception condition, there are some conditions under which a flag was not getting cleared which could result in a blank (black) screen appearing in Pimlical. In V-4.0.25 if Pimlical was in the foreground, the screen was not refreshed at the normal termination of Backup Everything.
• Fixes issue that the Template Dialog was not initializing the checkbox to display Subordinate Templates from the most recently remembered setting in the current session (in a new session, it starts out by hiding subordinate templates by default, in the same way that subordinate events are normally hidden at the start of a new session). Note that the setting for hiding subordinate templates is a separate setting from hiding subordinate events.
  
  

•  If you are in a phone call and have the preference AutoSnoozeDuringPhoneCall set to True, and an alarm triggers, there were some conditions under which the notification could get lost, leaving no trace of the missed alarm. This release ensures the notification is preserved and properly (a) does not play any notification sound, but (b) vibrates if vibration is called for and available on the device.
  
  

• Fixes an issue in the Internal File Manager of copying or moving a file from a Remote Server to local device, then returning to Remote Server with long press on the Local Folder/Remote Folder+ button and finding an empty file list and no way to navigate out of it.
• Another correction for this issue: If Backup Everything encounters an exception condition, there are some conditions under which a flag was not getting cleared which could result in a blank (black) screen appearing in Pimlical.
• 
  
  

• Corrects a really obscure case: if you delete a Google Calendar that was referenced in a Quick Entry Template, then re-create the calendar with the identical name, it was impossible to "fix" the template so that it would pickup the correct databaseID of the newly recreated calendar (since Google might change the databaseID of the calendar, even though the name remained the same), resulting in an error condition that made it impossible to update. 
• In DirectSync, if there is an indication of a File Transfer Out of Sync error, the note/query:  (Do P/A and P/D Match on both Major and Minor versions?) is now included (as that's often the problem).
  
  

• If Backup Everything encounters an exception condition, there are some conditions under which a flag was not getting cleared which could result in a blank (black) screen appearing in Pimlical - this was corrected in this release.
• In DirectSync, ensures that the sub-folder Android/PimlicalCalendars is properly created prior to writing out the Android Calendars for syncing to the desktop (using the preference: SyncAndroidCalendarsForDesktop). This avoids an error file and error condition complaining that a File Transfer Failed. AutoSync had always ensured that folder exists.
  
  

• Adds some new logs to track obscure issues that have been reported. 
• Fixes a new issue (from recent Beta Preview) in Contacts Section that if you perform a case-insensitive search, but have upper case characters in the search string, it was not finding the contact.
  
  

• Fixes an obscure issue with Android Calendars that could potentially cause repeat events with exception lists to be rewritten, expanding the size of the Android calendar unnecessarily.
  
  

• Addresses a new issue: when preferences are reset or restored, Pimlical now immediately re-reads the preferences and the calendar so the new configuration is immediately displayed (V-4.3.22 did not do that right away).
• Corrects an error in the usage of the new preference: AutoSnoozeDelayDuration which was not being internally converted to milliseconds properly.
  
  

• In the Find+ display, deleted records display [X] in front of the date and filename.
  
  

• Adds a new, special preference only to be used with versions of AOS that have the onStop() callback bug (symptom: AutoSnooze triggers early - currently hard-wried to 30s). Prior release had a 30s forced delay to sidestep that bug - this preference now has a duration value (default is 30s) which can likely be extended for those users seeing this issue. This bug was apparently fixed at some point, although some phones that did not get the AOS update that fixed it will continue to exhibit this issue.
• Main Preferences layout has been revised to put three buttons (Backup, Restore and Reset) above the OK, Find, Cancel buttons. Previously, the Reset function was located in the Restore Dialog which could confuse the user - also, the Reset function was not available if there were no backup copies present). And both buttons now return to the preferences dialog if Cancel is tapped.
• Avoids generating a spurious (but benign) error file and error message about an error writing System Preferences, immediately after System Preference file is manually reset.
• Reverifies license immediately after resetting System Preferences to avoid potential complaints about a missing subscription for preference items that requires one, when in fact the user was subscribed.
• If the preference EditQuickDialogReturn is set to false (default value), it now properly returns to the event selection list after editing a repeat event (regardless of what was selected in the Repeat Exception Dialog).
  
  

• Fixes a new issue in accessing Remote Server from File Manager whereby on occasion it would appear to get "stuck" on the root directory with no way to get beyond that point.
• Fixes another error in Remote Server handling when using Open command on a file stored on the Remote Server. Since Open cannot operate directly on the Remote Server, Pimlical has to copy the file to the local filing system with a temporary name and then use that to submit to the AOS Open function (previously, it was using the wrong filename to copy the file from the Remote Server).
• Find (and Find in All) function now includes a checkbox to search the Link field of a record for a text match - this makes it possible to locate events based upon the file(s) they are linked to. Find In All displays <L> to show that an item has a file link (not necessarily a matching file link).
  
  

• Fixes new issue in V-4.3.19 whereby the Find function in the Memos and Contacts Section was performing a case-sensitive search when it was not called for - giving the impression that the Find function was not working.
• Reverses the way the Find+ button works in Memos And Contacts from prior version - a brief tap will reset the filters to All, so that the entire database is searched as a default, whilst a long-press will preserve the existing filtering (for example, if Recents or Favorites are selected). In the prior version, if the startup view was set to Favorites or Recent, a tap on the Find button would only search those sections often resulting in a puzzling, empty display.
  
• Ensures the program is now consistent with the documentation regarding the Multi-Day and Weekly Views and the start of the week, and with P/D. To lock the Weekly View to the Start of the week (as defined by WeekViewStartOfWeek) set the preference LockWeeklyViewToWeekStart to True. To lock the Multi-Day view to the start of the week (using that same preference: WeekViewStartOfWeek), check the box: Force Day+ view to Start of Week in the Repeat Rule & Views tab of the current filter.
• When just an instance of a repeat event is being edited, and if the event is in the local calendar, you can now set a new repeat type on the instance. Previously, attempting to change the repeat type at the same time the instance was being first edited, was rejected.
  
  

• Scans the preference: BackupEverythingFolder for illegal characters and removes them (previously, a user could create invalid filenames which then resulted in a failure to perform the Backup Everything properly).
• Updated the documentation for Calendar, Memos and Contacts for the Find function to document that they support boolean searches using && and || operators (which actually has always been supported). You can use the special character sequences: && and || to signify a logical AND or OR condition (Subscription Feature) in the find. For example: Dog || Cat would find any item that contained Dog OR Cat, whilst Dog && Cat would only find items that contained both Dog AND Cat. You can string multiple AND's and OR's together, but they will always be evaluated from left to right as a simple expression (this is not a sophisticated, hierarchical expression analyzer!).
  
  

• Another fix to the issue of AOS stepping on itself when issuing an onPrepareDialog() callback (issue was Pimlical appearing to hang after being re-activated, following loss of all of its memory).
• On initial entry to the Memos or Contacts Section, any pending Find string (for text filtering) is removed. Also, the last used Find String is now remembered for the current session and will be restored when re-entering the Find Dialog.
  
  

• Avoids generating an uncaughtException error file from the new Set Snooze Alarm feature which could occur while scanning for pending snoozes (pending snoozes set by this command suppress any earlier alarms set on the event itself).
  
  

• Corrects the problem of the wrong default values being set for the eight, new long-press Command Bar preferences which under some conditions would cause the old behavior of prior versions to get lost.
• Updates the Memos and Contacts sections so that you can combine category selection and text matching with the Favorites and Recents startup views (or selections) - previously that would override the default startup view.
  
• Fixes issue that the correction for Memo/Contacts Delete in V-4.3.18 was imperfect and resulting sometimes in complaints that a single category was not selected (when preference MultipleCategorySelection was True).
• Eliminates a discrepancy in setting defaults for new preference items that was causing some preference items and the contents of some preference items to be incorrectly initialized.
• Fixes the icons in the Memos section so that the Find button when editing a memo does not display the + legend (which would otherwise lead the user to believe there was some dedicated long-press function). Also changed the Find Next button (double-right-arrow) to be grayed out when there is no active find String.
• A long press on the Category Select+ button in the Memos and Contacts sections, when all categories are selected, now displays no categories initially (to make it quicker to select just one category when all categories are currently selected and there's a really long category list).
  
• Fixes issue in an Event Selection List of attempting to display a future instance Date for a Repeat event when the last instance is still prior to today, or using the Repeat End Date (when the Repeat End Date was still in the past) - and also displaying the Instance Date icon when in fact in these two cases, it would be the start date of the repeat series that was used, not the instance date.
• 
  
  

• Adds new popup command: Set Snooze Alarm which sets a Snooze alarm on the event (even if the event itself had no alarm set). Any future alarms on that event will be suppressed until that snooze alarm triggers. The Popup command appears in both PopupListCommandsForEvent and PopupListCommandsForMultiSelect. The alarm sound for snoozed events is used when the alarm triggers. In the upcoming alarms list, these items will display [S] to signal the alarm was set from the Set Snooze Time command.
• Fixes issue of using the new Delete Memo (or Contact) button when preference MultipleCategorySelection is set to True (was always complaining that mulitple categories were selected even when only one category was).
• 
  
  

• When handling alarms, the new status type of Absent is treated similarly to Canceled (namely the alarm will be ignored).
  

• File Rename in File Manager now permits a rename that only involves changes to the upper/lower case of characters in the path (previously, a case-insensitive match discarded such renames). Since many OS's refuse to rename directly in this specific case, P/A renames the original file to a temporary file, then renames the temporary file to the new filename to ensure this works as expected.
• Adds Delete button to the list provided by Menu | Select Categories, and by tapping Category Icon in the Memo and Contacts sections, to make it more obvious how to delete a category - just select one category and tap the Delete button - note that the category must be empty for it to be deleted. If not empty, a list appears of all the places where the category is in use. Deleted Items are followed with [X].
• Implements eight new preferences: CommandBarButtonView0Long, CommandBarButtonView1Long... CommandBarButtonView7Long. These parallel the eight existing preferences (without the 'Long"), and override any existing long-press functions that would otherwise be assigned to the function at that position on the command bar. This maintains full backwards compatibility (it won't overwrite or change any existing use of a long-press on a Command Bar (such as a long press on Templates 1-4 to select templates 5-8). Also, the number of available templates/filters/views has been increased from four to eight (so it is now possible to have more than four templates, views or filters on the command bar. This makes it possible to invoke 16 discrete commands from the command bar.
• Adds Only Master{/Subordindate} Events checkbox to the Find function. If checked, only Master and (if Subordinate events are currently displaying) Subordinate Events will be displayed (that also meet the other find criteria). If Subordinate events are currently hidden, the checkbox displays Only Master Events and only Master Events will then be displayed. Previously, there was no simple way to locate all Master (and subordinate) events in the database. 
  
  

• The menu command to list upcoming alarms now displays the list even if the preference PimlicalAlarmHandling is set to None - a brief toast message appears though informing the user that no alarm will actually trigger because of the preference setting.
• Selection dialog of links (when more than one link is present and Edit Links button in Edit Dialog is tapped) now has the legends View (used to be OK), and Done (used to be Cancel) - making it clearer what those buttons do.
• Fixes issue of the popup command Change Category in multi-select mode not always changing the category of all selected items.
• Fixes some unexpected display anomalies (especially in the List View) when the preference StripEOLsForDisplay is set to False and there are explicit EOLs (including consecutive EOLs) in the description or other included fields.
• About Dialog, instead of displaying Heap Size, now displays Mem: and three parameters: Memory currently in use, recommended available memory for Apps, and maximum memory available.
• Works around an issue of AOS reactivating P/A when memory is gone after user touches the screen in a main view.
• Fixes issue of having templates with EOLs in the description being used in the preference: TemplateNamesForCommandBar (was causing template to not be found).
• Ensures that any temporary categories added in the current Memo or Contact session are removed when you exit the Memo or Contact session.
• Prevents the popup command Change Date from unexpectedly making exceptions in multi-select mode when the user taps the CANCEL button in the Date Selection Dialog.
• Fixes a very obscure issue of a missed alarm when AOS reports to Pimlical that the SD Card was unavailable (for some unknown reason) and the internal interval timer tripped just as the alarm was in the process of triggering.
  

• When invoking the File Manager from the main menu and Remote Server(s) are configued, but the FTP Client cannot connect, an appropriate error message is now displayed. Also, the timeout for testing to see whether Pimlical can log into the Remote Server is now forced to be 5s (since too many FTP clients fail to implement the  setDefaultTimeout() function properly). You can always long-press on the File Manager button in the main menu to manually select the Local Filing System. This version also better handles the cases where WiFi is not available, or where a user attempts to log into a remote server when none are configured, etc.
• Includes the new TemplateUID, Creator, Modified, CreationDate and Modification Date fields now in the comparison performed by Compare Calendar Events popup command.
• Avoids displaying the Instance Date icon ('i' in a circle) in the Meeting Lists where it should have always been hidden.
  

• Includes a test for Android OS sending an invalid callback to onActivityResult() which it will now ignore (previously it would result in an error file). Does no harm to ignore the invalid callback in this case.
• If an event links to a memo that no longer exists in the memo database (i.e. it was deleted AND removed completely from the database), Pimlical now displays a brief message; Memo Not Found. Previously, it was creating several UncaughtException error files. This now behaves identically to how a now, non-existent contact was handled.
• If an event links to a local file that no longer exists in the filing system, the error message now includes the information that the error condition can occur as the result of a file not found (previously, only mentioned an issue related to not find an associated App to open the file.
• Now displays an 'i' in a circle ahead of a repeat instance date in an event selection list (when the preference ShowInstanceDates is set to true, the next instance on or after the selected Date or Today is used instead of the Start Date for the Repeat event).
• A tap on the Repeat Icon in an Event Selection List now includes the start date for the repeat (this is useful if the preference ShowInstanceDates is True as you would otherwise have to edit the event to see what the start date was).
  
• Ensures the Master/Subordinate linking field (TemplateUID) is now included in the test for records being identical - prior failure to include that field could have resulted in odd behavior of a subordinate link being lost or not updated properly.
• If the preference StripEOLsForDisplay is false, the word-wrap routines now permit multiple, consecutive EOLs to appear unchanged in the display in the Main views (where multi-line descriptions are permitted). Previously, multiple, consecutive EOLs would be replaced with a single EOL regardless of that preference setting.
  

• Fixes issue of the automatic insertion of subordinate templates that repeat on a specific day of the week not having the day of the week and repeat end date adjusted based upon the new day of the week that the subordinate template was inserted on. Note that if the item repeated on just one day, that day is replaced with the new day of the week, but if the template repeats on two or more days of the week, the potentially new day is added to those existing days.
• Fixes issue of the automatic insertion of subordinate templates that are floating and have an explicit due date not having the Due Date adjusted by the date that the subordinate template was inserted on.
• Fixes issue of the popup commands that normally obey the toggle to make exceptions or not to repeat series sometimes resetting the toggle to force exceptions after the first item in a list of multiple items has been processed (so subsequent repeat items in the list might have exceptions unexpectedly forced).
• The Template Dialog display now includes the start date of Master and Subordinate templates (so if they occur on different days, the date offsets are readily visible). Also, all repeat templates display the start date of the repeat, regardless of the setting of the preference ShowInstanceDates (which only applies to events).
  
• 
  
  

• When using the popup command Find all Linked Events, the title of the Selection Dialog now shows: Linked Events (3), where the number in parentheses is the number of linked events. 
• Edit dialog field for Master/Subordinate linking now displays Templ. on label and Link to a Master Template on the button if editing a template.
• The Link to a Master Template button (i.e. a template is being edited) now finds the Master in the list of Templates rather than list of Events (previously, it was not recognizing that it should be searching the Template list rather than the list of calendar events, AND might have potentially set a link to a Master event in the calendar, rather than the appropriate Master in the Template Array!).
  
  

• Fixes an occasional inconsistency in the way that unacknowledged alarms are handled - in particular, after the count of unacknowledged alarms exceeds the value set in preference: AlarmSoundRepeatCount, it should consistently leave a notification in the notification bar and stop autosnoozing the alarm. It also seems a change around the time of Android-11 impacted that way that this previously operated.
  
• Adds new popup command in Template Dialog: Template Attributes which creates a file containing all the attributes of that template (this is primarily intended for diagnostic use). The default name of the file is TemplateAttributes_YYYYMMDDTHHMMSS.log (but you can edit this name before tapping OK button).
• When tapping a link icon to view a specific contact or memo, any current filters set for the associated database are cleared (because they may have been left set for some other item and that might confuse the user seeing something different there during/after proceeding with the link).
  
  

• Fixes an UncaughtException Error that could occur when editing a template (that had never been inserted) that had two or more Hyperlinks and user long-pressed Hyperlink button in Edit Dialog and then used the Remove button to remove one of them.
• When editing a template, the title of the Edit Dialog now displays: [Template] {Event Description} to remind the user they are editing a template and not an event (it's really easy to inadvertently insert a template and start editing thinking one is editing the template and not the inserted event).
• 
  
  

• Additional code to deal with AOS sending old/stale intents to Pimlical. This may prevent the symptom of Pimlical appearing to ignore the first tap on the launch icon, or in some other cases, when being relaunched off the Recents list.
  
  

• Preference filenames synced over to Pimlical/Desktop using DirectSync are now setup identically to how AutoSync handled the filenames (in particular, AutoSync included an underscore between the Device Name (from AutoSyncName preference) and the filename. DirectSync now does the same thing (also using the device name from the preference: AutoSyncName).
  
  

• If P/A's memory has been absconded with (without notification) and P/A is relaunched with a bogus callback to onPrepareDialog to rebuild the Event Selection list (when none existed and that dialog was not open), Pimlical will now simply attempt a relaunch of itself. This should avoid a case where it appears that Pimlical crashed/ignored the first attempt to launch it, etc.
• The Action Tag ScheduleIn: can now have just the value of Today to set the current date. It will also pick up the current time if the template was originally timed (so use no time in the template to just set today's date with no time). The locale for the ScheduleIn: tag is also set to the current Creation timezone preference value (previously, it was set to the current timezone preference value).
• Fixes new (benign) issue in V-4.3.08 whereby an error file was being created when exporting templates if there was no existing PimlicalExportTemplate.dat file.
• Fixes side effect of a change in V-4.2.23 to allow custom preference files attached to filters to be processed prior to the display of tasks which was, however, not properly saving a newly selected filter to the preference: DefaultTasksViewFilter with the result that it was not possible to select a new filter in the Tasks View. Also this updated filter setting is applied globally to ALL preference files.
  
  

• Adds new preference: TldsforUrlLinks which has a list of all the Top Level Domains (such as .com, .org, .net etc.) that can be used for URL Links and the feature to try and automatically extract the domain name to use as a tag for the link. Default value includes many of the most common TLD's (com/net/org/edu/gov/info... etc.). This allows the user to add their own (such as their own country, etc.).
• Fixes issue on inserting Master and Subordinate templates, that the TemplateUID field of the inserted Master Template (which was updated with a new uniqueID) was not always properly reset to that new UniqueID.
  
  

• Now sorts the quick entry templates so that all Master Templates follow the regular templates. Regular templates are sorted alphanumerically, then by start date/time. Master Templates are sorted alphanumerically, and subordinate templates are sorted, immediately following their associated Master Template, alphanumerically, then by start date/time. The Master Template Array is also checked for corrupt templates.
• For consistency with Pimlical/Desktop, Pimlical/Android now only inserts subordinate templates if subordinate templates are being hidden in the Template Dialog. This makes it possible to insert specific subordinate templates without necessarily having to insert their associated Master template.
  
• Fixes a new alignment issue in some list selection dialogs (such as is used to display groups).
• Fixes an issue of getting an UncaughtException error file and error dialog on logging into AutoSync under some unusual circumstances (usually associated with invoking AutoSync immediately after prior AutoSync ended).
• When deleting all templates, Pimlical now backs up the existing PimlicalExportTemplate.dat file to PimlicalExportTemplate.bak prior to backing up all the templates (so any existing copy of that file is not immediately overwritten).
  

• The useful feature of putting specific templates or filters on the command bar is now much easier to use because the preferences: TemplateNamesForCommandBar and FilterNamesForCommandBar now display a selection list of those items (where you can select them and also move them up and down) to set the preference values (previously, you had to manually edit a string carefully to set those up). The list also shows the position of the originally selected commands as <T1> or <F3> etc. and updates those designations as items are moved around.
• The list dialog that handles the StringsList type preference (popup commands, menu commands, etc.) now has improved instructions and button labels to make it easier to see how to use the selection and move functions. The UP and DOWN buttons now also display a + to indicate that a long-press on the button moves the item to the Top and Bottom of the list respectively.
  
• In addition to handling the sharing of text files (V-4.3.06), in this update, if there is no text file, Pimlical checks to see if there's any text saved on the Android System Clipboard and will use that as the shared text for this function. The text is also copied to the system clipboard.
• Fixes a typo in the popup command: Find All Linked Events that was causing subordinate events to be missed.
• When editing a template (from Template Dialog), the button that shows the link to a master event now displays the description of the Master Template to which it is linked (previously, it would typically be blank because it was looking for the linked master in the Main calendar database).
• Feature to create a tag automatically from a URL (on a URL Link) now includes .gov as well as .io) - next release may use a preference item for this so users can add their own URL's (especially for say country TLD's).
  
• 
  
  

• Now prevents Pimlical/Android from responding to AOS's onResume() callback when it follows a spurious AOS generated callback (where AOS sends the wrong intent to P/A) to onCreate() or onNewIntent() - this was potentially causing some error files to be created which can hopefully now be avoided and improve recovery after the spurious AOS callback.
  

• A long press on the T1 - T4 buttons on the Command Bar (to invoke a template as defined by the list of template names in the preference: TemplateNamesForCommandBar) now invokes templates T5 - T8, thereby doubling the number of templates that can be used on the Command Bar, without taking up any more buttons. This feature is also implemented for the Find Filters (F1 - F8) and the View Filters (V1 - V8). These extra functions #5 - 8 cannot be assigned directly to a dedicated button on the Command Bar).
• Pimlical now registers for the Sharing of standard Text files, and (as contacts do now) sets up the text file for sharing into Pimlical's Memo Database. On the next entry to Memos (from Menu | View/Edit Memos, or Widget button), the shared text will appear in a newly opened memo (tap the Green check button to save, or red X button to discard the pending memo).
• The Edit|All+ button in the Alarm Dialog now presents all selected events in Date/Time order of Start Date, starting with the earliest item, after that, events are sorted based upon the current filter, except that if the user has defined a custom filter with the explicit name: EventSelectionFilter, that filter will be used just for this specific sort.
• Adds new popup command: Change Time to the preferences PopupListCommandsForEvent and PopupListCommandsForMultiSelect to change the time of all selected event(s) to the specified time (the date is not changed).
• NOTE: The checkbox in the Event Selection Dialog, Make Exceptions: Delete & Toggle Commands, now also applies to all the Advance commands (Advance 1 Day, Advance 1 week, Advance to M/T/W/T/F/S/S, Advance to Today, and Advance to First of Next Month), and the checkbox legend has been updated to include advances. Previously, since V-4.2.23, the Advance commands were not included and therefore exceptions were not created for repeat events.
  
• 
  
  

• Avoids an UncaughtException error if a user long-presses the Internal File Manager button (to get a list of Remote Servers) when the preference RemoteServerList was blank (to use the long press, the RemoteServerList preference must contain at least one Remote Server).
• The text field for editing String preferences now wraps to mulitple lines (previously, the text was displayed on one line that scrolled horizontally).
• An obscure bug in the Event Selection List has been fixed that could result in event selection lists for things like Find, upcoming alarms, etc. to lose the dates on events when the list was re-displayed.
  

• A long press on the Edit | All+ button in the Alarm dialog which used to mark a single item as Done, now displays all selected items in a regular Event Selection List (where all popup commands are available). On initial entry, all items in the Event Selection List are selected in multi-select mode. The event selection list is re-displayed after popup commands have been issued (so you can say mark all items as completed and then remove alarms from all of them, etc.). Non-selected items in the Alarm Dialog are auto-snoozed. Use care when applying multiple popup commands - for example, if you advanced a repeat item to a different day and then made an exception, Pimlical might not be able to determine what day the exception was being made for. The Edit | All+ button is not available if the alarm triggered over an active Edit Dialog.
• A long press on the Menu button (on the command bar) will now force the display of all menu items by using the list of all menu commands.
  
  

• Sync logs now display [X] at the start of the log for deleted records (prior to event start date/Contact Name/Memo Title) rather than at the end where it is not visually obvious.
• When syncing events, if Device/Desktop and Server events match on the uniqueID but the creation dates differ, this is now logged as a Warning in the log file (in theory, if the events match, the creation date should also match).
• Events created in Google (or Android) Calendar that do not have the Pimlical Creation/Modification date fields are now preset on their first appearance in Pimlical so thatthe creator/modifier fields are set to ExternalCalendar, and the creation/modification dates are set to the current date/time that the event was read.
• The colors used for selecting/unselecting events in Multi-Select mode in the Event Selection List have been changed to avoid confusion with the icon for a completed, floating event.
• Avoids an UncaughtException error if a user brings up a StringsList preference (such as MenuCommandsAndOrder), taps the Up or Down buttons (which clears all the selections) and then taps the OK button (forgetting/ignoring the message that they now have to select which menu items they want to display). Now, all items in the list are selected and the list remains on the screen.
  

• Feature to automatically upgrade linking mechanism in Quick Entry Templates was not catering to a user who had never used this useful feature. V-4.3.03 would cause an UncaughtException error when attempting that conversion.
• Title of the Template Dialog now includes both the number of displayed templates and, if some subordinate templates are hidden, the total number of templates.
  
  

• If there are no quick entry templates, the template dialog will not display, so now a long-press on the TEMPL. button in the Event Selection List dialog will import the file PimlicalTemplateExport.dat if that file exists.
• The Delete All Templates popup command in the Template Dialog now specifies that all Templates will be exported prior to their deletion (as a safety precaution).
  

• At conclusion of AutoSync or DirectSync, if the preference SyncAndroidCalendarsForDesktop is set to True, Pimlical will "prod" AOS to initiate a sync with Google calendar right away (sometimes AOS obeys this, sometimes not, but it usually helps quite significantly, even though the method used was supposedly "deprecated" by Google).
• At the conclusion of DirectSync or AutoSync, items that were synced from P/D (or server) that are now in an Android calendar that no longer exists are now ignored (the condition will be logged of course). Previously, they were inserted into the first defined Android Calendar.
• A tap on the [M] or [S] icon in the Template Dialog now displays a list of the Master Template and all its subordinates. Previously, that did nothing and could cause an UncaughtException error. There should of course only be one Master Template - if you see two or more, there are invalid links present that should be corrected!
• Restoring icons in Menu | Prefs | Restore | Reset (and in other places too) now ensures that the 'factory-default' IconArchive.dat file is copied to the Pimlical/PimlicalIcons folder if there is a subscription and that folder exists (previously it copied it to the old location in the Pimlical folder where it would be ignored if there was already an IconArchive.dat file in the Pimlical/PimlicalIcons folder).
• Ensures that the [S] icon is only displayed on subordinate events that were linked with the subscription linking mechanism (previously, it was occasionally displayed on the legacy linking mechanism).
• If all the Master and Subordinate templates present were created with the old linking mechanism (i.e. by them being in the same group), and if the user has a subscription, they will be automatically converted to use the new linking mechanism with the TemplateUID field. This is only done if there are no templates present using the new linking mechanism!
• In the internal file manager, when performing a Move or Copy operation and changing the name of the file at the same time, if there is an existing filename, the warning message was confirming the overwrite but confusingly using the original name rather than the updated name.
• Fixed issue of an Android event's modfication date getting unexpectedly updated when the database was re-read immediately after Google Calendar had assigned a new UniqueID to the event - this could obviously interfere with syncing Android events into P/D's database as if that occurred after P/D had modified the record, the P/A event would overwrite the P/D modification.
• A new [X] button appears to the right of the Repeat button in the Edit dialog when a repeat is present - when tapped, the repeat specification is removed with a single tap.
• A long press on the menu item SelectLocalCalendar now enables the creation of an empty calendar - it displays an Alert Dialog where you can enter the new name for the calendar. The internal file manager can perform many useful functions such as duplicating a calendar, deleting a calendar, but creating an empty calendar was not available previously.
  
• 
  
  

• Ensures that all local databases (calendar, contacts, memos) are both written out and updated prior to AutoSync or DirectSync.
• Avoids generating a floating advance for an old event (i.e. prior to Today or Today) - previously, there were some odd (and very rare) conditions (such as importing an iCal file, pasting in old events from another file, etc.) that could cause a raft of advances to be generated in today's schedule for events that were months/years earlier.
• Avoids an UncaughtException error from causing an iCalendar Import to fail when there was an odd problem with the designated category (such as an invalid category name etc.). Such events are now just put in Unfiled.
• AutoSync toast messages and log files now distinguish between "Syncing" and "Overwriting".
• Now displays the modification date for a contact in the Contacts View Dialog (previously that information was only displayed in Debug Mode) - to be consistent with Events and Memos which do not require debug mode in order to view that information. This facilitates trouble-shooting of synchronization issues with contacts.
• Now ensures that if a record is in an Android Calendar that an exception cannot be made to the repeat series under any conditions (there were still some obscure loopholes), and instead of denying the command completely, it now brings up the Repeat Exception Dialog with ALL as the only option and an explanation. It also properly obeys the new checkbox in the Event Selection List Dialog that controls whether exceptions are made or not (previously, the command was denied even if the checkbox stated that exceptions were not going to be made).
• In Menu | Select Local Calendar if you select a different local calendar and then hit the BACKUP button or RESTORE button (followed by the Cancel button) - Pimlical could end up with the "wrong" calendar selected. To avoid any issue, this version now forces the read of the newly selected calendar before either button is processed in order to avoid any confusion or conflict over which calendar ends up in memory.
• File backups are now only performed before DirectSync and AutoSync according to the preference: MaximumBackupFrequency (previously, they were forced on every sync).
• For spoken alarms, when a daily repeat event is snoozed past midnight, Pimlical now properly reports how much time has elapsed, previously, it reported the time to the next instance of the repeat.
• The Day+ view now is only forced to the start of the week (as defined by preference WeekViewStartOfWeek) if the number of days is set to 7 or 14 (i.e. one or two weeks) and the preference LockWeeklyViewToWeekStart was True (default setting). The description of WeekViewStartOfWeek) now clarifies this intended operation. Previously, the filter setting would apply regardless of the number of days the Day+ view was set for and was inconsistent with how the preference has always been defined.
• Menu | Undo no longer changes the prior ModifiedDate for the record to the current time.
  

• Fixes several obscure issues in both AutoSync and DirectSync related to the new features of syncing folders, and handling Android Events that were synced over to P/D and back. For example, the modificationDate field was not always being properly preserved when updating the Android Calendar database, and there was a conflict with the preference to put deleted Android Calendar items into the local calendar. Note: if you used AutoSync with Android events in V-4.3.01, start off clean by doing an overwrite to the Server and then an overwrite to all other platforms.
• Adds new Template Duplicate command to list of popup commands on the selected template in the Template Dialog.
• Avoids the creation of an unnecessary error file (complaining about deleting a lock file) on occasion when using AutoSync to a Remote Server (only occurs when using AutoSync with a Remote Server).
• The Find+ (Find in All) function will now find deleted records and display them (the normal Find function does not display deleted records). Find In All also now puts the calendar name in brackets, rather than using a row of hyphens (because that was causing the first matching entry to not be displayed) and no longer displays an asterisk for an event being in a different calendar (was just cluttering up the display and with calendar name, not needed).
• A long-press on the left-arrow button in the Icon Dialog now displays the total number of icons and the current number of icon rows used for display.
• Fixes issue with file links set in P/D not necessarily using the same Path Separator (Windows/Android File Separator discrepancy in path names vis-a-vis use of forwards and backward slashes).
• DirectSync now displays the Sync Action (synchronize/overwrite) as well as the selected DirectSyncOptions in P/D in the Progress Dialog while DirectSync is running.
  
• P/A now fixes up file path separator discrepancies between Windows and Android (forward/backward slashes) when accessing a link originally set in P/D-Windows.
• Fixes issue of syncing Android events that were newly created in P/D back to P/A, and having them sometimes appear in the wrong Android calendar.
  
• When entering a URL for a website link, if no tag is entered, Pimlical will attempt to create a useful tag automatically from the URL (if it can't, then a default tag of (No URL Tag) is provided instead. 
• When upgrading to a new release, Pimlical will attempt to refresh the Widget to avoid the wait for the next refresh interval.
• In the Note dialog, you can now use \t to enter a Tab code so tables can be nicely aligned (in particular, Google's Gboard keyboard inexplicably has no provision for generating a Tab code). The conversion of \t to a tab code and the re-alignment of text in the Note field is only displayed when entering the Edit Dialog.
  
  

• Fixes some obscure inconsistencies in the way that Android events created in P/A are handled prior to completion of syncing with Google Calendar (at which time a new permanent uniqueID is assigned). This also corrects some issues of linking an Android calendar event that has not yet been synced to Google Calendar to other events and having those links retained after the uniqueID has been changed.
• In preferences, the last section is now displayed as Pimlical System Settings rather than just System Settings to avoid confusion between those settings and the Android System Settings (handled by AOS).
• DirectSync now checks that there is a match on Major and Minor versions of Pimlical between P/A and P/D (P/D now sends that information to P/A at the start of the sync) and immediately complains if they do not match. Pimlical now checks that there is a match on both the Major and Minor versions (Step version can differ) for AutoSync.
• The existing feature of stripping out all code in angle brackets in the Note field if the tag <html>  was found, has been changed to just look for <html as there might be cases where there are extra attributes in the <html.....> tag.
  

• When creating an automatic tag for the Set Link to File feature, the file extension is now removed from the tag (incorrectly implemented in V-4.2.32).
• Updates the DirectSync client to handle copying of preferences and syncing of files in Pimlical Folders (requires V-4.3.01 of P/D for this to be fully implemented). Zero length files are never synced. Note that for P/A to send files and preferences over to P/D, you have to set up the preference: AutoSyncOptions to include those two options (P/D cannot tell P/A to do that in advance, so this was a compromise that avoided unnecessarily sending all the files in those folders to P/D when it was not needed). Update: Next version will use new preference DirectSyncOptions for this purpose to avoid confusion.
• A click on a Master or Subordinate icon in an event Selection List is now treated like the popup command Find All Linked Events and brings up all events in the same linked group in another event Selection list (previously, it just indicated how many events were present).
  
  

• When Menu | DirectSync or Menu | AutoSync is used, Pimlical now first backs up the local calendar (provides better recovery at P/A end if something goes awry in the sync). Pimlical/Desktop has always backed up the local calendar prior to syncing.
• Fixes an obscure UncaughtException error that can occur if you set an alarm on a hidden item that is a repeat, and have the preference set to enable alarm on hidden items, and when the alarm triggers, press the Edit button in the Alarm dialog and then tap the This Instance button in the Repeat Exception Dialog.
• On File Transfers via DirectSync, the Last Modified Date/Time field of the file is preserved - previously it was reset to the current date/time (not an issue until the new ability to sync files in custom folders was added - hence the change of minor version from 2 to 3, as you will get a warning if the major/minor versions don't match).
• Fixes an obscure issue in DirectSync when handling files larger than 65,535 bytes - potentially such files might not have been transferred properly.
  

• When creating an automatic tag for the Set Link to File feature, the file extension is now removed from the tag.
• When setting a link to a file and copying it to the PimlicalLinks folder, the filename in PimlicalLinks is purged of characters that can interfere with the linking/sharing mechanism (such as having a comma, etc.) - only alphanumeric characters, underscore and period (for extension) are permitted. All other characters are converted to an underscore (so .../Itinerary: London Trip.pdf would be changed to .../Itinerary_London_Trip.pdf). The tag still uses the original filename as a default tag, only changing ,| to ;/ to avoid conflicts with the link field syntax.
• The Edit button in the Manage Action Tags dialog now places each selected Action Tag on a separate line, making it easier to edit a specific tag (for example, to add a year to a Birthday tag).
• When deleting a Master Event, if the preference is set to issue a delete warning, Pimlical will display a message indicating that deleting this Master Event may leave orphaned subordinate events in the database.
  
• 
  
  

• Brings the default WorldTimeZones.txt and WorldTimeZones_All.txt files up to date to match Pimlical/Desktop. In particular, this includes the removal of DST rule for Tehran at 03:30 (which dropped DST on 9/21/2022), while still keeping the old N rule for previously-created events that might reference that rule. Also, Worldtimezones_all.txt did not have the updated DST rule changes by year for Israel.
• Fixes issue of syncing files in Pimlical folder with CloudRail/Dropbox as sync device (generated an error file complaining about a folder name ending with a file path separator (/ or \).
• If viewing a contact when debug mode is set, Pimlical now removes the Aver field (Android Contacts Version) if it's not present (it would typically only be present when importing contacts directly from the native Android Contacts Database).
• In the code that recovers from a spurious intent sent by AOS, if P/A V-4.2.31 was not waiting for an explicit intent, it continued to process the intent, EXCEPT that AOS might have sent an old P/A intent with a request for say doing a Backup Everything (which would then get processed again!). This version now allows the intent to be processed, but strips out all of the flags from the old intent, thereby avoiding any issue of seeing old flags which could not possibly be relevant (since the intent was generated by OS to launch Pimlical, not by Pimlical itself.
• Fixes a new issue that appeared in V_4.2.28 as part of the feature to synchronize Android Events to Pimlical/Desktop - under some conditions, it was causing an Exception Error when attempting to write a new item from P/D back to P/A.
  

• Implements the new preference SyncCustomPimlicalFolders which can contain a comma-separated list of custom sub-folders of the Pimlical folder that you want to sync. The default value is PimlicalLinks, PimlicalIcons, PimlicalImages, but could also include other custom folders that you create under the Pimlical folder. The folder names should also support a path, such as:
  …PimlicalImages,PimlicalSpecial/SomeFolder,PimlicalSpecial/SomeOtherFolder etc. To then sync files in those Pimlical folders, select Folders in the preference: AutoSyncOptions.
• Fixes a long-standing issue with the use of the Widget: if you create a custom preference file for the Widget, those preferences are invoked when the Widget refreshes, but, under some conditions, those preferences would not be reset when the Widget exits, leaving those preferences set when P/A next launches.
• Fixes an UncaughtException error that can occur when using Master events (i.e. events with Action Tag: MasterTemplate) that were created with earlier versions of P/A.
• When copying a local file to a Remote Server and vice versa, Pimlical now ensures that the last-modified date/time stamp on the original file is properly preserved after the copy (provided that your FTP Client software properly handles the setModificationTime() & getModificationTime() functions - some do not). Note: Windows-11 FTP Client in Windows File Manager does not preserve the last-modified date/time stamp when copying files from local filing system to a Remote Server directory.
• A long press on the Open button in the Internal File Manager with a file selected that has a .TXT extension will now launch a simple, internal file editor so the file can be edited and saved even if the file came from Scoped Storage (as other third party Editor programs can not save a file to Pimlical's Scoped Storage Area due to Android OS restrictions). A Find button in that dialog makes it easy to locate a text string (long-press the button to proceed with the search from the last find position). A Start | End+ button moves to the start (tap) or end (long-press) of the text. Use Save button to saved the text, or the Android Back button to cancel out of the dialog.
• In the main menu, menu items that support a long-press now display a + after the legend (currently, just File Manager+ and Find+). Also, a long-press on File Manager+ now includes Local, so the local filing system can be selected (useful because if you last used a Remote Server in File Manager and the Remote Server is no longer available, this provides the mechanism to reset to the use of the local Filing system).
• Extends fix in V_4.2.30 of using the Link to A Master Event button in the Edit Dialog when creating a new event (that is not yet in the database) - then changing your mind and tapping the REMOVE button (previously this caused an UncaughtException Error).
• Fixes issue of using Paste/Exit button with a tag present when creating a URL link - it should just append the clipboard contents (providing a separating comma if missing) to the tag the user entered (previously, the tag was ignored).
  
• 
  
  

• Adds support to the Contacts and Memos activities to attempt recovery when dialogs are left open with unsaved data and AOS unexpectedly destroys P/A's memory. In some/most/all(?) conditions, P/A may be able to preserve the unsaved data. As always, it's best not to leave dialogs open in an App for an extended period of time, as dealing with event clicks after the App's memory has been removed by AOS is usually problematic.
• Fixes an issue in the workaround for the AOS bug where AOS sends an old (stale) intent on a callback - previously, the callback was ignored if the sequence number (from an old intent) indicated it was obviously invalid - now it only rejects the intent if Pimlical was explicitly waiting to process a new intent - as part of this bug is that AOS was intending to launch P/A and using a stale intent that P/A itself created (as opposed to a stale intent that AOS had previously created).
  
• If the Preference: HideAllAndroidCalendars is set to True (default is false), any local categories that begin with the A_ prefix (normally reserved for Android Calendars) will be displayed in the Category Selection dialog (rather specialized use: for example, when dealing with errors in syncing using the new feature to store Android Events as local events in P/D).
• AutoSync now displays a Progress Dialog with a spinning wheel to make it clearer that an important activity is going on.
• Avoids skipping sync of preferences if calendar/tasks/memos/contacts were not updated since the last Sync - also avoids skipping sync if files in Pimlical sub-folders are being synced.
• If a repeat, daily, floating event that has the Reschedule from Checkoff Date box checked is changed to a different repeat type (Repeat Weekly, etc.), the checkbox is now automatically cleared (P/D already had the fix for that issue).
• Fixes very obscure issue if you invoke a separate activity from a main view (such as Menu | Select Calendars or Menu | View/Edit Contacts), then leave P/A, and other Apps/Activities result in AOS absconding with all of P/A's memory, then on return, the first tap to bring up the menu might be ignored (this is an apparent AOS issue - this workaround should improve the situation).
  

• The IconArchive.dat file will now be located in the .../Pimlical/PimlicalIcons folder rather than the .../Pimlical folder. This is in preparation for full folder syncing with the forthcoming preference: SyncCustomPimlicalFolders. Pimlical will also copy the file from .../Pimlical to .../Pimlical/PimlicalIcons (and will also automatically create the PimlicalIcons folder if it does not exist).
• Links to local files will now be located in the .../Pimlical/PimlicalLinks folder rather than pointing to the original file location. If the folder does not exist, it will be created, and the file will be copied to that folder. Again, this is in preparation for synchronizing custom folders so that local file links will work on all platforms. This action only takes place if the preference UseCustomFieldForSetLink is set to its default value of 5.
  
• Now allows the use of the Link to A Master Event button in the Edit Dialog when creating a new event (that is not yet in the database) - previously, this would cause an UncaughtException Error.
• The Link to Master popup command now refreshes the display so the subordinate/master icons are displayed (both main event display and Event Selection List display).
• A change was made to the way in which the Widget launches P/A to address a potential issue (on just some phones?) whereby P/A was not always launching on the first tap.
• Fixes a new issue on duplicating a repeat event in an Android calendar that the mechanism to determine when it had finally been synced to Google was invalid (needed to avoid creating an exception to a repeat series in an Android calendar before Google had assigned a new, unique permanent ID for the event.
• Fixed a potential timing issue in changing the value of a string preference where the cached preferences might not have been updated early enough to lock the value in.
  
• 
  
  

• Fix in V-4.2.29 (Restores an old behavior) caused some odd behavior, especially with the AlternateSelectionInterface pref set to True - this has now been corrected, and the Event Selection List is always popped up in either case.
• Fixes an Uncaught Exception Error that can occur if you force-stop Pimlical and then as the very first thing on launching, go into Menu | About.
• When Pimlical is reactivated by tapping on a main view, after AOS has absconded with all of memory, Pimlical will now relaunch rather than attempt to recover memory (this may be a safer strategy that avoids running into exception conditions).
• Fixes issue that due to new method of handling temporaryUID's, under some rare conditions, Pimlical was reporting that a repeat event in an Android Calendar had not yet been synced to Google (when in fact it had).
  
• Fixes obscure UncaughtException Error that could occur if AOS for some bizarre reason issues the onStop() callback after it has absconded with all of P/A's memory.
  

• Links to local files in the Pimlical Folder (or any sub-folder) are now compatible across all platforms (this will be especially convenient when DirectSync and AutoSync support the synchronization of user-created folders underneath the Pimlical folder - such as PimlicalIcons, PimlicalImages, PimlicalLinks) etc.
• If you use the Copy Command in multiple file Select mode, Pimlical now correctly issues an error message if the user fails to select a different folder (the test in V-4.2.28 was invalid and the message appeared spuriously).
• Fixes an obscure issue that might prevent the Automatic Backup Everything from running.
  
  

• Adds a new method for the Menu | GSync Now command which might improve the speeding up of Google's Android Sync Software.
• Fixes issue of creating a new event and immediately adding a new Local File Link and not displaying the newly created event until the calendar is refreshed.
• On Android 11 and later, Pimlical now uses a new API call to determine the size of the status bar - this could correct some odd alignment issues in P/A where a tap on the screen sometimes selected an item above the intended item (this would likely only be noticeable when long-pressing an item in a main view or when using the AlternateSelectionInterface Pref set to True).
• Works around the bug in AOS whereby it sometimes starts showing an unnecessary "App Bar" at the top of the screen with the legend PimlicalA.
  
• Avoids some exception error issues in redrawing the screen under low memory conditions.
• Restores an old behavior that got lost somewhere along the way: if you briefly tap on a timeslot and then tap the button to create a new event, the event should use the date/time of the timeslot that was tapped - recently, a tap there was treated as a tap on the entire timeslot (either bringing up that event, or if no event, the Event Selection List for that day).
• Avoids creating a spurious (but benign) complaint in the debug log file about a mismatch on sequence numbers when they in fact did match ok.
• 
  

• Now handles syncing of Android Calendars to Pimlical Desktop's local calendar file, so all the Android Calendars selected in P/A can be displayed in P/D. Any of those events that are modified in P/D can then be synced back to Pimlical/Android where they will update the Android Calendars (and from there, update the Google Calendars). This is a workaround for users who no longer have grandfathered credentials to access Google Calendars in P/D. This works with both AutoSync and DirectSync, and since AutoSync is quite fast to a local HD or USB key on the router, and can be invoked automatically, this actually provides a more than satisfactory solution to this long-standing issue.
• A long press on the EDIT + button in the Alarm Dialog now marks the selected item in the Alarm Dialog as Completed (quicker than invoking the Edit Dialog and having to manually change the status and exit the dialog).
  
• Fixes issue of not saving updated contents of Edit Dialog when using the Green Plus button to set an alarm at the event time (a new feature in V-4.2.27).
• Fixes issue of the Toggle Hidden command only toggling the display if there were hidden events in the current view/selection (now toggles regardless of that condition - important when switching to a different day/view).
• For Beta Testers, the Revision History displayed in Menu | About | What's New now displays the information on the current (and possibly next) Beta Preview.
• Fixes issue of the debug command to dump the differences in a filter not including the Sort Order & Direction.
• If you use the Open command in File Manager, Pimlical checks for an extension of .LOG or .ERROR and if so, copies the file using the name TEMP.TXT, so that your configured Text Editor will open the file (these are text files, but no text editor would recognize the .LOG or .ERROR file extensions - and this eliminates the extra step of using the Temp button).
• If the preference BackupEverythingFolder now specifies a path that begins with a File Path Separator (Forward slash: /), it is treated as an absolute path in the filing system. Otherwise, as previously, it is treated as a sub-path of the External Storage Directory (normally something like: /storage/emulated/0/).
• Fixes issue that when deleting multiple files with the Internal File Manager, Pimlical was not obeying the preference WarnOnDelete set to True (i.e. previously, items were just deleted without first dipslaying the warning/confirmation dialog).
• The Event Attributes popup command now properly reports the Calendar name for events in the Android Calendar database. This popup command now also allows the created log file to be renamed.
• If you use the Copy Command in multiple file Select mode, Pimlical will now issue an error message if the user fails to select a different folder (obviously makes no sense to copy files on top of themselves).
  
  

• Now avoids creating an error file when AOS spuriously sends an old/stale intent on a callback to Pimlical (it's still logged into the log file, however, as we want to know if Google fixes this bug at some point).
• Fixes an obscure issue of potentially reading an old XXX_updates.dat file (Calendar/Contacts/Memos) which might cause updated information in the sync to get lost. In theory, this would only occur if a user mistakenly copied an XXX_updates.dat file into the sync folder.
• Changes logic for warning message: Status not Normal, Alarm can not be Set from appearing when status is being changed to when user attempts to set an alarm on an item with a status other than Normal. To set an alarm on an item which does not have a Normal status, change the status first to Normal.
• Ensures that on adding or renaming a category, the category name cannot begin with one of the three special, reserved prefixes (A_, G_, T_, for Android, Google, and Tasks).
• The files generated by the Debug commands (Calendar Columns, Event Columns, Find Event, Filter Attributes, Preference Diffs) as well as the popup command Event Attributes now have a .LOG extension (previously, they had a .TXT extension). This change allows the Email Tech Support command to easily pickup those files by checking the box to include log files.
• Fixes an UncaughtException error that can occur if one of the display font preferences is unexpectedly deleted.
• Added another workaround for the AOS bug of sending the wrong intent through - this particular fix takes care of the case where P/A has sent an intent and AOS serves up an old intent, but not one that was originally created by P/A - and that should ALSO be ignored - this could potentially cause (a) a lost alarm, or (b) failure to run Backup Everything at the Floating Advance time, etc.
• Fixes issue of sometimes getting an Uncaught Exception Error when creating a new filter with the Green Plus button in the filter dialog.
• Fixes an error in the sort algorithm, when sorting items on Due Date - also potentially causing the creation of a TimSort Error file.
• Avoids generating a spurious warning message about a custom preference file on a filter when there is no custom preference file present and a filter is being updated.
• If an event is created in an Android Calendar and participates in a subordinate/master link prior to the assignment of a SyncID by Google Calendar, Pimlical now fixes those link references to point to the newly assigned SyncID.
  

• In the Edit Dialog, if no alarm is set on an event and the Green Plus button is tapped, an alarm (using the value in the preference ApptAlarmPreset or FloatAlarmPreset) will be set on the event.
• Fixes an issue that under some conditions, Restore Everything was not restoring the System Preferences at the conclusion of the Restore.
• When using the preference AlternateSelectionInterface set to True, Pimlical now ensures that popup commands always create an exception for the Delete and all Toggle commands (previously, since the checkbox to reverse that state is not displayed with that preference, it could have unexpectedly been left reversed and cause a repeat series to be subject to those popup commands).
  
  

• A brief toast message now appears with the message: Status not Normal, so alarm will not be set if you attempt to set an alarm on an event that does not have a status of Normal. Previously, the alarm setting was stripped out with no explanation.
• After the popup command in the Template Selection Dialog to Delete All Templates is used, Pimlical now just displays the brief toast message that no templates are available and returns to the Event Selection List (previously, the old templates might briefly flash onto the screen and it would return to the main view).
  

• Fixes issue with filters that under some conditions was filtering out ALL events and resulting in a blank display.
• Avoids an Uncaught Exception error if the sorting routines encounter some bizarre transivity rule violation in the sort.

• Adds a new Toggle Hidden menu command which provides a quick way of toggling the display of ALL hidden events on and off. Remember that if there are events that are potentially hidden on the current day (due to your Filter settings), you will see a tilde (~) in front of the date banner if events are currently hidden, and an asterisk (*) if hidden events are currently being displayed. When toggling back and forth, Pimlical will preserve the prior settings for Toggle Untimed and Toggle Subordinates (but only in the current session). You can also put this on the command bar so a single tap toggles the display of hidden items on and off (the icon is an Eye). On the Command Bar if Hidden items are not displaying, the button will have a red tint.
• The Toggle Subordinates and Toggle Untimed commands, when placed on the Command Bar, now have a red tint when the toggle is on (i.e. items are being hidden). The Toggle Untimed command has a new icon (looks more like a clockface).
• A new field has been added to the Edit Dialog to display (and set) the link to a Master Event. If it is not linked, the button displays: Link To A Master Event and a subordinate icon ([S]) with a slash through it is displayed in the left margin. Otherwise, the button displays [M] {Master Event Description} and the normal subordinate icon is displayed. If the button is tapped and a link already exists, a brief warning message appears (New Link will replace old Link) reminding you that this will overwrite the existing link (i.e. a subordinate event can only be linked to one master event). In either case, tapping the button brings up a sorted list of all the Master Events in the Calendar database so you can pick a Master Event to link to (similar to how the popup Command Link to Master works if there is no Master Template in the selected record(s)). There is also a Remove button which will remove the link to the Master Event.
• The Tasks View now includes a new selection button (to the right of the Multi-Select Button), which if tapped, offers four options: Master which will only display Master Tasks, Master+Sub. which displays Master Tasks and their Subordinates, ALL which displays all tasks (but not subordinate tasks), with a long-press on the ALL button displaying all tasks (including subordinate tasks). The currently displayed graphic on the button indicates which mode is currently selected (items not displayed display a gray icon with a red slash through it)
  
• The popup command list for templates now includes Internal Record Details to display the internal record details of the template.
  
• If you have the preference AlternateSelectionInterface set to True (default is false), and long-press an item directly in a view, Pimlical will now properly display the Show All button in the popup list of commands.
• A button has been added to the Alert Dialog that appears when you tap on the URL button to set a URL link for an event, labeled Paste/Exit. This appends the contents of the clipboard (which presumably contains a URL, copied say from your web browser address) and also inserts a comma if the current contents of the Edit Field does not end with a comma. So after typing in a Tag for the URL, tapping this button appends a comma and the contents of the clipboard. If no tag was entered, Pimlical will use best efforts to create a meaningful tag from the URL (usually the domain name).
• Fixes an issue on the Delete Command not recognizing that the checkbox in the Event Selection List for handling exceptions to repeat series (for Delete and Toggle Commands) was not checked. The deletion messages were also updated to be more informative.
  
• 
  

• Using the new Sequence# feature to trap Spurious Android OS callbacks, Pimlical now logs an error file and ignores the callback completely if the sequence number is earlier than the current sequence number (indicating it was an intent that had already been submitted in the past). This helps in avoiding missed alarms or other odd behavior in P/A.
• Fixes issue that tapping the Hide/Show Latch in the Tasks View was also clearing the Tasks View.
• Avoids creating an error file (complaining about being unable to determine the UTC Timezone) when it's only an issue of not being able to properly adjust the date/time in the log file.
• Several subtle changes have been made to the Sort Ordering in Filters. In particular, the meaning of Ascending and Descending has been changed so that Ascending now refers to the most likely or "natural" ordering of the item. In particular, the ordering for Urgency and Priority has been reversed from its prior setting (which was confusing users anyway as everyone was having to set a Descending Sort in order to get the "natural" ordering from high to low). With sort criteria that cater to null or empty values (such as No Urgency, No Priority, No Location, No GroupKey etc.), items that have a null or empty value will sort last regardless of whether the sort is set to Ascending or Descending (on the grounds that if that sort is relevant, then items that have that attribute are by definition more interesting and should sort first).
• When invoking the Tasks View - Pimlical now checks to see if the Tasks View has a Custom Preference File attached, and if so, will read the preference file prior to the first display of the Tasks View (this permits customization of the Tasks View which is a standard Event Selection List).
• The debug commands that write out a file ( Calendar Columns, Event Columns, Find Event, Filter Attributes, Preference Diffs) now display the filename in an editable field so you can update the filename with an additional annotation (such as before_update, after_update, etc.) when you tap the OK button.
• Avoids a very rare (but completely benign) UncaughtException Error that could occur if the Alarm Dialog was dismissed by the user within a few milliseconds of the end of a spoken alarm.
• If the Tasks Display was completely empty, a grayed-out dialog appeared stating there were no tasks to display (which also caused a spurious error file to be generated) - now it just displays a brief Toast Message, noting the list is empty.
• Fixes some obscure problems related to the use of custom preference files with filter when an alarm or the floating advance triggers (since it's important that the Default filter be in effect when those events are being processed (previously, some updates to the custom preference files could be lost).
  

• Adds a View button to the dialog that displays the number of Subordinate links for an item, which displays the description field and date/time of the linked events including identifying the Master and Subordinate events.
• Adds a new Show All button in the selection list of popup commands (single or multi-select) that displays all the popup commands in Pimlical (not just those that were selected in the preferences: PopupListCommandsForEvent and PopupListCommandsForMultiSelect). This makes it easier to prune those two lists to a smaller size as very rarely used commands are still accessible without having to fiddle with preference settings to display them).
• The Link to Master command now displays an error message if there are less than two selected events.
• A long press on a template in the Template Dialog now includes a new command: Link to Master Template. This displays a list of all the Master templates so you can set (or add) a link to the Master Template you select. If you need to add a good number of subordinate templates to an existing Master, it's probably better to insert the Master as an event, select all the events you want to link to the master, and then use Save as Template to save all of them.
• Avoids some confusion over the identification of Subordinate Templates by only using the new, subscription method (linking to the UniqueID of the Master Template) if a subscription is present, and only using the old non-subscription method (Item is in the same group as used in a Master Template) when a subscription is not present.
• A click on the Master or Subordinate Icon in the Template Dialog, now just counts subordinate templates, whereas a click on the Master Or Subordinate Icon in an Event Selection List now counts subordinate events in the entire database. The UnLink button is only displayed when clicking on a Master or Subordinate Icon in an event Selection List.
• If a subscription is present, Pimlical now scans all the templates to see if there are Master/subordinate templates present in the old format (using the Group Key field to associate items). If so, it converts them to the new format, where subordinate templates have a link (via TemplateUID field) to the Master Template (which is also updated with its own uniqueID). Note that events in the database are not updated. If you need to update them, use popup command Find all Items in Group to locate Master and Subordinate events and then Link to Master. However, if you had inserted the same Master/subordinate templates several times, the Link to Master command will complain because there should be only one Master Event present in the group being linked (and in this case, you would have several copies of the Master Event in the selection list. In that case, you would have to manually select the items to be linked to each instance of that Master Event (this ambiguity is one of many reasons for changing the link format!).
  
• 
  

• Restores the feature of linking to a contact in the Android Contacts database (only used if there is no local contacts Database) which was broken by a new bug in Google's Android OS (this may have been broken for some time? It was only just recently reported). Still investigating if the required change causes some other display anomalies in P/A.
• The Save As Template popup command, when issued on multiple events, no longer complains if there is no master template present (it just adds them all as individual templates), and only complains if there are two or more Master Events present, as if there is one Master event, all the other events are linked as subordinate templates.
• The popup Delete command now always displays a confirmation dialog if there are two or more events to delete (previously, that confirmation dialog was only displayed if the preference WarnOnDelete was set to true).
• The popup command Delete All Templates in the Template Selection Dialog now first exports all templates to the file: PimlicalTemplateExport.dat to simplify recovery.
• Avoids displaying the note icon in main views and event selection list if the note field contains nothing but one or more spaces.
  

• In the Event Selection List display, there is now a new checkbox: [X] Make Exceptions for Delete & Toggle Commands which by default, generally preserves the current behavior of Popup Commands (as of V-3.2.07 that forced exceptions to be made on most popup commands, regardless of whether or not there was a reference date). If cleared, though, those popup commands, which support making exceptions, when applied to a repeat event will apply to the entire repeat series and not make an exception. This would be useful when, for example, moving a block of events, which included a repeat event and exceptions to it, to a different day. Exceptions for repeat events are only available for Delete and Toggle Commands (Toggle of status, type, alarm). Note that from this point forwards, exceptions are no longer made to repeat events for commands which change the time or date - such as Advance 1 Day, Shift Times Forwards/Backwards, etc. Update: In V-2.03.06, the Advance commands are now included for making exceptions via the Make Exceptions.... checkbox.
• The handling of Master and Subordinate templates has been substantially enhanced by remembering the Master/Subordinate relationship on the inserted events (which now display the Master or Subordinate icon). Subordinate templates are now linked to the Master template by sharing the same unique Template ID (this internal field is only displayed in the popup command: Internal Record Details). This linked relationship is also propagated to the events created from this template, thus providing a mechanism to link multiple events to a single master event.
• A new popup command Find Linked Events issued on a master or subordinate event will then present a list of the Master and all subordinate events (at which point they can all be deleted, shifted to a different date/time, etc.). In that list, the Master event is clearly marked by the Master Event Icon [M] and subordinates by the Subordinate Event Icon [S].
• A new popup command: Link To Master can now be issued to link multiple events to a Master event. When this popup command is used, the list of selected events (in an Event Selection List) should include one and only one event which has the ActionTag: MasterTemplate. All other events in the selected list are then linked to that Master Event. This can be especially useful in setting up a Task with subordinate tasks, or for just associating a group of events with each other. The old method of locating subordinate templates for inclusion by noting they were in the same Group has been maintained for backwards compatibility, but going forwards this new mechanism should be used. It is no longer necessary to require that master/subordinate events be assigned to any group.
• The Save as Template popup command can now be used in multi-select mode to add multiple events as templates in one step. Typically, this would be used after the Link to Master command had selected a Master event and its subordinates all of which are now to be used as a template.
  
• Adds a new menu Command: Toggle Subordinates (which can also be put on a command bar button) which toggles the display of subordinate events on and off when tapped. The icon for the command bar is the Subordinate Icon with a Red X through it.
• Tapping on the Master Icon in an event Selection List also displays an UnLink button that will unlink the Master Event and all the Subordinate Events in the database from the Master Event.
  
• Fixes an obscure issue that under certain conditions might cause Backup Everything to run twice on the same day.
• 
  

• Restores the Show All Repeat Instances popup command (fix for bug in AOS3/4 now interferes and has been removed as AOS 3/4 no longer used).
• The prior popup commands in the Template Dialog to show all or hide subordinate templates have been replaced with a checkbox in the Template Dialog itself (since it made little sense to have to select a template to invoke a command that affects all templates).
  
• Changing the status of a repeat series to Normal is now consistent with changing it to any other status type (an exception is made to the repeat series - previously for some odd reason, changing the status to Normal always applied to the entire repeat series). Undeleting a repeat event with a status other than Normal, however, resets the status of the series to Normal without creating an exception.
• The list of templates is now sorted so that regular templates always precede linked templates and linked templates are sorted together with the Master Template always preceding the linked, subordinate templates.
• Another tweak to work around the issue of AOS (Samsung's version only?) erroneously calling onStop() prematurely in the Alarm Receiver, which under some conditions would cause all Alarms to be immediately autosnoozed after Alarm Dialog appears.
• If Toggle Untimed menu command is put on the command bar, an appropriate icon (a clock face with a big Red X through it) is used instead of the Text Tu.
• Fixes issue in Tasks Display that using the Cancel button in the Edit Dialog does not properly return to the Tasks View.
  

• Adds new popup command: Set Link To URL. This command brings up a dialog into which you can enter the optional Tag and comma and then the full URL to use to access a web Page (or set an Email Address).
• Adds new popup command: Edit Link Field. This command allows you to directly edit the full contents of the hidden Link field in the database. Use caution with this command as if you inadvertently introduce/delete commas or vertical bar separators, the link field may be corrupted. Useful if you manually edited a long URL, but made a typo and need to fix it.
  
• A long press on the link icon in an event Selection List now always brings up the list of links even if there is only just one link (normally, a tap on a single link invokes the link immediately. This feature allows you to access the link and edit it or remove it when only one link is present).
  
• Default setting for preference: RestoreFBGrndAfterAlarm has now been changed to True from False.
• The preference: RestoreFBGrndAfterAlarm was interfering with the recent fix for the Edit button not always working in the Alarm Dialog - this has been corrected.
• If you set the preference BackupEverythingAfterFloatAdvance Pimlical will only perform the backup at the end of the nightly advance (determined by preference AdvanceFloatingEventsTime). This avoids the problem of P/A interfering, when proceeding with the Backup Everything, if you are using the device after midnight but before the Advance Time.
• Another fix for a very obscure issue whereby the BackupEverything might get triggered at the end of the Floating Advance, but then fail to proceed to successful completion.
  
• 
  
  

• Ensures that the tags used in the new linking mechanism do not contain a comma or vertical bar (|) as those would interfere with the linking mechanism (commas are changed to semi-colons and vertical bars are changed to a forward slash).
• Avoids an Uncaught Exception Error when creating a new filter, and the sort parameters have never been initialized.
• Avoids an Uncaught Exception Error that has occurred on very rare occasions in the List View for reasons that remain unknown (but are possibly related to the erroneous reporting of timezones on the device).
  
• ScheduleIn Action Tag no longer pops up a dialog to enter a value if you use '0' or '0s' as the duration (leave it completely blank to popup the dialog). You would use a value of '0' to enter the event at the current time.
  

• Adds new Preference: BackupEverythingFolder that allows you to specify what folder (or Folder Path) to use for Date/time Stamped Backup Everything - default value is the previously hard-wired value of PimlicalBackups. This is taken to be a path off the root of the Android Filing System (or the Remote Server path attribute if using a Remote Server).
• When BackupEverything fails to run because the system is active (typically, the user was using Pimlical right at the AdvanceFloatingEventsTime), Pimlical now keeps on checking to try and run it when the system becomes inactive - previously, under those conditions, the BackupEverything failed and did not occur again until the next scheduled day.
• Adds new Preference: RestoreFBGrndAfterAlarm which if set to True (default is false to maintain prior behavior) will return Pimlical to the background if it was already in the background when the alarm triggered. This is similar to the behavior invoked if you set the preference to use the Volume up/down buttons to dismiss an alarm. So if the full-page alarm dialog appears over some other App, when you tap DONE or Snooze and dismiss the dialog, you return to that other App rather than having Pimlical brought to the foreground. Note: due to an AOS bug, if you immediately look at your App list, you'll see that AOS gets confused about what to display as the miniature page for Pimlical as it typically shows that other App Screen as P/A has already pushed itself into the background, but this is just a cosmetic issue.
• The contents of the Past Alarms dialog is now displayed in a special field so that Copy (to clipboard) can be used. This now also applies to tapping the NOTE icon in an Event Selection List.
• When using the feature to set a date range for generating exceptions to a repeat series, P/A now checks that the ending date for the exception period does not precede the starting date, and issues an appropriate error message.
• A long press on either the Create Link+ button in the Edit dialog, or the New+ button in the Link Selection Dialog now brings up selection dialog to choose either to set a link to a memo, a file or a Web page. This is far more convenient than using the Set Link To File popup command, when the event is already being displayed in the Edit Dialog. When setting a link to a URL, you can precede the full Url with an easily understandable user tag and a comma (say Pimlico,https://www.pimlicosoftware.com) - and that user tag is displayed in selection lists, and in the description of the event.
• The preference: IncludeContactLink now applies to all four types of links, and for memos, only the memo title is displayed, for a local file, only the filename itself is displayed, and for a Url, the user-tag (if present) is displayed instead of the full Url.
• The Set Link to File command can now store the link in the internal (and normally hidden) Link field in the database (as are the links for contacts and memos) - this is accomplished by setting the preference UseCustomFieldForSetLink to a value of 5. And linking to a local file can now be accomplished directly from the Edit Dialog (see below).
• Setting a link to a web page or local file is now consistent with setting other links (the link is placed in the normally hidden Link field in the database (as are all other links) - just long press Create Link+ button (or New+ button in Link Selection dialog) and either select the Memo, navigate to the local file, or enter the full URL to a web page (most likely copied to clipboard from web browser address field). You can enter an optional Tag (i.e. an arbitrary name you pick) and a comma first for the links to a local file or URL, so that when the link is displayed you know what the link is for (rather than a long, inscrutable path). The old method of inserting the link into a text field or custom field is still supported for backwards compatibility. When you click on the Links field in the Edit dialog, you can now see all four link types for the event ([C]ontact, [M]emo, Local [F]ile, or [U]rl) and can select them for removal or display. The Edit Links button now includes the number of links present for the event. Note that the normally hidden contents of the Link field for an event can be displayed by using the popup command: Internal Record Details.
  
• A new Debug Command (Change Category) allows user to change a category name regardless of whether it was previously in use or not. Any reference to that category (in events, templates, filters, preferences) is switched to the new Category Name. The default value for the new Category is Unfiled. This can be useful in removing an old, but now unused category name from, for example, filters that explicitly reference that category. It's also a quick way of moving all events in one category to another category (or to just rename that category).
• When linking to a contact and the uniqueID for the contact has changed (after import/export from another contact database), Pimlical attempts to locate the original contact by name, but there was a flaw that this only worked if the contact link was the first link in the potentially larger list of links for that event.
• Fixes a flaw in Backup Everything whereby the Backup might get interrupted and fail to complete properly due to the use of a shared thread that could potentially cause an access conflict.
  

• Fixes cosmetic issue in Error File created if user has incorrectly edited the preference ContactPhoneLabelOrder so it has the wrong number of lables (should be 8), whereby it reports the same value (rather than showing the expected and found values).
• Fixes issue of not reporting in log file that the Backup Everything did not take place because the main thread was currently writing the local calendar file.
• Addresses obscure issue of having Preference Section Selection Dialog open, having AOS abscond with all of Pimlical's memory (due to memory needs of other Apps run in the interim), followed by an alarm triggering.
• Fixes new issue in V-4.2.20 of the EDIT button in the Alarm Dialog not bringing up the Edit Dialog if Pimlical was not in the foreground when the alarm triggered.
• The preference: ShowTasksInSeparateView had been commented out in the preference file some time ago, but this is an active preference item. The default is false, but if set to True, tasks are never displayed in a main view (and this overrides the settings of any filter that may be attempting to display Tasks in a main view).
• When right-clicking the Find+ button in Advanced Find, all events in the Display Results dialog are now selected (previously, everything was unselected).
• Adds seven new fonts for display (Goudy Stout, Matura, Old English, Script bold, Sue, Vladimir and Gorilla).
• When handling a duration value for preferences, the Seconds column is now displayed (so you can, for example, set a value for the SecondsToAutoSnooze preference to say 30s).
• Removes the dubious "feature" of suppressing the Calendar line in the Edit Dialog if only one calendar was present - it's still helpful to see the name of that one Android Calendar displayed...
• When using the Find Function, the list of available categories now includes Task Categories (previously, they were inadvertently omitted).
• Another attempt at a workaround for the problem of losing an alarm if AOS calls onStop() (which kills the auto-snooze timer), whilst still catering to the bug in some Samsung phones (just AOS-12?) whereby onStop() is called spuriously just milliseconds after an alarm has triggered.
• A correction was made to the Worldtimezones.txt file to accomodate the rule that all entries at the same DST offset (i.e. like -07:00) with DST rules must precede the final entry which does not have a DST rule. If you have not customized timezones, you can just go into menu | Preferences | Restore | reset and check the two boxes for TimeZones and All TimeZones. If you have customized the Worldtimezones.txt file, just scan it to ensure everything follows that rule above.
• The popup command for Internal Record Details now presents the information in a Text Field that you can select text and Copy from (useful, for example, to copy information from hidden fields, like the Link field).
  

• Adds a new Temp button to the File Manager which forces the new filename to Temp.txt. This is convenient for looking at a Text file with Open that does not have a TXT extension (such as log files, error files, etc.).
• Adds new preference: UseMoreCompactListDialogs (default is false), which, if set to True uses a more compact list dialog (where the height of each row is about 3/4 the normally used height), in certain list displays in Pimlical (most dialogs that do not display graphics /colors).
• Adds new preference: UseDialogFontInListDialogs which uses the DialogFont (previously unused) to control the font for the display of text in supported list dialogs.
• Ensures that if Backup Everything fails for some unexplained reason (AOS terminated the App, etc.) that the status of the last Backup Everything is always marked as having failed.
• On dismissing an alarm with the volume button (Preference: UseVolumeButtonsForAlarms), if the alarm triggered while some other App was in the foreground, Pimlical is now moved into the background so that the prior App appears on the screen. Previously, Pimlical would always be in the foreground when an alarm was dismissed. This is convenient using say Google Maps while driving and a full-page alarm triggers - a tap on the volume button dismisses the alarm and returns Google Maps to the foreground.

• Replaces the Alert dialog that displays all matching entries in the Find In All function with the Pimlical list dialog style which is visually more desirable and which, with a subscription, has preferences to control the display.
• Avoids an UncaughtExceptionError when restoring the File Manager dialog after AOS has removed P/A's memory.
• Fixes issue of having preference EditDialogQuickReturn set to False and using popup command Set Meeting Status or Set Meeting Role, and having the next tap on an item in the event selection list ignored (there's a hack to work around a long-standing AOS bug, but there are occasions where the hack has to be suppressed).
• Changes the informative message: Exiting Dialog since Database needs to be refreshed... from a brief toast message to a log in the debug log (if enabled), as too many users were concerned this was some errror message indicating something was wrong.
• When using the irregular repeat feature, Pimlical now verifies that the exception date is on or before the start date of the event and on or earlier than the Repeat End Date (if there is an explicit Repeat End Date) and displays an appropriate error message if the date is out of range.
• At the conclusion of the Floating Advance, if Pimlical was in the background when the advance took place, Pimlical is now returned to the background (previously it stayed in the foreground).
• Avoids an Exception Error caused by Android OS deficiency in limiting saved bundles to apprx 0.75Mb - P/A no longer attempts to save contact photos larger than 250k.
• Now checks to see if the preference: ContactPhoneLabelOrder has incorrectly edited by the user and left with an invalid value (it must have precisely eight entries), and resets it to the default preference value. An error file is also generated.

• Fixes issue in handling ListOfStrings preference type (RemoteServerList preference). When there was only one string present (i.e. after deleting all but one item, or with long-press on InternalFileManager option), it would split the string on a comma rather than a vertical bar, puzzlingly displaying 6 items in the list, when in fact there should have been just one item separated by commas.
• Removes a secondary parameter when setting the Binary File Type for Remote Server which in theory was always redundant, but which apparently caused grief with one of the FTP Servers that one user had because it didn't handle the second parameter on the setFileType() command.
  

• Fixes alignment issue in Exceptions Dialog where legend Remove All appears on two lines (on older/low-rez phones).
• Ensures that the new Exceptions panel in the Repeat Dialog is hidden when the Repeat Type is set to Repeat None.

• Should cater to users of older/low-rez phones in Exceptions Dialog where legend Remove All might get truncated.

• Cleans up a long-standing inconsistency in AutoSync at the conclusion of the sync when the preference: DisplaySyncLog is set to True. There are now TWO files created by the sync: PimlicalAutoSync.log which always has a brief record of all the prior syncs that have taken place, and is copied back to the Server with the new date/time, and PimlicalAutoSyncCurrent.log which now contains the results of the most recent sync and only appears locally in the Pimlical Folder. In Debug mode, the filename for the latter file appears as PimlicalAutoSyncCurrentXXXXX.log, where XXXXX is a date/time stamp, so those records can be maintained separately.
• Fixes issue of not remembering the last folder in the Internal File Manager when the Done/Multi-Select+ button is long-pressed.
  

• Adds a new menu item: Find In All that will search all local calendars for a particular string of text. This function can also be invoked with a long press on the Find button (if Find is on the command bar) or with a long-press on the Find function in the menu display. It brings up the same dialog as the regular Find function, except that instead of searching the current local calendar and any selected Android calendars, it searches all the local calendars (meaning any file with the extension .DAT in the .../Pimlical/PimlicalCalendars folder. Find In All displays a list of the matches sorted first by local calendar name, and then by start date of each event. The start of each local calendar is demarked by a line of hyphens and the name of the local calendar. The most relevant attributes of each event are displayed along with the letters <F,T> for F-loat, T-ask, and <CXDA> for C-ompleted, X-canceled, D-eferred and A-bsent, and <R> for a repeat item) if not normal status and an appointment. An asterisk (*) follows if the event is in a local calendar different from the one displayed when the command was invoked. Tapping on an item in the list will display a dialog showing the local calendar name (in the title) and the event status icon (if not Normal), the full event start date/time, the description, note, location, repeat type (if a repeat) and due date (for floats/tasks). This dialog displays a Copy button which will copy the selected event from some OTHER local calendar into the currently selected Local Calendar (this button is only displayed if the selected item is in a different local calendar from the currently selected local calendar). A GoTo button will go to the day of the selected event in that local calendar in the Day View if more context is needed (Caution: remember that P/A is now displaying a different local calendar, just as if Menu | Select Local Calendar had been invoked to change it! The widget is also forced to refresh, noting the calendar change). The availability of this function should encourage users to archive old events to keep their local calendar smaller as old events can now be viewed and referred to quickly.
• Adds a Remove All button to the Repeat Exceptions Dialog to allow all exceptions to be removed with one tap.
• Now sorts all the exception dates to a repeat series in ascending chronological order.
• Adds buttons to the Repeat Dialog to allow you to make exceptions to a block of instance dates by setting a start date and end date for the range of exceptions. All instances of the repeat that lie between (and including) the start and end date will be marked as exceptions.
• Fixes issue of not properly handling the RemoteServerList preference when only one remote server was defined.

• Avoids creating the spurious error file complaining about a read error on the calendar database when the Automated Backup Everything is running for the first time on the day.
• Provides a few better diagnostic messages for syntax errors that the user created in some preference settings..
• Strips off the meeting information on advance reminders (to avoid the advance reminder itself triggering emails when it gets created and subsequently advanced).
• When removing or adding images to an event, the Edit Dialog name/path fields are now properly updated.
• Updated the online manual for Action Tags to include the better, alternate, method of handling the FloatDays action tag, plus several recently added Action Tags.
• Fixes an inconsistency in the use of log file names - AutoSync was sometimes creating a file under the DirectSync filename (i.e. PimlicalLocalSync.log instead of PimlicalAutoSync.log).
• Provides workaround for odd AOS issue of reactivating the wrong activity at the conclusion of an alarm.
• Long Press on the Green Plus command bar button (Create Appt) now creates a Floating Event (previously, it brought up the Event Selection List, but this is no longer necessary as you can always tap a timeslot, etc.). Also, long press on the Command Bar button that creates a Floating Event now creates a Task.
• When entering the Find dialog for the first time, if all categories are selected, the legend on the Category Selection button displays (All) rather than listing every single category explicitly.
• Changes legend in Repeat Exceptions Dialog from Delete to Remove to avoid any confusion over terminology.
• Fixes issue of a time-change notification from Android OS potentially triggering an early notification for the upcoming alarm (especially important with Samsung AOS in fringe reception areas, which generates constant time-change notifications even when time is not changing).
  

• For the Automated Backup Everything, P/A no longer requires that all dialogs be closed (previously, it would avoid the process if any dialogs were open).
• When launching the contacts or memos activities from the Widget, P/A no longer forces a re-read of the calendar when Pimlical is next invoked.
  

• If AOS is terminating P/A while it's reading the calendar, P/A now just logs that to the Debug Log rather than creating an error file (since there is no need for any recovery).
• Fixes thread error in displaying the accumulated size of all selected files in the File Manager dialog when handling multiple files on a remote server.
• Fixes errors in moving or copying multiple files when a remote server was involved (either as source or destination of the move).
• If the File Manager dialog is left open for quite some time, P/A will now automatically logoff and log back into the FTP server if the FTP server disconnects due to timeout.
  

• When an alarm goes off that is not acknowledged and all autosnoozes have taken place, Pimlical no longer finishes the task if it was originally in the background when the alarm triggered. This should avoid an unnecessary re-read on the calendar when P/A is next invoked.
  

• Adds multi-file select capability to the Internal File Manager so that multiple files (in just one directory) can be moved, copied or deleted in a single operation. To toggle between single-select and multi-select modes, long-press the Done/MultiSelect+ button. In multi-select mode, the Done button invokes the File Manager Dialog to perform the file operation on multiple files (use Back Button if you need to exit that dialog without invoking any file operation). Also, in multi-select mode, there is now a button that will Unselect All items, or, on a long-press, Select All+ items. When multiple items are selected, the File Manager Dialog displays the total number of selected files and the sum of all the individual file sizes.
• A long press on a day in the Pimlical Date Picker now also includes the number of days from Today's date (negative if before today, positive if after Today) in addition to displaying the Week Number and Day of Year number. For example, when looking at an event in the past, in the Edit dialog, tap on the Start/Date Time and then long-press the Day highlighted in blue (which will be the event start date) to see how many days in the past that event took place.
• Adds two, new popup commands: Set Meeting Status and Set Meeting Role which allow you to set the meeting status and/or role of every participant in the meeting of the selected event (except for the Chair/Organizer whose status and role always remains unchanged).
• 
  

• Removes the somewhat redundant preference: BackupEverythingUsesRemoteServer. If the preference BackupEverythingRemoteServer is a blank string (default value), then backup is to local device. Otherwise, it species the name of the remote server and an optional timeout (as before).
• When creating new floating events or reminders from the overnight advance of floating events, Pimlical now sets the modification date/time to the earlier of (a) 00:00:00 on todays' date, UTC, or (b) the last Sync Date/time. This avoids any possibility of the sync routines thinking that there's a genuine conflict if the preference LatestUpdateAlwaysPrevails is set to False. That way if the modification date/times are later than that of the last sync, it would be because of user interactions and not Pimlical auto-updating the date/time. Note that this could result in "bogus" modification date/times since they might well precede the actual creation of the event.
• Fixes a potential conflict in the onStop() callback which was not checking to see if there was a major file operation in progress (which there would be if BackupEverything was triggered from the floating advance).
• Fixes a very remote timing window whereby P/A could attempt to reschedule alarms AFTER an alarm had triggered, but either BEFORE the alarm dialog was fully displaying or because the AlarmDialog display was terminated by AOS (which called the onDestroy() callback to destroy the task). The symptom was triggering a subsequent alarm in the future at the auto-snooze interval instead of re-displaying the current, auto-snoozed alarm.
• Fixes another obscure issue where after a Backup Everything to a remote server triggered off the floating advance could result in a blank screen when Pimlical was first launched on the day.
• Fixes an obscure Exception Error (which should be benign) when using notifications for alarms, and an alarm triggers after AOS has absconded with all of P/A's memory.
• Adds a new Popup Command: Event Attributes which creates a text file with all the event's relevant attributes (useful to send to Tech Support instead of screenshots of Edit Dialog, and much more informative). Command is in both PopupListCommandsForEvent and PopupListCommandsForMultiSelect so it can be used to dump out the attributes of a group of events in multi-select mode.
• Pimlical now automatically forces the display of new Popup Commands (such as the one above) when installing the new version that first presents them, so it's no longer necessary to manually edit the preferences to include the new popup commands (provided that version was not skipped). The new popup commands are always added to the bottom of the existing list without disturbing the possibly custom order and display of the existing popup commands.
• Now sets the Meeting Organizer and Meeting Email Fields from the Chair (for compatibility with P/D).
• Works around an obscure issue - if you rotate the screen while P/A is reading the local calendar database and there are some pending updates that have been stored in the Updates file, P/A could end up truncating the local calendar file at the time the screen was rotated. However, this would only occur because of a bug in AOS - under no conditions should AOS be terminating P/A as P/A indicates that it will handle all screen orientation changes itself! With this fix in P/A though, that AOS bug should no longer result in the potential corruption of the local calendar.
• Meeting participant list is now top-aligned in the Meeting Dialog (previously, it was bottom-aligned), and now also scrolls properly in the region below the Chair Info and the bottom line buttons.
• (Internal change: Used Sync_Status_Bit in InternalField5 to avoid potential conflict with other uses).
  

• Fixes a new issue in V-4.2.10 that after a floating advance, under some conditions, Pimlical would end up with a blank screen and the widget would no longer refresh because a flag did not get reset properly after an Exception error - this also fixes the benign exception error as well. Also ensures that menu | Exit clears that particular flag.
  

• When removing the last attendee of a meeting, PA was displaying an empty Meeting list and also generating some unnecessary error files, and could also cause PA to terminate. PA now correctly returns to the Edit Dialog if the last participant is removed from the Meeting.
• Fixes a timezone issue on untimed events that could under some conditions appear on the wrong (earlier) day but only when the event was East of GMT.
  
• Avoids potentially generating a spurious error file at the conclusion of BackupEverything when triggered off the end of the "2am" Floating Advance.
• The logic for removing deleted records on the Floating Advance has now been modified to use the latest of (a) the Modification Date, (b) the Appointment End Date, and (c) the Due Date (if a Floating event). Previously, only the Modification Date was used to compare to the cutoff date as specified in the preference: DaysToKeepDeletedRecords. Also, when a deleted record is removed, this is logged into the audit trail file along with the date (and whether (a), (b) or (c) above) used for that determination.
• Reverts the handling of Wake Locks for the Floating Advance, as either (a) AOS has a bug, or (b) their documentation is backwards :(. Apparently, starting with V-4.2.08, the Floating Advance was causing the phone to power on the display at the Float Advance Time.
• Fixed spurious SUCCESS message at the end of BackupEverything when performed silently and the operation actually failed.
• Ensures that if P/A is force-stopped or if a program update is installed, that the Floating Alarm does not get lost (there were cases where the next alarm could get skipped).
• Fixes issues with getting Backup Everything to work at the end of the 2am (or designated time) Floating Advance. Turns out to be an undocumented bug (or intended action?!)  in AOS: a sub-thread spawned off the thread of a Broadcast Receiver (even with a WakeLock held) has its network connection terminated by AOS after a short period (seems to be the Display Time out??). P/A works around this by  now spawning the thread off the main thread - and that apparently works!
  

• Avoids generating a spurious, benign complaint about logging into a Remote Server when using menu | Internal File Manager and no remote file servers have ever been setup.
• Avoids an obscure issue in trying to catch alarms missed by AOS (although it's not clear that there would be any consequence of the code the way it was in prior versions).
• Removes new change in V-4.2.08 which was causing alarms to be auto-snoozed if AOS callback onStop() was called. Appears that Samsung phones spuriously generate that callback even though P/A remains in the foreground. In any event, it seems more useful to leave the Alarm Dialog displayed if the Home or Back buttons are pressed (User wants to finish what they were doing, then return to Alarm Dialog, etc.) rather than trying to 'fix' the issue of just leaving the Alarm Dialog open after the switch with no further alarm sounds.
• The first Alarm button displayed in the Edit Dialog now displays an Alarm icon with a red X if no alarm is set, or the regular alarm icon.
  

• NOTE: you will need to edit the RemoteServerList preference to re-enter your password (the sixth attribute of each entry in that preference) as the password field is now scrambled in all cases, except when the Edit button is used to edit one of the server list attributes. It will display as scrambled characters because V-4.2.08 now assumes it was scrambled in the Default.txt file (previously it was not). This just avoids having a password in plaintext in the default.txt preference file.
• When including the copying of preferences in AutoSync, P/A now includes the number of preference/system files copied in the concluding sync dialog.
• The Internal File Manager now displays + after button legends Copy, Rename, Delete and Move to show that a long-press skips the normal notification message that appears.
• Works around bug in Netgear router (and possibly others?) of not providing proper file size in the internal file manager's file attribute dialog by implementing an alternate method to get the filesize.
• A long-press on the Start Time or Start Date in the Edit dialog now unlocks the End Time/End Date before allowing a change to be made, meaning that if you long-press the start time and change the time, the end time will remain unchanged, and the same applies to a long-press on the Start Date field (End date will not be adjusted). A lock or unlock icon appears below the legend End+ to indicate whether or not the date/time fields are locked (normally a lock icon is displayed). You can tap that icon to toggle the lock condition for the start/end date/time.
• At the conclusion of an automated Backup Everything, you can now long-press the right-arrow button on the command bar to return to whatever date was previously being displayed (if your filter was not set to  preserve the current date).
• If the password for the Remote Server is incorrect, an error message and error file are generated
  
• Now prevents the Widget from triggering a Backup Everything (can be an issue if triggering the backup at the end of the Floating advance).
• The password in the RemoteServerList preference is now scrambled (previously it was displayed in ClearText). It is now only displayed in ClearText when you tap EDIT on the selected remote server  to edit it.
• Fixes a timeout issue on some routers when retrieving a file from a remote server.
• Fixes an issue on the Widget refresh whereby if the Android OS made a spurious call to invoke the widget, subsequent, legitimate refreshes could get missed.
• Adds preference: BackupEverythingRemoteServer which allows you to specify a particular Remote Server in the RemoteServerList preference (just set to the name of the server (first attribute in the list) - default is blank - meaning just use whatever Remote Server is in the top position in the RemoteServerList Preference). The server name can be optionally followed by a duration value for the Floating Advance Wakelock timeout. This may be necessary if you set the preference: BackupEverythingRemoteServer to true, and you are getting errors on the backup because AOS is releasing the wakelock prematurely. The default value for the wake lock is 10m - so consider increasing this to say 1h or 2h, especially if the backup is taking a lot of time (you can look in the PimlicalDebugInfo.log file which will log the completion of the Backup Everything command to see how long it was taking).
• RemoteServerList preference now trims off leading and trailing spaces for the six attributes in the list.
• When long-pressing the Hyperlink button in the Edit Dialog, the Remove button now caters to a link with leading and trailing spaces and removes them (possible if link was manually inserted by user).
• A long press on the menu item: File Manager now brings up a selection list where you can select one of several Remote Servers (as defined in the preference: RemoteServerList),
• Backup Everything to a remote server now preserves the original modification date of the file (previously, the file's modification date was set to the current date/time).
  

• If a user attempts to convert a former exception of a repeat series into a new repeat series, P/A now prevents the user from doing that since Google Calendar can not handle it and corrupts the event) - previously, it just issued a warning message.
• If the preference UseGoogleCalendarColors is set to True, Pimlical now displays an informative message as to why the background color is not displayed in the dialog that manages category attributes (Menu | Select Calendars).
• Date for last Backup Everything in Menu | About and info legend no longer displays 1/1/1900 if no backup had ever been done and displays "(None)" instead.
• Fixes an issue in the new RemoteServerList Preference that before the preference was set to any value it was displaying an error message (the fix in V-4.2.06 was incomplete).
• When using Menu | Debug | Remove Deletions, Pimlical now logs the number of deleted records into the AuditTrail file (this is important for tracking down issues with unexpected re-appearance of deleted records).
• Removes the prior requirement that duration values entered for preference values use time interval specifies in the same case as the associated preferences. Previously, if, say LetterForDay was set to 'd', then it would not match a 'D' entered as a duration value in a preference (such as SnoozeStrings, etc.).
• A problem with unacknowledged alarms is corrected in this version - under some conditions, if the user never acknowledges an alarm (and it might be this only happens if they tap the alarm icon to silence the alarm and then do nothing), no further alarms will sound until Pimlical is re-activated. It could also be an issue dependent on the screen timeout value (more of a problem with short screen timeouts).
• A new problem (caused by a change in AOS) was causing Pimlical to miss a change of timezone if it was running when the timezone was changed in Android Settings. In turn, this could cause events to be shifted by the amount of the missed timezone resulting in them being displayed at the wrong time.

• Fixes an issue with dropped line of code n V-4.2.06 which was causing AutoSync to unexpectedly fail if the preference AlwaysResetBeforeAutoSync was set to True.
  

• Leaving the preference AlwaysResetBeforeAutoSync set to True when using Remote Server no longer causes an issue (previously, AutoSync might not proceed).
• Fixes a new issue in V-4.2.05 that if you were using an alarm preset, it could cause an Exception Error when creating a new event.
• Fixes issue of complaining about the RemoteFilePath preference if it was never set (the default preference file supplied a default value of an informative template for the preference (ServerName),(Protocol),(Host Addr),(Path),(UserName),(Password) and was not checking for that. If not used, that preference should either be blank, set to None, or to that informative template.
• Fixes an issue on bootup whereby if the Widget was installed, it was not refreshing.
  

• Adds support for Remote Servers which can be accessed via FTP or FTPS protocols. For example, you can attach a hard drive to your WiFi router (if it has a USB port) and then access it with the Internal File Manger to copy files to and from that device. There's a new preference: RemoteServerList which supports multiple Remote Servers. For each server, there are six attributes specified, separated with a comma: {Name},{Protocol},{Host Address},{Path},{Username},{Password}. There can be any number of Server Attributes specified - by default, the first defined server will be used by default. The name is an arbitrary name that you assign so you can quickly recognize which server the remaining attributes are for. The second item in the list is the file transfer protocol which can be set either to FTP or FTPS (Secure). The Default value is FTPS. For example, the server attributes might be specified by something like RouterDrive,FTP,192.168.0.1,/sda1/,admin,MyPassword.
  
  In general, you may find that you have to use FTP for a router (few routers support FTPS), but can use FTPS for accessing a web page (more secure).
  
  For the path, there should be a directory name unique to that storage device as Pimlical uses that to know that a path is on a Remote Server (if there is none, just use a single forward slash). The path should always end with a forward slash. You may have to fiddle around a bit to determine what the name of the path is. For example, on a TP-Link Router, the path is usually just /G/.
  
  The user name and password will be the same as what you use to log into the Router, for example: admin,xyz or Trouter, NzY0414). Note that such drives (including NAS) can also be accessed directly from the desktop (for example, in Windows (Right-click This PC, select Add a Network Location and enter the appropriate information to access the drive).
  
  Access to the Remote Server is almost completely transparent. the Only difference is that to use Open and Share, Pimlical will copy the remote file to a temporary file in the Pimlical folder (Temp.tmp) as otherwise the App responding to Open and Share would itself have to be able to handle FTP/FTPS access (which it won't). Note that if you Open a file and then change the file, the changes would be made to the temporary file only and not the original file on the Server. Most contemporary routers have a USB port which you can plug in an external USB drive or USB key, thereby providing a server on your local network. You can also use None as the first entry in the RemoteServerList preference to indicate that there is no Remote Server (while still keeping lists of other Servers available for subsequent restoration). If you use a VPN you might find access is blocked by your web-hosting service/router, especially if it's a popular VPN (this is not a Pimlical issue!).
• Adds new Preference Option: BackupEverythingUsesRemoteServer. If set, instead of doing the Backup Everything to local storage on the phone, the Backup Everything uses the Remote Server for storage (thereby providing a more secure backup as if the phone is lost or stolen, the backups are still available). Remember this backup would occur over the wireless network and would therefore take substantially longer.
• Adds support to AutoSync to sync using a Remote Server in a manner similar to how Dropbox was used (but in the case of a local Remote Server, still providing an off-cloud sync solution, or on-cloud but to some other Web site that the user has access to). To use this feature, set the preference: AutoSyncFilePath to RemoteServer, and Pimlical will use the Remote Server defined by the first RemoteServerList Preference to store the Server Files (in a manner identical to how Dropbox currently handles files). Pimlical creates a folder PimlicalAutoSync in the root folder of the Remote Server (in the example above, it would be in /sda1/PimlicalAutoSync) to store the files. You can also follow RemoteServer with a comma and then the name of the Remote Server (first item in the list of six attributes for one of the servers). That way you can have Backup Everything backing up to a Remote Server on your Router, but have AutoSync sync to a web server page on the Internet without having to change any preference item. If there is no server specified, then the first server in the RemoteServerList preference will be used by default.
• In the File Manager, the root path is now hidden and the parent directory indicator (..) is no longer displayed in the file list of the root directory (avoids some confusion that there is access to the parent directories).
• The Edit dialog now adds a + sign for the legend: Create Link to signal that a long-press on that button creates a link to the Memos database (a brief tap links to the Contacts Database). After tapping the Edit Links button in the Select Linked Item dialog, the New button also has a + to signal that a long press on that button will create a new Memo Link (a brief tap still creating a Contact Link).
  
• The About dialog now records the date AND time of the last Backup Everything function (and that now includes manual as well as automatically initiated backups (previously, only the date of the last Automated backup everything was recorded). Also, a green checkmark indicates the last backup everything was successful, whilst a red X indicates that it failed.
• When copying files for BackupEverything/RestoreEverything (and initial setup), Pimlical now displays the current number of files copied in real time (so you know something is going on).
  
• When using Direct Sync or AutoSync, Pimlical now copies the following files to the other device/server: Default.txt, SystemPreferences.dat, IconArchive.dat, Worldtimezones.txt, PimlicalTemplateExport.dat, *.flt (all filters). To avoid confusion (since files from different platforms could end up on the same platform), the filenames start with the platform name, so they would appear as: Windows_Default.txt, Android_Default.txt, Windows.IconArchive.dat etc. This provides for backup of preference/system files on every sync, and also facilitates moving files such as the IconArchive.dat file between platforms, as they can then just be renamed as appropriate.
  

• Now handles the case where an alarm triggers during DirectSync in a manner similar to how an Alarm triggering during AutoSync is handled (alarm is auto-snoozed to avoid contention problems).
• Addresses obscure issue of not properly rebuilding the screen under some rare end conditions. 
• Corrects erroneous fix in V-4.2.03 for UncaughtExceptionError when handling meetings and legend was None.
• If location field contains both a period and a comma, then it considers the field to be an address and will display the Map icon (for GPS coordinates) - previously, it would display the phone Icon.
• When the preference AlternateSelectionInterface is set to True and you long press an item to popup the list of popup commands, P/A now enforces a delay of one full second before an item can be selected (previously this was set to 1/2 second). This is intended to avoid a "bounce" problem because AOS can pop up the list while the user's finger is still down on the screen, and when they lift their finger off the screen to select a popup command, AOS can generate a spurious tap right then which automatically selected whatever command was under their finger.
• Fixes an obscure (and benign) IllegalArgumentException error that can occur when the Floating Advance triggers a log that also requires insertion of the user's required information into the log file.
• Fixes issue of not displaying the AutoSync icon during AutoSync if the preference AlwaysResetBeforeAutoSync was set to True.
• If there are multiple toast messages created right after each other, P/A now quickly cancels any pending toast messages to display the most recent one.
• Ensures that no more than 100 error files can be created in a single session (there are some really odd circumstances where an operation might create thousands of error files because the same problem was encountered over and over again - and that could overwhelm the Android Filing System
• When creating a new event (appt or float) if the event is untimed, the primary alarm preset is not applied even though the preference: ApplyAlarmPresetToAppts/ApplyAlarmPresetToFloats was set.  However, if the preference  ApplySecondaryAlarmPresetToAppts/ApplySecondaryAlarmPresetToFloats is set and the preference ApplyAlarmPresetToAppts/ApplyAlarmPresetToFloats is not set, then the secondary Alarm preset is applied to the primary alarm. That way, there is a workaround for those users who still want to have a preset alarm on untimed events (unlikely though it would appear anyone would ever want that!).  This is only done on the initial creation of the event (not when toggling the alarm status, etc.).
• The image path in the Edit dialog when an image is present has been made more legible as some users apparently did not even notice it was there (with just the filename now in larger type). When the image is tapped, there is now a View button that uses the internal File Manager's open command allowing it to be viewed/zoomed, etc. in whatever App is associated with images. Also, the image name is included in the popup command to display the Internal Record Details of an event.
• Fixes a new issue in the handling of Action Tags whereby tags were getting constantly repeated (it was only noticeable if you went to Edit a tag or looked at the list of tags).
  

• Adds new Action Tag: SpanEventsUseStartEndDay. If an event is a span event, then rather than using the start of day as 00:00:00 and the end of day as 23:59:59, it uses the start and end of day as defined in the preferences: DayStartMinute and DayEndMinutes (thereby avoiding the creation of multiple time slots that may not be wanted or needed).

• Toggling Absent Status now includes functions for Toggling Cancel Status (sets Type to Free, and if the preference SetZeroDurationIfCanceled is set, it also does that for the Absent Status too.
• Fixes a very obscure issue: if you put the Filters function on the command bar and long-press that button to toggle between the Default Filter and the last used filter, on rare occasions, and if the view/date did not change based upon switching filters, the button would change color appropriately, but not immediately redraw/refresh the view to show the results of the new filter.
• Caters a bit better to the display bug in AOS when the screen is displaying the Quick Entry Dialog in landscape mode (previously AOS screwed up the display of the three buttons at the bottom of the screen so badly that the button text was unreadable).
  

• Fixes typo in V-4.2.02 that inadvertently set delay on selection of popup command to 5 seconds instead of 0.5 seconds, after long-press on item in main view (with AlternateSelectionInterface set to true).
• Fixes issue of UncaughtExceptionError when handling meetings and the legend None appears for a meeting attendee.
• Fixes issue of popup command Remove Snooze Alarm returning to EventSelectionList when preference:  AlternateSelectionInterface is set to True (it should return to the main View).
  

• Fixes an issue with some popup commands when the preference AlternateSelectionInterface was set to True, whereby it might unexpectedly popup an event selection list after executing the command.

• Adds a new Status type of Absent. This is similar to Canceled, except it means the event will/did take place, but it was not attended (useful for meetings where you aren't going to attend, but don't want to mark it as Canceled when the meeting was still being held). Events marked as Absent will also be struck-through (like Canceled items). And like Canceled items, any alarm set on the item will be removed. The associated icon is a stick figure of a person with a red, diagonal line through it. This status type is also included for the FIND function and for Filters. Also adds a new popup command Toggle Absent to set/clear this Status type (alternating with Normal Status - remember to enable display in preferences: PopupListCommandsForEvent, PopupListCommandsForMultiSelect if you want to use it).
• For Contacts links, if the original link in the Calendar Database is no longer valid (the referenced contact no longer has the same uniqueID due to backup/restore, import from vCard file, etc.), Pimlical now attempts to recover the link by using the first/last name of the linked contact.
• Adds new popup commands: Copy Description, Copy Note and Copy Location that copies the respective fields of the selected record to the system clipboard (again, you might want to edit the Popup List Commands to display these commands).
• When setting an image for a contact in the Contacts Section of P/A, P/A now obeys the preference: UseFileNavigatorForImages. Previously, it always used the Android media navigator to locate an image for a contact (also corrects some issues in setting/replacing a contact image).
• Adds new preference item: UseVolumeButtonsForAlarms. Value can be Ignore (default setting), or Dismiss (either volume button dismisses) or Dismiss And Snooze (Volume up dismisses, and Volume Down snoozes). Very handy when alarm goes off while driving as you don't have to look at the screen to dismiss an alarm!.

• In the Meeting Dialog, the Add and green checkmark buttons have been swapped around to be more consistent with the layout of other dialogs in P/A.
• The fix for the bug in the Android OS (on Samsung phones only) whereby it (sometimes) fails to include the alarm notification in the onCreate() Callback was incomplete in V-4.1.34 - this version should now close what is hopefully the last remaining loophole in that code. Symptom was a very rare missing of an alarm on Samsung phones.
• When you use a template that contains the Action Tag: ScheduleIn: you can now put a comma after the duration and include a note which is then appended to the description field of the create event (You might set up an event with a description of Reminder: and this action tag so the comment gets put after the "Reminder:").
• Fixes one (but probably not the only) loophole in a very obscure issue: if the Widget has just refreshed and the Contacts or Memos button is tapped, and there's a fast startup file present, the display can "look" allright, but in fact the underlying pointers are still those of the Fast Startup File and point to the earliest records in the database (the puzzling issue of bring up the Event Selection List or Long-pressing an item and finding it's pointing to one of the earliest records in the database). 
• Timed events that span more than one day now use the start/end of the day as defined by the preferences DayStartMinute and DayEndMinute for days other than the first or last day. Previously, it would use 00:00:00 and 23:59:59 which resulted in many more timeslots being added to the display.
• Fixes an issue with some popup commands when the preference AlternateSelectionInterface was set to True, whereby it might unexpectedly popup an event selection list after executing the command.
• Avoids unexpected side-effect of workaround for AOS bug with Scrolling (AOS creates a spurious scroll event when finger slides a bit when tapping/pressing a button), which was interfering on occasion with long-presses on a button on the command bar (such as the Filter button if set there).
• Menu | About now includes total number of records in Local calendar and Android Calendar and suppresses that line if the corresponding value is 0.
• Fixes issue of not being able to see the full HTTP address in the Direct Sync dialog - the address is now placed in smaller type in the message area of the dialog (previously it was put in the title, but often got completely truncated so nothing was displayed). Also removed confirmation on canceling sync as that is unnecessary.
• Now protects against a spurious AOS callback (onCreate() or onNewIntent()) while the Alarm or Snooze dialogs are displaying. In theory this should be impossible, but the log files show that this indeed happens on rare occasions (and was causing alarms to get lost by forcing an unexpected reschedule of alarms).
  

• Short Description field in Edit Dialog now obeys capitalization preference (AutoCapitalizeEventTitle) for main Description field.
• If the time field is in a different timezone, so both the adjusted and native times are displayed, and if the resulting string is wider than the available space, the native time is omitted and "[TZ]" appears instead to signal that the event had a different native timezone. Also, the description is now properly word-wrapped taking that into account.
• Avoids an obscure issue where a licensed/subscribed user could show up as unlicensed/unsubscribed if there was a network problem reading system files.
  

• Fixes a contention issue after rebooting phone where P/A and the Widget were not being sequenced properly. Widget should now refresh immediately after P/A exits after rescheduling alarms. Remember that you may well have to remove/reinstall the Widget after installing a new release (should not be necessary, but seems to be under some conditions not yet identified).
• Fixes an issue of an alarm being delayed or handled oddly when the Contacts or Memos activity is active at the time an alarm triggers.
• In cases where AOS reactivates P/A after absconding with P/A's memory, and an event selection list was displaying, P/A now displays an empty list along with a brief toast message stating: Wait for Database to Finish Reading... (while the database is being read). Previously, it might have shown a rather bizarre "template" display.
  

• Fixes a missed alarm issue due to onResume() not thinking an alarm was pending.
• Fixes an obscure missed alarm issue due to onStop() being called milliseconds after onNewIntent() was called (something that in theory should never happen, but the log files showed it must have).
  

• Adds new Debug Command: Find Record # which displays the start date/time and event description of the record at the specified position and a button to go to that date (useful for finding records referenced in some error messages/error files).

• Fixes an obscure error that was preventing the new code in onResume() from catching missed alarms. Also added more diagnostic information in Log file for alarm handling.
• Removed two potential contention issues in P/A and Widget that could create error files (condition was benign and handled).
  

• Removes the validity check in Debug Mode for uniqueID's when reading the calendar database as it isn't really necessary any more (now that there is a Menu|Debug function which does the check), and its removal obviously speeds up the process of reading large, local calendars in Debug mode significantly.
• Avoids generating the Alarm Dialog much later when Pimlical launched due to a missed alarm.
• Now catches missed alarm by detecting when AOS fails to generate onCreate() or onNewIntent() callback (for unknown reasons) by catching it in onResume().
• Removes the Release/Install Date line in Menu | About and in Reqd Info list in Menu | Help & Usage Tips, as the date is incorrect (perhaps it's just the very first time the user installed P/A and does not get updated for version upgrades?).
  

• Avoids generating error file on Backup Everything with preference BackupAndroidCalendars preference set to true and there are no Android Calendars at all.
• Avoids generating stacked "Toast" messages when moving multiple floating events to a date that is later than the Due Date.
• Long press on the Task button in an Event Selection List no longer creates a Floating Event (probably left over code from an old layout of that dialog that did not include a Float button, and this function was never documented).
• Now that there is a button to copy the Required Info to the clipboard, the automatic copying of that same information on the Email Tech Support button (in case the user does not have email configured) is no longer useful and has been removed.
• Includes code for Widget that might allow Widget to refresh right after a new version is installed.
• Fixes issue of the Widget thinking some Preference Dialogs were left open and therefore would not refresh.
• Time field in Widget now caters to different values for preference: TimeSeparatorString and also right-aligns time field better.
• Fixes side effect of workaround for alarm problem in Samsung phones - if the user launches Pimlical off the Recent List, AOS can in some cases end up launching a repeat of the alarm.
  

• There is a new Preference: BackupAndroidCalendars. If set to True (default value), then on the Backup Everything function, Pimlical will also save all Android calendars locally under their calendar names in the .../Pimlical/PimlicalCalendars folder. The databaseID's are changed from the Android calendar to the local calendar. This insures against any loss of information in Android Calendars, as you can always open up that local calendar and copy events from it back into any calendar.
• If the note field in the Edit dialog has a number of lines less than or equal to the maximum number of lines shown (either limited by the preference: MaxLinesForNoteDisplay, or because the field size was toggled to maximum size), a single note icon is displayed to the left of the note field. If there are more than that number of lines, the icon shows a small and large note icon with an arrow between them to show that there is more text than currently being displayed (the same icon that was always used in prior releases). That way you can tell immediately if a portion of the note field is being hidden or not and the icon is updated in real time as characters are typed.

• Fixes the issue of  multiple instances of P/A showing up in the Recent Apps list, which if then dismissed could cause unexpected issues in P/A.
• The list of Preferences now ignores the global prefix ($) when displaying sorted preferences (previously, the prefix was not shown and it looked like the sort was just wrong, since the item sorted to the top of the list).
  

• Contacts View dialog now has a Copy icon at the end of the header for the note field that copies the note of the contact to the system clipboard.

• Fixes another case where the recent change in V-4.1.25 was, under some circumstances, causing multiple instances of P/A to show up in the Recent Apps list, which if then dismissed could cause unexpected issues in P/A.
• If preference MultipleCategorySelection is set to True, and all categories are unselected, Unfiled is now set as the category (previously, P/A either complained about leaving one category selected, or left the category selection unchanged).
  
• Avoids an UncaughtException Error in handling the resolution of meeting participants when the Meeting dialog was left open, user switched to another App, AOS had absconded with all of P/A's memory, and AOS reactivated P/A.
  

• Removes one line of code left over from V-4.1.24 which should have been removed. It apparently was causing multiple alarms to be missed by one beta tester (although I could not reproduce it here).
  

• Removes a debug check in V-4.1.24 for AOS restarting an App without properly reinstating task (yes, it does that on occasion) that was causing UncaughtException Errors when that happened (in particular, it seems that if the user relaunched P/A from the Recent Apps list after the onDestroy() callback had been processed (either because AOS terminated P/A or menu | Exit was used) odd errors inevitably occurred because AOS would reactivate P/A at unexpected places in the program without calling onCreate() or onNewIntent().
• When using menu | Exit Pimlical, or when AOS terminates Pimlical, Pimlical now uses an AOS function that avoids displaying P/A in recent Apps list. This helps avoid the above issue which can cause problems
• Avoids the issue, new in V-4.1.24, of ending up with multiple copies of P/A in the Recent Apps List.
  
• Fixes issue in popup command: Compare Calendar Events where the Android Calendar Names were not being reported correctly when the DatabaseID's did not match.
• Now marks the preference; WidgetIsInstalled as $WidgetIsInstalled in the default preference file as this preference should always be "globalized" (i.e. written to all Custom Preference Files).
• Preference Diffs function in Menu | Debug now properly manages globalized preferences that begin with a $ prefix.
  

• One more fix for Alarm issues here.
  

• Fixes an issue that, as a side effect, appeared to be causing a lost alarm if Pimlical was active at the precise instant an alarm triggered.
• Provides another fix for the issue on Samsung phones whereby Pimlical is launched to manage an alarm, but Samsung OS failed to provide alarm indication in onCreate() callback.
  

• Protects against a lost alarm caused by a very obscure case where AOS apparently got confused and generated multiple callbacks, some spurious, and some in the reverse of the normally expected sequence (generally, only on Samsung phones).
• Protects against an obscure case where Widget encounters an UncaughtException error which could result in Widget not refreshing.
• Protects again an obscure UncaughtException error when the date picker dialog is left open, the user leaves Pimlical, AOS absconds with Pimlical's memory, and then the next day, Android OS invokes Pimlical to restore the date picker dialog.
• In the meeting dialog, the list of attendees now scrolls nicely between the header (with the Chair, and Chair-email) and the bottom row of buttons (previously, the list view pushed the bottom row of buttons off the screen).
• In the meeting dilaog, six separate icons are now used for the six possible status types (previously, only four icons were used and in an inconsistent manner).
• Ensures the Chair and Chair Email are displayed on entry to the Meeting dialog even if the Chair is not currently displayed in the list (i.e. has not been scrolled into view yet).
  

• The dialog showing the list of attendees to a meeting now displays the Chair name/email above the list (same way that P/D displays it). Also when long-pressed from an event selection list, the green "done" button is now displayed.
• The long press on the Icon Add button (Green + button at top right in Icon Dialog) now generates a brief ''toast' message reminding the user that it will import all icons in the selected folder.
• Menu | About now disables the Upgrade button while re-reading the licensing information in the background and re-enables it the instant the information is available.
• Messages from the Upgrade button in Menu | About,  regarding installation of new versions/new beta previews has been updated to be less confusing to the user. Also avoids trying to install an older (or the same) version which previously caused puzzling message from Android about an "invalid package", as Android fails to indicate that the problem is that you cannot downgrade without first uninstalling the later release.
  

• Fixes an UncaughtExceptionError that might occur in the popup command Compare Calendar Events when the first event has a repeat specification but the second event does not (was all right if it was the other way around).
• Removes some new code in V-4.1.19 that could under some circumstances (such as changing calendar selections/attributes) cause Pimlical to exit while another thread was updating the local calendar which could then end up truncating the local calendar file.
  

• Adds new preference: ReReadCalendarOnChange which monitors the native Android Calendar database for changes (which could also come from Google calendar) and will force an immediate launch of Pimlical/Android and re-read of the calendar if Pimlical was in the background (if in the foreground, just the brief Toast message is displayed). Default value is False, set to True to perform the immediate launch/reread. Requires GoogleRefreshInterval preference set to -1. This action is triggered off the Android OS broadcast (which at times seems a bit flaky?).
• A long press on the Note icon of an event in the Event Selection List now copies the contents of the note to the clipboard.
• A long press on the Location icon of an event in the Event Selection List now copies the contents of the Location field to the clipboard.
• A long press on the Web/URL link icon of an event in the Event Selection List now copies the contents of the Link field(s) to the clipboard.

• Fixes an UncaughtExceptionError that might occur under some conditions if the preference GoogleRefreshInterval was set to a non-zero value.
• Re-implements feature of setting GoogleRefreshInterval to -1 to automatically pickup changes made in Google Calendar or the native Android Calendar App.
• Avoids an android.os.TransactionTooLargeException: caused by attempting to save a very large Event Selection List for later restoration (when AOS has absconded with Pimlical's memory). Only lists < 100 events are now preserved for later restoration.
• Adds another fix for the Samsung OS alarm problem (where it creates an erroneous onCreate() callback) - turns out the onPrepareDialog() callback was ALSO trying to reread the calendar and that caused onNewIntent() to bail, which in turn caused the alarm to be lost.
• Fixes layout in Boolean Preference Dialog (where Cancel button was getting truncated).
  
  

• When the Share or Open button is tapped in Menu | File Manager, if there is no application registered to handle that filetype, a brief toast message appears to that effect (previously, it was causing an Error file to be generated).
  

• When upgrading to a new version, all old log files and error files are deleted.
• A recent change in a Beta Preview was causing log files to not be created. If the log file already existed, the log file would be updated, but it was not alwlays creating a new log file.
• Caters to what appears to be a new case of AOS activating Pimlical in an unexpected place AFTER AOS has absconded with all of Pimlical's memory (this is something that is apparently not documented?).
• Handles a potentially lost alarm if the device is rotated at the precise instant that Pimlical is in the process of re-reading the calendar in order to display the alarm.
• Avoids an obscure problem with a lost alarm (Android triggering onCreate() as well as onNewItent() when Task was already active (bug? undocumented action? Activity layering issue?). This does not appear to occur on Google Pixel Phones, and may be just unique to Samsung phones, so it might have been a new issue that Google fixed, but which has not yet migrated to Samsung's proprietary version of Android(?). It should eliminate that odd toast of CalendarMain.onNewIntent(): CurrentlyReadingCalendar: True, readingSystemPreferenceFile: False - intent ignored...
  
  

• More fixes for obscure alarm issues.
• Restores the reason why the Widget was not refreshing to Widget Configuration Dialog (the condition was unexpectedly lost in a recent version). It now shows the date/time of the last Refresh and (if appropriate) the latest reason why it did not refresh.
• Fixes a lost alarm issue caused by a complete exit of Pimlical prior to Floating advance (timer was stopped so triggering an alarm review to get the next alarm set was non-functional) - the timer is now reset.
  

• Ensures that the user has granted permission to Display Over Other Apps when Pimlical is launched if the preferences are set to use full-page alarms (alarms won't work if that permission is not granted). Previously, this was only checked for when exiting the Preferences dialog, and several users ran into this problem being unaware that they were no longer holding that permission.
• Fixes issue in the Floating Advance that might have left a flag set that could cause an unnecessary re-read on the calendar, and which might also account for the event Selection List displaying old or no information on first invocation of the day.
• Fixes a Typo that was causing a lost alarm when the message: CurrentlyReadingCalendar Flag Set - intent ignored was displayed (it was inadvertently, prematurely terminating the main calendar thread).
• Fixes cosmetic issue of menu buttons having differing widths - in some cases that was causing a somewhat ugly, lopsided display - in this release all buttons are equal width on the line.
  

• Reverts to using the level AOS-33 SDK libraries, as the level 34 libraries did not appear to be stable and were causing odd, fatal errors.
• Works around alarm issue in V-4.1.12/14 that were caused by a subtle change in the way that Android OS was handling the Life Cycle that grossly interfered with the way that P/A was handling alarms.
  
• AutoScrolls participant list for meetings so it displays the most recently selected/entered participant.
  

• Adds a Move command to the File Manager to move a file from the destination folder to the new folder location.
• Fixes issue with File Manager Copy Command returning to the parent directory of the target directory rather than the target directory.
  

• In Debug Mode, the Memo Edit dialog now displays the uniqueID (as is done for contacts).
• Fixes Exception Error that can occur in File Manager if item is opened/shared and then while other App is displaying item, low memory conditions cause AOS to abscond with Pimlical's memory, and AOS then tries to restore the File Manager dialog.
• Fixes issue of a user trying to launch Pimlical at the precise instant that Pimlical is re-reading the calendar in anticipation of displaying an alarm. If that happens, a brief "toast" message appears informing the user to wait, and that an alarm is about to trigger.
  
• Fixes issue of AutoSync being automatically triggered while another thread (Widget, Pimlcial) is reading the System Preference File - AutoSync is now delayed until that (and some other contention issues) are resolved.
• Fixes long-standing consistency issue with Category and Calendar names now being treated as not case-sensitive (it's gone back and forth a few times over the years). One symptom of the inconsistency was that a Filter would show an explicit list of all category names rather than just "(All)" - which could then result in a category being unexpectedly hidden because it was not listed.
  
• Several minor layout tweaks for improved cosmetic appearance, especially if Display Fonts in System Settings is set to one size larger than the default.
• Compiled with, but does not yet target, SDK Level 34.
  

• Changes the values of the Attendee Status and Attendee Role Lists to match iCalendar 5545 standards. This change will also appear in P/D, V-4.1.02 or later, which then resolves the incompatibility in the way P/A and P/D were handling the Attended Status and Role fields. Also removes irrelevant icon at start of each row with green checkmark. Note that users with existing meetings might need to edit them to conform now with the RFC 5545 standard.
  

• Adds a new Debug command: Preferences Diffs that takes the current Preference file (usually Default) and generates all the discrepancies from the default values into a file in the Pimlical folder. Preferences still set to their default value are not listed. This is useful for quickly determining which preferences are set to different values from the default, and for saving your customizations for future restoration.
• When Opening or Sharing a file in File Manager and the filename/extension was changed in the Edit field, P/A now makes a copy of the file in that same folder under the new name, leaving the original file untouched.
• Changes the mechanism for invoking the Automated Backup to trigger off a user action (such as exiting the Edit Dialog or Event Selection Dialog, or moving to a new day, etc. Previously, it was triggered off refreshing the main screen, but that could be caused by some internal event, such as an alarm which was not desirable (could force a snooze on the alarm).
  

• The AlarmPreamble preference for spoken alarms now implements the use of leading commas BEFORE any text to provide a pause before anything is said (in a meeting you could see the screen light up and have time to tap the Alarm icon so no sound emerges). This was already documented to work that way in the manual but not implemented till now.
• Adds an operating mode line to the About dialog to indicate if the user is running in Debug Mode (with or without a log) or Normal mode (this information is also now included in the gathered information for Emailing Tech Support).
  

• Fixes issue of erroneously displaying brief toast about No Events Selected to be Snoozed every time an alarm is snoozed (the alarms were all properly managed though).
• Has new Worldtimezones.txt file (and Worldtimezones_all.txt) with two new DST rules to properly handle Central and Eastern Europe, i.e. separately from Western Europe, as London changes DST at 1am, Central Europe (Paris, Germany) changes at 2am and Eastern Europe (Greece, Finland) changes at 3am, These two DST rules were added:
     .L L103 L110 Central Europe, Paris, Germany
      .M L103 L110 t3h Eastern Europe Greece, Finland
  and the timezones were changed to:
      +01:00L Europe/Paris [CEur]
      +02:00M Europe/Athens [EEur]
  and the rule for Tehran was changed to N in both files to accomodate this change. Note that this file is cached into SystemPreferences, so you have to go into menu | Preferences | Restore | Reset and check the box for Worldtimezones.txt to see this change take effect.
  
• Fixes issue of encountering an Exception Error with a feature (I think only used on Lord Howe Island and Troll) in Pimlical to handle Daylight Savings adjustments other than one hour (30m and 2h respectively!). Such DST rules would look like this: .P 1110 1104 t3h d30m Lord Howe Island.

• Another fix to V-4.1.09 for the problem of avoiding an obscure UncaughtExceptionError in the new File Manager Function that could occur under some conditions when the remembered path was completely empty.
• The Advance Time dialog used to set alarms was unexpectedly displaying Seconds for users running in Debug Mode - leading to the expectation that it was possible to set alarms to the exact second - that is not supported and in fact such alarms would get missed, so this release no longer displays the seconds field in debug mode.
• Fixes a flaw in the BackupEverything/RestoreEverything commands: the destination folder contents were not always being pre-deleted, so any existing files in the destination that were not in the source were retained (normally not any issue, but the expectation is that the copy should be a perfect match).
  

• The About Dialog now includes information on the Widget Refresh (date/time of last refresh, and why the Widget may not have Refreshed the last time it was scheduled to refresh).
  

• If an alarm triggers while AutoSync is active, or during a Backup/Restore everything, or during a Widget Refresh or any other activity which could potentially conflict with the alarm, the alarm will be auto-snoozed to avoid interaction issues. The reason for snoozing is written to the debug log file and also displayed as a toast.
• When exiting Pimlical using menu | Exit, or refreshing the Widget from Menu | Debug, Pimlical now ensures that all dialogs that could ever be displayed are all closed (due to issues of Android OS doing odd things that leave Pimlical with the indication that a dialog was open when it was not.
• Removed some old animation code (that never seemed to work properly) for the Event Selection List (in case it had something to do with the bizarre issue of it sometimes displaying the dialog template instead of event data. On same issue, now attempts to rebuild selection list if it is found to be null, and if unable will just relaunch acttivity. That should prevent all those odd displays.
• Changes the test for the maximum number of permitted email attachments (such as error files) from the Email Tech Support button from a limit of 20 files to a limit of 20Mb (approximately) as that is the limit in Outlook (Yahoo mail and Gmail have a 25mb limit).
• Avoids an obscure UncaughtExceptionError in the new File Manager Function that could occur under some conditions when the remembered path was completely empty.
• Caters to an unusal situation where Android OS was terminating Pimlical/Android activity at the precise time it was reading the calendar - problem was that some flags were not cleared, result in the need to force-stop Pimlical to recover.
• Fixes problem with rotating the screen whilst the Icon Dialog is displaying (calculations for number of rows and columns was completely off, when preferences were set to 0 for autocalculate).
• Fixes issue in using the TodayLocator feature (highlights Today cell temporarily in all views displaying more than one day - other than ListView) whereby on relaunching PIimlical from the Day VIew, under some circumstances the screen would be blank.
  

• On reading an event from Android Calendar that was originally created in P/A and marked for the home timezone with the (normally hidden in P/A) [H] tag in the note field, Pimlical now caters to the possibility that the event was MOVED to another timezone by Google Calendar (or Native Android Calendar App) and will re-adjust the times appropriately so it displays properly in the Home Time Zone (previously if the event was say changed to UTC, the UTC time was preserved, but the timezone reset to Home Time Zone). For example, some other calendars interfacing with Google Calendar might not include the timezone information at which point Google might present the time in UTC, which would be a problem with an event originally created in P/A and which had the [H] (Hometimezone) tag in the note field.
• Restores the brief toast message that the widget is refreshing when the Widget Refresh button is tapped even if the Widget is not forcing a re-read of the calendar.
• Incorporates a slight change in the formatting of the Preferences Restore Dialog to make it a bit clearer as to what gets restored by listing the actual filename rather than abbreviations - note that ALL custom preference files (attached to filters) are also backed up and restored, as well as the Default.txt file. Previously, the file size was reported for the CURRENT preference file in effect, whereas in this release it now uses the DEFAULT preference file size for consistency. Also, it was always displaying "Yesterday" for any date in the past, rather than displaying the date in medium date format for any date preceding yesterday.
  

• Fixes a new issue in timezone handling in Google/Android Calendars whereby the Android and Google calendars were not properly recording the time and original timezone of the event from Pimlical/Android.
• Fixes a long-standing issue of an event in Google/Android Calendars that has different start and end timezones round-tripping through the Android Calendar (that can only handle one timezone) through Google Calendar and then back through Android Calendar to Pimlical with Pimlical restoring the original end timezone.
• Fixes issue in moving an event with different start/end timezones to a new time or day (the end timezone locale was getting lost, and if it was moving across a DST crossover day, the duration might not be correct).
• Fixes issue of not always reporting the correct duration of an event if the start/end times were in different timezones, or the start/end dates straddled a DST crossover (example, event in USA this year on March 10th starting at 1am and ending at 3am now finally shows the correct duration of 1h, since 2-3am did not exist!).
• Fixes several obscure cases where on moving or modifying events, an event with different start/end timezones might unexpectedly get both start/end timezones set to the start timezone (displayed times were still correct, but the original, native timezone information might have been lost).
  

• Fixes new issue in V-4.1.05 that it was not correctly reading the embedded Icon Key # in the filename of older style icons that had somewhat screwy filenames (all newer icons did not have this issue). Result was that older icons all had a key of 0 and returned the same icon. Note: it is possible you may need to restore the IconArchive.dat file from a backup to properly display the old icons.
• NOTE: it turns out that tiny change in V-4.1.05 only may have also unexpectedly modified some of your preferences that had a negative integer value (in particular, check these four preferences to be sure they have the expected value: ListViewHeaderPosition -1, LightenGoogleColor -1, DaysBackToRead -1, FingerSlipThreshold -1).
  
• Fixes an obscure issue of possibly not setting the correct locale for event timezones in an Android Calendar with a UTC offset that was not whole hours (such as Pacific/Marquesas,-09:30).   

• When using the Backup Everything command with the preference NumberOfBackupsForBackupEverything set to a value, Pimlical will now iterate through the process of deleting backups until the number of backups agrees with that value (otherwise if you set it to a smaller value, the number of backups would not be reduced to that value as it only deletes one backup prior to performing the backup).
• The File Manager Share and Open commands now use the possibly changed filename in the dialog (this can be useful, for example, changing the extension of an error file from .ERROR to .TXT so a regular text editor can be invoked with Open).
• The color selection dialog now includes two new buttons: Set Default which set Pure Black {0,0,0} and Pure White {255,255,255} respectively for the Foreground and Background colors. The default values for the preferences: ForeColor1 and BackColor1 have been changed to an "almost black" {0,0,1} and an "almost white"{255,255,254}. This avoids confusion over choosing Pure Black as a foreground color and not realizing that Pure Black is also the default foreground color and can therefore be overridden for example, by the default category foreground color. Also, if the preferences: ForeColor1 and BackColor1 have the old values of {0,0,0} and {255,255,255}, they will always be changed to the new default values of {0,0,1} and {255,255,254}. When a default foreground or background color is set, the color swatch also displays the legend "Default".
• Ensures that on upgrading, if permission to install unknown Apps is not provided, then after providing that permission, Pimlical proceeds with installing the upgrade (a recent change broke that feature).
  

• Fixes issue that a change in a recent beta preview had caused the manual refresh of the widget after booting up to be lost.
• Fixes issue that "File Manager" was listed as "FileManager" in the preference: MenuCommandsAndOrder which means that under certain circumstances an erroneous error message (Menu Item Not Defined: FileManager) was being created.
• When invoking DirectSync, P/A will now proceed without a WiFi connection if a cellular Data Internet connection is available (this would not normally be useful, but perhaps some advanced users fiddling around with VPN's could take advantage of this?).
• When an image attached to an event is missing, the error file now identifies the date and description of the event.
• Fixes an issue with a momentary notice that a subscribed user had no subscription, either on startup or upgrading to a new version (a moment later, the issue went away).
• Fixes issue of the interval timer that times things like the moving of the Red Bar in a main view, etc. getting unexpectedly disabled.
• In the color selection dialog, if a default foreground (Pure Black) or background color (Pure White) is set, the legend "Default" appears in the color swatch to make these defaults distinguishable from a "near-black" or "near-white" which are used to set an explicit Black or White that will not be overridden as a default.
• Fixes issue that the Cancel button in the Calendar Edit Dialog (which displays category colors and icon) did not result in leaving the original values alone - they were always updated to whatever changes were made in that dialog).
• Fixes issue that if the Image Path in the Edit Dialog is invalid, there was no clear indication in the dialog that there was a problem (other than an error files being created). Now displays a RedX, and the legend: File Not Found: {full path to image}, and an error file is no longer generated for this issue.
• When using the old "DateBk-Style" Time Picker, tapping on the TimeZone button to change timezones now reflects immediately in the button legend (previously, there was a cosmetic flaw in that it  only refreshed when another button was tapped).
• Ensures that when the Event Selection List is exited (returning to a main View) there are no spurious indications that any dialog is still open (which could cause the Widget to skip a refresh).

• Fixes issue of possibly, prematurely releasing the Wake Lock in the Alarm dialog when buttons are tapped - in particular, tapping the Alarm Icon  to silence the alarm and then user does nothing else (AOS might terminate the thread on timeout of the wakelock and in particular kills the AutoSnooze timer so that never kicks in and future alarms don't get rescheduled).
• Fixes a new timezone issue (would have first appeared in V-3.7.118, but never reported till now) when displaying an event from Google Calendar that was entered in a different timezone on a date that also spanned a Daylight Savings Time crossover (such as an event entered in PST for a date in which PDT was in effect).
  
• Menu | Debug | Internal Reset now also resets the remembered date of the last Automated Backup to Today's date.
  

• Adds a new preference for the File Manager: FileManagerSort which currently supports two values: Alpha - which sorts the folder contents alphabetically (as previously) and Date - which sorts the folder contents in reverse chronological order (newest item at top). 

• Fixes new issue in V-4.1.02 where a bizarre glitch caused a line of code to drop which resulted in the (duration) type preference values in minutes being ignored (so a preference that specified say 10m would result in 0s!).
• Adds a new Search Manual button in the Help & Usage Tips Dialog that links directly to a web page with the Google Search field at the top of the page so the manual can be more easily searched (requires WiFi connection of course).
• Fixes issue: on exit from the Edit dialog, when an Alarm or Snooze dialog was being displayed, Pimlical was scanning for the next alarm which could, under certain circumstances, unexpectedly caused the next alarm to be scheduled as part of the AutoSnooze action (so instead of showing the original alarm that was unacknowledged, it could show the next alarm). This might happen if user was IN the Edit Dialog when the alarm triggered, and then exits but never acknowledges the alarm and it subsequently autosnoozes. In theory, this is impossible because the Alarm/Snooze Dialogs should display on top of the Edit dialog and it should not be possible to exit the Edit Dialog under these circumstances (so this looks like an obscure Android OS bug that caused this behavior).
• The function to display a web page (such as Help items, Revision History, Subscription Page, etc.) now checks that either WiFi or a Cellular Data connection is available so the internet can be accessed and if not, displays an appropriate alert dialog (previously, there was no proper feedback as to what the issue might be).
  

• Fixes scheduling issues with the new feature to invoke automated BackupEverything commands (previously, it only got launched if the database was re-read, and there was also an error in recording the date of the last Automated backup - which is now also recorded in menu | About and required information). Note: for users who used this feature in V-4.1.01, go into Menu | Debug | Internal Reset and that will reset the date of the last Automated backup so it backs up on the next opportunity.

• On installing a new version, when launched, Pimlical, if it's not performing an automatic Backup Everything, will request that AOS activate the Widget right away.
• Includes a new button in Menu | Help & Usage Tips with legend: Copy Reqd. Info to Clipboard which copies all the required information for getting Technical Support to the Android Clipboard so it can be pasted into any email program (The Email Tech Support button also did this, but it seems most users were not aware of that).
• Fixes erroneous PimlicalDebugInfo.Log message on resetting snooze interval (was displaying date of last date in calendar instead of precise date/time to the next snooze).
• Fixes new issue in V-4.1.01 of inadvertently generating EXDATE rules when writing repeat events with exceptions into the Android Calendar Database which was causing Write Errors on Android Calendars (for some bizarre reason, Android Calendar import goes beserk if it sees such iCalendar rules).
• No longer runs the Widget if the Event Selection List is open in P/A (turns out that was causing unexpected error files as Android was complaining about an expired activity).
• When a locale is undefined (usually because Worldtimezones.txt was edited but subsequently replaced with default version), P/A now just logs this to the PimlicalDebugInfo.log file (if debug mode is set) and sets it to Home Time Zone rather than creating potentially thousands of error files. It also avoids the issue of floating events with an invalid locale getting all advanced to today's date.
• Adds more robust verification of date fields in the database (to catch errors such as the above).
• Many internal changes dealing with some subtle timezone issues - fixes the issue of events that spanned more than one day in a different timezone that also crossed a DST change-over not displaying a time that was off by one hour in the main views (the date and time were correct in the Event Selection List).
• Fixes an Uncaught Exception Error that could occur when snoozing an alarm on an item with a very short description.
  

• When deleting multiple items in an Event Selection List, if there are one or more repeat events present, Pimlical now displays an Alert Dialog asking if you want to delete just the instances of those repeats (INSTANCE), or if you want to delete the entire repeat series (SERIES). And there's a cancel button  if you want to cancel out and manage them individually.

• Fixes potential issue of getting a read error on System Preference File when upgrading to a new version (this correction will not take effect of course until this version is performing the upgrade).
• Fixes new issue of not properly importing an iCalendar file when using the File Navigator in Menu | Select Calendars | IMPORT.
• Fixes issue of not handling Exception Dates in repeat records from the iCalendar File that Pimlical generated from the local calendar since it was not properly reading the list of exception dates in the iCalendar Record.
• Cleaned up Icon button display in Icon Dialog and second row buttons in Event Selection Dialog.
• Fixed a potential conflict problem between Pimlical/Android and the Widget on starting up after rebooting the device.

• File Manager now displays a full dialog (rather than an alert) and includes the full path, filename, file size and the last Modification Date for the file. The navigation routine now replaces the path /Android/data/com.pimlicosoftware.PimlicalA/files/Pimlical with Pimlical [SS] (for Pimlical in Scoped Storage)as otherwise, the path is so long it doesn't get displayed on the title line. The new dialog also allows a long-press on the Copy/Rename/Delete buttons to bypass the normal confirmation dialogs (i.e. overwriting a file on Copy or Rename or confirming you want to delete) and includes a Done button to exit the File Manager. You can use the Back button in that dialog to conveniently return to the initial File Selection Display in File Manager. Adds an Open command which will open the file using any associated Apps for that filetype (so you can open PDF files in Acrobat, or graphics files with your graphics program, text files with any Text editor etc. This makes it possible to view error or log files on the phone using a text editor (more functional than using menu | Debug to look at them). Also adds a Share command which will send the file to any other application on your device that accepts files (email, printer, photo App, SMS App, etc.). When using the Copy command in the File Manager, you can also change the name of the file to be used in the destination folder, by editing the filename (as you would when renaming a file).
• Adds ability to schedule Backup Everything so it is automatically invoked at an interval of days specified by the new preference: DaysBetweenAutoBackupEverything. This preference has a default value of 0 which turns off this feature. To backup every other day, set this to 2. This backup will either do the backup to the root Pimlical/ folder, or will make date/time stamped backups to the PimlicalBackups folder (depending on the setting of the preference: BackupEverythingUsesDateTimeStamp (default is false). Regardless of whether the Backup is invoked by menu Command (or Command Bar/Gesture), you can now have Pimlical automatically delete the oldest backup copy prior to performing the backup with the new preference: NumberOfBackupsForBackupEverything (default value is 5). So if you already have 5 backup copies and perform a BackupEverything, and if  BackupEverythingUsesDateTimeStamp is set to True, the oldest backup is automatically deleted to make room for the newest backup. Note that due to new restrictions in Android it is not really practical to invoke this as a background task, so it is done in the foreground when Pimlical is launched (so it would typically run on the first launch of Pimlical on a day that called for the backup to be performed (so it relieves the user of having to remember to manually invoke the full backup). And the new File Manager feature makes it easy to just pull a single file from the backup for restoration.
• On installing a program update (from Menu|About|Upgrade), P/A now checks to see if the permission has been granted to install unknown Apps and if not, it immediately invokes the Android Permissions Manager to allow the user to grant the permission, and then proceeds with the installation if permission is granted.
• Adds the Menu | Backup Everything command as a command that can now be placed on the command bar (using the preferences: CommandBarViewButton#...) or as a swipe gesture using the preferences: UserDefinedGestureXXXX).
• Menu | Backup Everything now saves the file size (Gb or Mb) using definitions as a power of two (previously, power of ten was used - so one gigabyte is now considered to be 1,073,741,824 bytes as opposed to 1,000,000,000 bytes).  Values are also now displayed with one decimal point.
• Extends the use of the Preference:  ForceCalendarReadAfterWidgetRefresh to also apply to the Widget itself. If this preference is set to False (default is true), this means that the calendar as read by either P/A or the Widget is valid and does not need to be re-read. Do not set this preference to False if the Widget is reading a different set of calendars from P/A. If the same calendars are read, and if the Widget finds that the database is intact, it avoids the unnecessary re-read on the calendar, resulting in a much faster refresh of the Widget, often taking less than a second (so the normal "Toast" message is skipped and in general this results in much less interference with P/A too).

• Protects against an odd type of corruption in repeat events that would cause Pimlical to crash.
• Import button in Menu | Select Calendars now allows full navigation through all folders outside of Scoped Storage as well as all folders inside the Pimlical folder in Scoped Storage (previously, it was hard-wired to the Pimlical/ExportedCalendars folder, and the filenames were not sorted). 
• Fixes issue of not setting the CreationDate field in a newly created contact.
• Includes potential fix for odd (and relatively rare) issue whereby the Event Selection List shows ancient events, even though underlying view shows correctly (typically only after Android OS has absconded with all or part of Pimlical's data).
  

• Adds a simple File Manager menu option so that a Pimlical user can navigate throughout all of the filing system, except for the Scoped Storage area of Apps other than Pimlical. A file can then be selected at which point a dialog appears offering options to Copy, Rename or Delete the selected file. In the case of Copy, the file navigator appears again (this time only listings folders) so the destination folder can be selected for the Copy. In the case of Rename, the user can change the filename and then tap the Rename button. To delete the file, just tap the Delete button. A confirmation dialog will appear if the destination file for copy or rename already exists. Tap the Done button to exit the File Manager, or press the Back button at any time.There are buttons in the File Navigation dialog to quickly move to the root of the filing system and to the Pimlical folder in Scoped Storage (otherwise, you can't even navigate to that folder!).

• Adds a Root Folder button to the File Navigation dialog (used in commands like Set Link to File) to quickly reach the root of the filing system (normally something like /storage/emulated/0/). Also adds a Done button to exit the File Navigation dialog, and the legend of the Pimlical button has been changed to Pimlical [SS] to more clearly indicate this is the Pimlical folder in Scoped Storage.
• When installing a new version, Pimlical now consults a table of menu items and the associated versions they were introduced on and if there is match AND if that menu item is not currently bein g displayed, the menu item will be automatically added at the end of the currently displayed menu items (Preference: MenuCommandsAndOrder) so that it's forced to display. This is only done one time on the first run of a newly installed release.
• Tightens up the menu row height so more items can be displayed on the screen - on most contemporary phones, all the current menu items can display on a single page. Note that you loosen up the display by increasing the preference: MenuTextSize.
  

• Fixes issue of crashing when scrolling through entire System Section of Preferences (a test preference in a Beta Preview was inadvertently left in the program).

• Avoids creating the PimlicalDebugInfo.log file when the preference EnableDebugLog is set to False (previously, it would create that file for certain specialized logs even though that preference was set to False). Note though that if the file already exists, the logs may still be added, so delete that file if present and it won't get re-created with this release.

• Adds a Delete button to the Menu | Restore Everything dialog, so that backup copies can be deleted from Pimlical. Also includes the size of the backup (in MB or GB) so that the approximate space used by backup copies can be assessed, and removes unnecessary re-read of calendar after doing a backup (that's only needed after a restore). Also includes count of files copied or deleted at conclusion of file operation. Also now requests confirmation for Restore (and Delete) after backup copy has been selected (previously requested confirmation before even checking to see if there were any backups available for restoration or deletion).

• Fixes new issue in V-4.0.32 of not setting the correct exception date when an instance of the series is moved to a different day (it was picking up the instance date from the new date set on the instance, not from the original date of the instance.)
• Fixes erroneous error file (Count of Missing Items: 0) which was not testing for no missing items and skipping the creation of the error file.
  

• Fixes a new issue in syncing memos - under some conditions, an error file would get generated and some memos might not get synced properly from the Dropbox Server.
• On dialing a number (or sending SMS) if there is no vertical rule (|) character present (added in V-4.0.30 to truncate phone number at that point), Pimlical now processes the phone number as it did previously (allowing: 0-9 + - {space} . # * ( )
• Another fix for the issue of editing an instance of a repeat series in a different timezone that also got shifted to a different day - the instance was not properly picking up the original date/time/locale of the repeat series itself.
• Works around new restriction in AOS-14 that could cause a hidden ANR (Application Not Responding) error when Pimlical was attempting to get alarms rescheduled in the background and the device was unusually busy or the calendar was unusually large AND the device was running Android-14. Pimlical is now launched as an App to reschedule alarms after the device is rebooted (you can disable that behavior by setting the new Preference: launchPimlicalOnBootUp to false (default is true) but if you do that, alarms might not get rescheduled until you manually launch Pimlical).
• Restores the functionality of the menu items Find All Items Linking to This in the Contacts and Memos section (a recent update to the Android OS broke this functionality completely, so it had to be rewritten to work with the latest version(s) of the Android OS).
• Fixes an obscure issue of tapping the UPGRADE button in menu | about very quickly (before Pimlical has refreshed the licensing information) which could result in an erroneous complaint that the subscription was not valid.
  

• A new preference: DownloadFolderFilePath can be optionally set to provide an alternate path to the Downloads folder. If this preference is empty (the default value), Pimlical uses the "External Storage Directory" + "Downloads" to locate the Downloads folder (this is typically something like /storage/emulated/0/Downloads). This same preference is also now in Pimlical/Desktop. Note that to access a folder off the root of the filing system, you would need to include that External Storage Directory string (see the File Path displayed in Menu | About).

• Fixes issue with the alarm Preference: AlarmSoundRepeatCount. It is documented to be the number of additional alarms that will sound for an event if the Alarm Dialog is not acknowledged. However it was functioning as the total number of alarms that would sound. If you set this preference to 0, the alarm should (and will now) sound once and that's it. After the SecondsToAutoSnooze preference elapses, the alarm dialog is removed from the screen. So a value of 0 for AlarmSoundRepeatCount effectively disables the autosnooze feature. A value of 1 would mean that the alarm is autosnoozed just once (for a total of two alarms - the original alarm and one snoozed instance).
• Fixes a relatively new issue: if an exception is made to a repeat series in a different timezone that results in the displayed instance being on a different day from the day it would be displayed on in its native timezone, the exception date was wrong (it was set to the date of the displayed instance, not the date of the exception in its native timezone). This used to work, but got broken by some code introduced to work around a bug in the Palm OS Desktop(!) - the code having been subsequently copied from Pimlical/Desktop.
• Includes line of code to possibly address odd issue of Event Selection List sometimes showing raw template data rather than event data.
• Adds leading 0 to one-digit month in the Menu Backup Everything folder names, so backups sort better.
• Fixes a potential UncaughtExceptionError that could occur at the conclusion of a Restore Everythiing command.
• Fixes a cosmetic issue that if command Find Items In Group is issued after a Find command that was searching for text, the search string would not always get cleared out and could appear in the Event Selection List title.
• Fixes a significant, new problem in menu | Restore Everything command when restoring from a date/time-stamped file (i.e. from a folder within the /PimlicalBackups folder) - not all files were getting properly restored, and the folder sometimes contained a copy of itself.
  

• When dialing a phone number or using SMS, all characters in the phone number field are now used, but a vertical rule (|) can be used to strip out all remaining characters in the field (so 830-456-3145 | x-245 would result in the vertical bar and the x-245 being stripped out (previously, only selected characters would be permitted, but that was a bit too restrictive).
• Avoids generating logs to PimlicalDebugInfo.txt file from floating advances. and some notifications.
• About Dialog now includes brand and model of phone (useful when user just sends screenshot of About dialog rather than provide info via EMAIL TECH SUPPORT button).
• Fixes issue that if an iCalendar event is imported with an ORGANIZER field, but no email field for the organizer, P/A was crashing with a Null Pointer Exception Error.
• Forces re-read of preferences and main calendar after Menu | Restore Everything completes which should remove the need to force-stop P/A after this menu item is invoked.
• Fixes issue that if menu is not taking up the entire screen, and user taps outside of the menu to dismiss it, under some conditions, the Fling gesture might get temporarily disabled.
• Changes legend in Menu | Help | About from Purchase Subscription to Purchase Another Subscription if the user currently has an active subscription.
• Preference AnimateTodaysDate has been deprecated (no longer works due to interference from some odd Android OS update). It's been replaced by two preferences:  TodayLccatorBackground - if 0 (default value) the feature is disabled, otherwise, this is an Alpha transparency value from 255 (opaque, white background) to 1 (fully transparent background), with 210 being a reasonable value to see this feature work. The faded background is displayed for a period of milliseconds set by the preference: TodayLocatorDuration - default value is 750 - or 3/4 of a second which may be about right for most users.

• Yet another approach to fixing an obscure issue whereby Pimlical gets launched twice when an alarm goes off, which can then result in the alarm not sounding and displaying properly.

• Another approach to fixing an obscure issue whereby Pimlical gets launched twice when an alarm goes off, which can then result in the alarm not sounding and displaying properly.
  

• Fixes an obscure issue (which may be new with AOS-14) whereby Pimlical gets launched twice when an alarm goes off, which can then result in the alarm not sounding and displaying properly.
  

• Fixed issue of icons in the Find dialog not being redrawn properly when the Find Dialog was subsequently refreshed.
• (Changed path Definition for RAW_DATA_FILENAME - this is just an internal diagnostic tool).
• Speeds up processing of license information with improved algorithm, extends duration of temporary license.
  

• After RestoreEverything command, Pimlical now forces a re-read on the restored user and system preferences, as well as a re-read on the calendar, timezone settings and Icon Archive (previously, those might not have been fully reset). The conclusion dialog also mentions that a Force-Stop might be needed to get a completely "clean" launch (hard to know whether that's actually required, but definitely do that if something does not seem to have been restored properly).
• Fixes an obscure issue where User and System Preferences might not be refreshed after life-cycle relaunch of Pimlical.
• Changes the preference NumberOfMenuRows default value to 20 from 2. It seems a lot of users were unaware they could fill the entire screen up with menu items. If you don't like that, just set that preference back to 2 (Only changes this on a clean install).
  

• Avoids checking for an internet connection PRIOR to seeing if it is a day on which a check should be made for the availability of a new software release.
• Avoids a spurious File Not Found message when downloading an APK file for installation.
• Fixes instability issue when Widget was installed and Pimlical was invoked after a Widget Refresh.
  

• Fixes UncaughtException issue in installing upgrade. Also changes criteria for displaying Beta Preview button in Menu | About after tapping Upgrade button (Beta Testers have been updated on this change).
• Now displays version number in Menu | About without the -D for Beta Preview releases.
  

• Adds new Backup Everything menu command (remember that you may need to edit the preference: MenuCommandsAndOrder to make sure it is visible in the menu list). This does the exact reverse of the file migration performed when upgrading from V-3.x to V-4.0 - namely it copies ALL files and folders from the Pimlical folder in scoped storage to the Pimlical folder off the root of the filing system (creating it if it does not exist). Any files with the same name as those being copied are pre-deleted first from the destination Pimlical folder, but any other files there will be preserved. Destination folder may be modified by Preference below:
• Adds new preference: BackupEverythingUsesDateTimeStamp. Default is False (which sets the above behavior for Backup Everything command. If set to True, the backup folder is named BackupEverything_YYYY-MM-DD_HH-MM-SS and that folder is placed inside a root folder with the name PimlicalBackups. This allows multiple backups to be preserved.
• Adds new Restore Everything menu command (again, remember that you may need to edit the preference: MenuCommandsAndOrder to make sure it is visible in the menu list). If there is a PimlicalBackups folder, it displays all the available backups in a sorted selection list. If there is only one available backup (normally the root folder: Pimlical/, that is used for the command.
• Upgrade button in menu | About now automatically downloads the current official release and installs it on the device. If Debug Mode is set, a third button is displayed which will download the latest Beta Preview release.
  

• Fixes new issue in V-4.0.x on import of iCalendar file that if  END:VEVENT is followed on the next line with BEGIN:VEVENT, the event gets skipped (possibly only importing every other event). If there is a blank line between events, the problem is not seen.
• Fixes obscure Exception Error on iCalendar import if import is done before anything else in Pimlical.
  
• When maintaining the Audit Trail, the new feature of documenting every single change made in the Edit Dialog was overlooking the change in deleted status (when deleting or undeleting an item).
• Includes addition to Manifest which should allow Pimlical Calendar to be listed as a target calendar app in any other third party app that wants to invoke Pimlical Calendar.
• On the initial SETUP when upgrading from V-3.7 to V-4.0, a progress dialog with a spinner is used to make the user more comfortable that something is indeed happening.
• The Menu | Archive function now runs in a separate thread (to avoid OS complaint when archiving a really large number of records, or operating on a slow device) and includes a progress dialog with a spinner.
  

• When a widget refresh is being aborted, the [W] icon in the Android status bar is now removed (previously, it would be left displaying).
• Fixes new issue of UncaughtException error in setting an icon on a filter, caused by switching from Text button to Image button in Icon Selection Dialog.
  
• Fixes issue that when the Widget filter was missing, and the Widget was installed or refreshed, the Widget was just using the default filter instead of automatically recreating the default Widget filter.
  
• Fixes issue of the Tu command (toggle display of untimed events on/off) being non-functional if the current filter was set to display ALL events (as long the filter was filtering something, it worked fine in prior release). 
• P/A can now read the imagePath for an event set in Pimlical/Desktop and 'fix' it in such a way that images can be displayed on both platforms. Old image paths up to and containing the /Pimlical folder are stripped and the remaining path appended to the main user path. Note that to have this work properly, the images should either be in the Pimlical folder, or (better) in a separate sub-folder of the Pimlical folder (say Pimlical/PimlicalImages). And of course you would have to manually ensure that those two folders in P/A and P/D were kept in sync (future releases might add the capability to keep those folders in sync with each other on DirectSync or AutoSync).
• Fixes new issue in V-4.0.x on import of iCalendar file that if  END:VEVENT is followed on the next line with BEGIN:VEVENT, the event gets skipped (possibly only importing every other event). If there is a blank line between events, the problem is not seen.

• Removes the permission restriction for using Exact Alarms (previously limited to SDK level 12, meaning that it was not being requested in AOS-13/14) - most likely the cause of a few missed/delayed alarms that some users were seeing. This was a potential PlayStore conflict that no longer needs to be addressed in V-4.0 (but will be an issue in the V-3.9, Playstore-compliant version).
  

• Fixes problem of the ERROR and LOG file buttons in Menu | Debug not being re-enabled after new error files appear (previously required force-stopping Pimlical to refresh the buttons.
• In the Month and MultiMonth views, the preference ShowDownArrowInMonthViews now also applies in the case where there is no text at all that can be displayed in a cell (previously, this preference only applied to the down-arrow used to show there were more entries on that day that were not displayed).
• When an icon or graphic associated with an event is missing, rather than create an error file, there is now just a log to the PimlicalDebugInfo.txt file (created when EnableDebugLog preference is set to true). Previously, error files were created every time the event was displayed (and with graphics moving around, and the ability to create new icons, such error files were proliferating in those cases).
• Fixed several issues relating to a totally clean install with no prior Pimlical folder - Trial Period test was failing, Subscription items were not available during trial period, error files were being generated, etc.
• Corrects issue of invoking license lookups too frequently.
  

• Rearranges items in the About dialog to display better on lower resolution screens.
• Fixes problem in File Navigator when selecting a Directory (such as importing directory of icons, or exporting memos to a directory) - the new Pimlical button overwrote the Select Directory button so there was no way to select a directory.
  

• Fixes a new issue from V-4.0.16 whereby the new preference values were triggering a false error on valid subscriptions because the licensing information had not yet been read.  Also, now resets any preferences requiring a subscription back to their default value if there is no subscription.

• All of the new features since last official release have now been designated as Subscription Only features. 
• Fixes UncaughtException Error caused by changing button in icon dialog from a regular button to an image button (from "Cancel" to a RecX graphic).
• Fixes a typo in the default user preferences where "Recent Updates}Past Alarms" appeared instead of "Recent Updates|Past Alarms" - probably only those users who were resetting their user preferences would have seen this problem (created an error file complaining about an undefined menu item).
  
  

• Icon Delete feature is now operational (long-press icon in the All Icons display and tap the DELETE button). This does not delete references that you may have in events, templates and filters (if an icon is not found, a ?? icon is displayed instead) (Subscription only)
• Add icon feature now automatically assigns the next highest Icon Key# to an icon if there is no embedded IconKey# in the filename, and renames the file (so a filename like: GarbageCan.png becomes something like 465_GarbageCan.png).
  
• Icon Dialog now has a Backup/Restore button to backup and restore the IconArchive.dat file. Add/Delete/Backup/Restore Icon features all Subscription only.
• Adds new preference: UseCustomFieldForSetLink which has a value from 0 (default) to 4. The default value of 0 preserves the current behavior of putting the link in the note field. If the value is 1-4, then the link is placed into the corresponding custom field (Custom1-Custom4) (Subscription only).

• Menu | About now refreshes itself after the possibly changed licensing information has been updated (so you will see it blink a moment after it appears as it reads the new information). This avoids the issue of having to go back and forth more than once to menu | About to see the updated licensing information.
• The Expiration Date information is now written on a second line since on some devices with low resolution or very large text, the information was overwriting the label field.
• Fixes issue with using boolean && or || with an expired subscription (dialog was not displayed and program was hanging).
• In the file navigation dialog (used by Set Link to File, Image button in Edit Dialog and [+] button in Icon Dialog, Cancel and Pimlical buttons have been added - the latter goes directly to the Pimlical folder in scoped storage (necessary to sidestep a bug/flaw in Android OS most likely involving a failure to recognize ALL_FILES_ACCESS - the file navigation dialog can't get to {root}/Android/Data from {root}/Android to get to the Pimlical folder (!)).
  

• When handling a new purchase, Pimlical will now use the latest expiration date of all the cumulative purchases (so if there was a prior order with an earlier expiration date, it will always use the order with the latest expiration date).
• Fixes a new issue in V-4.0.13 where there was a benign error condition that would, under certain special conditions, which included debug mode being set, slow down the read of the local calendar, and log multiple errors into the audittrail file.
• Fixes issue in Menu | About on an expired subscription where the license was still valid and Pimlical was displaying the note to contact Tech Support in regards to the ReferenceID - the message is now properly hidden in those circumstances.
  

• Caters to a minor change in the Licensing/Subscription feature by distinguishing between old orders and new orders using a subscription purchase.
  

• When deleting a category, now scans all preferences that might reference that category and identifies them (subscription only).
opup
• Adds new Action tag: ALWAYS HIDE which always hides the event. It will set the Show/Hide latch in the Event Selection List so it can be detected (this would be primarily used on shared calendars where one person does not want to see the other person's specific event) (subscription only).
• Implements Action tag: NO ALARMS which always causes any alarm set on the item to be ignored (this would be primarily used on shared calendars where one person does not want to hear the other person's alarm on a specific event) (subscription only).
• Adds menu command (Past Alarms) to list all of the alarms that have triggered since the start of ttoday. Note that this would not include a "missed" alarm (for example, an alarm that would have triggered but didn't because your phone was completely shut down, or because Pimlical was Force-stopped and not relaunched), (subscription only).
• Allows modification of the Icon list: an ADD+ button can (on a short tap) add a single icon from a graphic file (and updates the RecentIcons list, or (on a long-press) add all graphic files in a directory (or a single file, without updating the RecentIcons list). A DELETE button will be implemented shortly in following release when viewing all icons and long-pressing an icon (subscription only).
  

• Subscription feature now identifies the feature that is not available and when appropriate suppresses the display of the purchase dialog (but will write an error file, so the condition is known).
• The feature to toggle untimed events on and off now properly sets the Show/Hide latch if the Event Selection List is brought up while untimed events are being hidden.
• The Menu | Recent Updates command now displays the proper title when the events are being displayed (previously displayed Find and possibility a filter string).
• Fixed obscure issue in menu | Recent Updates when issued immediately after clean launch (or force-stop) of Pimlical which would end up unexpectedly and erroneously displaying items at the top of the list because they never had a ModificationDate set (typically items from Google or other third party calendars).
• The Action Tag FloatDays now allows an alternate (and easier to remember!) syntax where days of week are specified with the first 3-letters of the day of the week (such as FloatDays: Mon-Tue-Wed). The hyphen is not required, but makes it more readable (only a hyphen can be used as a separator).For backwards compatibility, the original syntax of using a numeric string (where 0 = Sunday, 1 = Monday...) is still supported.
• When using Preferences | Restore | Reset, resetting the IconArchive file now first invokes the backup procedure on the file (creating .bk1, .bk2, etc.) (for diagnostic or recovery) and also renames the RecentIconsList.txt file (which has the list of recently accessed icons) to RecentIconsList.bak.