This section below is for Users who want to know every single issue and fix that have been applied in all prior interim releases. It is always a good idea to read the latest release notes on the version you are now installing and any prior versions you may have skipped over when upgrading.

New Features in V-4.x of Pimlical/Android (new features since V-3.7.x require a subscription)

• Switches to the use of Scoped Storage for better security and compliance with Android-11 and later (...android/data/com.pimlicosoftware.PimlicalA/files/Pimlical). This version will automatically move all your files from the old {root}/Pimlical folder to this new folder.
• Icons can now be added (individually, or all icons in a folder) to, or deleted from, the Icon Library directly from the Icon Dialog (no need to perform this step in P/D and then create a compatible icon collection for P/A and move it to P/A). Also includes multiple backup/restore function for IconArchive.dat file. Both P/A and P/D now use the identical IconArchive.dat file in V-4.x.
• Restores the full-page Alarm Dialog on Android-10 and later (see alarm documentation for details - remember you have to grant explicit Android OS permission to display full screen over other App dialogs).
• Find In All function now quickly scans all local calendars and produces a list of all matches in those calendars (makes it very convenient now to locate an event in the Archive calendar, etc.).
• For repeat events, you can now set a start/end date range for exceptions and have Pimlical automatically insert exceptions for all instances of the repeat that lie within the date range.
  
• The Widget has been completely rewritten and is now part of the main Pimlical App (there is no separate Widget App). Note that you likely need to remove and reinstall the Widget when upgrading to a new version of Pimlical/Android. Widget has option to avoid re-read of database by both P/A and the Widget, to greatly speed up refresh (and most users can take advantage of this - set ForceCalendarReadAfterWidgetRefresh to False which is the new default setting).
• An internal File Manager now allows access to Pimlical's Scoped Storage as well as all other files and folders outside of the Scoped Storage folders of other Apps, and offers Copy/RenameMove/Delete/Open/Share options for the files.  Also accesses files on Remote Server.
• The Debug menu commands to view Error files and Log Files now include a DELETE button to conveniently delete all of them.
• New Backup Everything and Restore Everything commands make it easy to backup and restore ALL local databases, preferences, etc. (Remember you might have to edit the preference: MenuCommandsAndOrder to see those new menu items). Also, there's a special preference to create multiple, date/time-stamped backups if you wish. You can also set Pimlical to automatically perform a BackupEverything on a schedule, and also delete the oldest backup to avoid using too much storage. BackupEverything can also use any available Remote Server to do the backup to and can also be automatically triggered at the end of the floating advance (when the phone is typically not being used).
• A new Status type of Absent has been added to cover cases where an event is still being held, but the user won't be attending it. The event is struck-through and any alarm is removed. New popup command Toggle Absent can also change to/from that status in an Event Selection List.
  
• The Upgrade button in menu | About can now automatically download and install the latest upgrade to Pimlical.
  
• A new preference can be set to automatically reset AutoSync Authentication prior to invoking AutoSync. And the AutoSync command can now be put on the Command bar.
• AutoSync can now use a Remote Server (USB hard drive or key on Router USB port, or any internet web page to which user has access rights).
  
• A new preference ForceFloatsToBeUntimed (like existing ForceTasksToBeUntimed) allows all floats (including timed floats) to appear at the top of the list of events for a day.
• A new preference item for the Command Bar (Tu) toggles between displaying and hiding all untimed items (if you have a lot of floats or tasks, this makes it easy to view just the timed events).
• Adds new Action Tags to always hide an event, and to suppress alarms on an event (useful when handling shared calendars).
  
• Several other new preference settings have been added (see entire Revision History since V-3.7.110 or peruse the online Manual section on preferences.
• 
  

• 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 a Remote Server 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. 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. The user name and password will be the same as what you use to log into the Remote Server, 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.
  

• Fixes a licensing issue (which has always been present on the Direct Download) namely that if there is no WiFi (or cellular data) connection it was resetting the license status to NOT LICENSED, whereas it was supposed to preserve the existing license status. If running a trial period though, a check is made that the trial period has not expired (and if it has, the license condition is reset to NOT LICENSED). It's also possible that the prior code in Pimlical was  concluding that a connection was not available if a user only had a cellular data connection to the internet (in theory (meaning Google supplied the code), this version now checks for an internet connection via WiFi OR a cellular data connection).

• Adds ability to import a VCF file shared from another application (subscription only).
• Handles the import and export of Tasks (ToDo's) - by implementing BEGIN:VTODO and END:VTODO tags (which parallel BEGIN:VEVENT and END:VEVENT) as well as the optional DUE tag (subscription only).
  

• Sidesteps another case where an initialization issue could cause Android to fail to properly launch Pimlical (and this could potentially cause an alarm to get lost).
• Implements Subscription Management (but licensing database has not yet been updated for any subscriptions).

• Removes the option to set the date to None, when using the popup command Change Date (since you cannot remove the start date from an event or task).
• The Contact Tech Support button now appears as Email Tech Support (to match P/D), and now, like P/D copies all the Tech Support info to the clipboard (so if there is no primary email address, you can just manually open up an email and tap Paste to provide the requisite information).
• When tapping on the icons to copy phone/email/address of a contact (in Contacts View), phones with Android-13 will briefly display buttons to handle Share and Nearby Share.
• 
  

• Fixes issue on Samsung phones which share contacts without specifying a VCF extension in the share file. The fix should take care of any anomalies on other phones as the test now is the actual contents of the file.
• Fixes new problem on adding meeting attendees which apparently got broken some time ago (but apparently no beta tester was using that function), which was causing an UncaughtException error.
  
• Adds missing colon to the UID tag when Pimlical is exporting a contact in vCard format (tag was causing an import error).
• Avoids logging an error file from Alarm routines, when user hits a button at the PRECISE instant that Android has finished speaking an alarm but before Pimlical tries to sound the alarm sound.
  

• Fixes issue with creation of spurious error file: onUtteranceCompleted.... Exception error from Android OS with Media Player.
• 
  

• Fixes issue (that appeared some versions ago) where the contacts app was not properly picking up a newly-assigned photo in the Contacts Edit Dialog. Also, photos are limited to one half megabyte due to internal Android OS limitations.
• The Menu | Debug | View Error Files function now only attempts to display up to 25 error files (but still allows you to delete all of them). This caters to a relatively rare situation where hundreds (or even thousands of error files) can get generated when Debug Mode is set (since Debug Mode appends the date/time stamp to create a unique filename). Also, only the first 5k of the file is displayed (to avoid issues with multi-megabyte log files).
• Changed messages in Menu | Debug | View Error Files and View Log Files to reflect that the Delete button now manages both cases.
• Changed the extension for the files: Pimlical_Android_AuditTrail, PimlicalDebugInfo and WidgetDebugInfo from TXT to LOG, so that you can now easily delete those files from the Debug menu's View Log Files function.
  
• On initial entry to Menu | Debug, now disables (grays out) the buttons for View Error Files and View Log Files if there are no files present of that type.
  
• Includes preliminary logic to manage subscription purchases (status now displayed in menu | About) - for now will just show N/A.
• The Menu | Debug | Refresh Widget function now dismisses the Debug Dialog and delays for a few seconds the refresh of the Widget (otherwise, the widget won't refresh because the Debug Dialog is open).
  

• Fixes yet another new issue (appeared in V-4.00.04) as side effect of fixing sort issue in contacts: the Recent List was still not properly preserving its order properly.
• Sidesteps a problem with the Android OS and Pimlical failing to launch after it had been inactive for a period of many hours (for example: first tap on the launch icon in the morning would not launch Pimlical). This potentially could cause an alarm to be missed too.
  

• The Menu | Debug | View Error Files item now includes a button to delete all the error files in the Pimlical folder (Subscription only).
  

• Fixes new issue (appeared in V-3.8.20) as side effect of fixing sort issue in contacts: the Recent List was not preserving its order properly.
• Fixes issue of Widget freezing if it is invoked before Pimlical was ever launched, or after Pimlical was force-stopped (and not relaunched).
• On vCard import (or share), multiple category selections for contacts are now permited if the preference MultipleCategorySelection is set to true (otherwise, only the first category is used). Previously only the first category was preserved, regardless of that preference setting.
• On iCalendar Import, Pimlical now allows multiple calendars (i.e. sections containing BEGIN_VCALENDAR and END_VCALENDAR) to be imported (previously, Pimlical stopped reading the file when it found the first END_VCALENDAR).
  
• Fixes issue with preference: AlwaysResetBeforeAutoSync that was not being properly handled when set to False (default is True). When set to False, Pimlical was not re-submitting the saved login credentials. For some period of time (somewhere around an hour or two?), Dropbox does in fact allow the saved login credentials to be reused (thus avoiding need to sign back into Dropbox). Most of the time though, users will likely leave the preference set to its default value of True.
• Importing of contacts through share now occurs in two steps - first, a pending file is written (or appended to) locally Pimlical/PimlicalContacts/vCardFileToImport.vcf, then, when the contacts database is next read, the pending file is imported and renamed with a .BAK extension (for diagnostic purposes). There are separate messages covering these two steps. If multiple contacts are shared before the contacts database is read, then all of the shared entries will be imported when the database is next read.
• Fixes a new issue (from V-4.0.01) whereby the Temporary Sort of Contacts was lost (the permanent sort was overriding any temporary settings). The Temporary sort only stays in effect while things are not changed (i.e. if you switch to Recents list or Favorites, for example, the permanent sort is re-applied). For example, you normally sort by last name, but want to find someone whose first name you recall, but not their last name - sorting temporarily on first name and using the GoTo button makes it easy to find that person.

• Fixes new issue of missing Read Calendar permission for Android Calendars (Inadvertently removed in V-4.0.02 owing to suggestion that since Pimlical had Write Calendar permission, the Read Calendar permission was not needed, but that was not true).
  

• For Direct Download and Amazon versions, includes automatic migration of contents of old Pimlical folder into new location in Scoped Storage (when Pimlical recognizes that there's a non-empty {root}/Pimlical folder, and an empty {root}/Android/data/com.pimlicosoftware.PimlicalA/files/PimlicalA folder.
• Fixed an issue of generating an exception error on a clean install (due to a change in V-4.0.01).
  

• Updated Version number in preparation for official release.
• Changes the Initial Install dialog that appears if the Pimlical folder in scoped storage is empty (meaning it's either a new install or the user is upgrading). Adds a HELP button with a direct link to the migration document on Pimlico's website.
  
• Now implements UID field of vCard standard (not clear why this was removed at some point in the past?!). This should permit a Share from a contacts App (that is properly providing the UID field) to overwrite an existing contact rather than duplicate it.
• Improved messages surrounding AutoSync to indicate WHY it was being deferred (such as some other lock file found in dropbox, or dialogs were open in Pimlical, etc.)
• Includes fix for very obscure (and quite possibly irrelevant) error of interpreting phone labels using the type field from email when reading Android Contacts.
• Included some cosmetic fixes for debug logging, as well as included some additional diagnostic logs.
• Included some internal changes that might prevent Pimlical from thinking that a launch of Pimlical very shortly after an alarm had triggered and been snoozed/dismissed, was in fact a launch to display the Alarm Dialog.
• Fixes flaw that when asking for permissions, after all the permissions have been granted, Pimlical was not being automatically relaunched as it should have been.
• PimlicalDebugInfo.txt file (created if EnableDebugLog is set to True) now includes ALL the information in menu | About, since too many users requesting tech support fail to provide this information(!). Also includes brand and model of Android device.
• Fixes a new issue in properly recording the preference ContactSort when it is changed by long-pressing the Sort button in the Contacts section of Pimlical/Android (the preference type had been changed from an integer to a StringList for better readability many versions ago, and that code had never been updated, causing a GetArrayIndexFromString error file).
  

• For the Initial Install Message (when Pimlical folder is empty), the OK/CANCEL buttons have been renamed to CLEAN INSTALL and UPGRADING, as too many people don't read the message and just click on OK, thinking Cancel must mean you don't want to do the normal thing(!).
• Preference: NumberOfBackups has been changed to 9 (prior value was 5). These take up so little room, and there have been several cases, where users would have been better off having the maximum number of backups.
• Fixes two other cases where bugs in the Android OS (trying to invoke the widget when it was not installed) ended up creating the WidgetDebugInfo.txt file (if EnableDebugLog was set to true). Pimlical is endeavoring to not create that file unless the WidgetIsInstalled preference is set to True.
• If EnableDebugLog is set to True, the setting of the Floating Advance Alarm is now logged into the PimlicalDebugInfo.txt file.
• When the Widget is removed from the Home Screen, Pimlical now attempts to force the OS to cancel the periodic work request to refresh the Widget, because the OS does not even bother to check subsequently to see if the widget is installed before invoking the work request (!).
• The error message about "Mismatched Versions" when syncing versions that differ by Major or Minor versions has been substantially toned down now to just Information, as in fact this issue has yet to arise, and with the latest database design, it's most unlikely to ever be an issue.
  

• The ContactSort preference is now written into ALL custom preference files (not just the current preference file as was previously the case). Also the preference is set in BOTH the Default.txt and Default.dat files (previously, only the cached DAT file was updated, which could possibly cause the sort order change to get lost).
• The rule for handling a past-due floating event with a display date in the future has now been modified. Previously, a past-due Float would always appear in Today's schedule, regardless of the Start date. This has been refined to handle all six possible cases:
     Case 1: Has due date in the past, start date in past - DISPLAYS TODAY (repeat status ignored)
     Case 2: Has due date in future, start date in the past - DISPLAYS TODAY OR if a repeat, on Next Repeat Instance after today
     Case 3: Has due date in the past, start date in future - DISPLAYS on START Date (repeat status ignored)
     Case 4: Has due date in future, start date in future - DISPLAYS on START Date (even if due date is earlier)
     Case 5: Has no due date and start date in past - DISPLAYS TODAY OR if a repeat, on Next Repeat Instance after today
     Case 6: Has no due date and start date in future - DISPLAYS on Start Date
  Some of the behaviors are the same, but the program separates out these six cases in case they need to be modified in the future.
• If a Floating event (or Task when the Preference LockDueStartDateOnTasks is false) has a due date that precedes the Start Date, a brief "Toast" message will appear alerting the user to this condition (it's unusual to want this, hence the warning when updating or creating the float).
• Incorporates an internal change that may reduce battery usage (prevents any activity when running in background)
• Avoids creating the WidgetDebugInfo.txt file (when preference EnableDebugLog is set to true) to log the Android OS error of erroneously trying to invoke the Widget when the widget is not installed (apparently the Android OS is using its own erroneous test to determine whether the widget is installed or not!).
• Fixes a problem in the new V-3.8.19 feature to track ALL changes made in the Edit dialog, which was causing an error file to be generated under some unusual conditions.
• When removing a snooze on an alarm from the Menu | View Upcoming Alarms list, the snoozed item is now removed from the list (previously, the item remained in the list, even though the snooze alarm had been removed).
• Fixes issue that under some conditions when first entering the Contacts Activity, and immediately switching say from Favorites to All, the contacts list would not be properly re-sorted.

• When the preference MaintainAuditTrail is set to True, Pimlical/Android now documents every single editing change made in the Edit Dialog (previously, only the addition of new records and a few other changes from popup commands were logged - subscription only).

• When you exit out of Preferences, Pimlical will now ALWAYS check that (a) Battery optimization has been turned off, and (b) that Pimlical has permission to schedule Exact Alarms. In AOS-13, Pimlical can no longer demand these items because google will yank the App from the playstore. So it can only REQUEST  these permissions and hope the user grants them because without them, alarms may cause exception errors, may not go off at the right time, the widget may fail to refresh etc. - so don't blame Pimlical for this, go complain to Google about this silliness ;). These two permissions ARE also requested on the launch of Pimlical too, but ONLY if the  primary permissions (calendar, contacts, phone state) have not yet been granted. Finally, these two permissions are checked for whenever the ShowHelpOnStartup Preference is set to True (typically when the App is first installed).
• Fixes issue of not properly indicating that the Widget was not installed in menu | About when the WidgetIsInstalled Preference (which is usually set internally by P/A) was set to False (it was not fixed in V-3.8.18 as previously indicated)
• Fixes issue that if the only change made in the Edit Dialog was to change the Attendee Role of a meeting, that change might have been lost.
• Fixes problem with memo and contact linking that resulted from a further side-effect of the changes made in V-3.8.17.
  

• Fixed a side effect of a change in V-3.8.17 regarding Contacts and Memos which, when invoked from Menu | View/Edit Contacts or Menu | View/Edit Memos was not properly returning to P/A as expected.
  
• Changed the default setting of preference: AlwaysResetBeforeAutoSync from False to True (because that's the most likely setting users will want with this new preference).
• Removes automatic request for ignoring battery optimization as the Google Police have now stated that Apps targeting SDK 33 or later (which is required for listing in the Playstore) that request this optimization will be yankedfrom the Playstore. P/A does ask the user on initial install to review the Battery optimization settings (that apparently is still "legal").

• Tiny change to try and get Widget Icon to display when Widget Refresh was initiated by Android OS's Periodic Work Request.
• Fixes cosmetic (confusing) issue in the appearance of messages, logs, modification/creation dates in memos and contacts of appending the designation (UTC) to the date and time. In those cases, the date/time had already been adjusted to the current timezone, so the information that the original date/time had been stored in UTC was causing confusion that the displayed date/time were in fact still in UTC. At no time was there any internal confusion in P/A with regards to the handling of these date & times.
• If the Memos or Contacts button in the widget is tapped and Pimlical has to re-read preferences and the main calendar database (either because AOS has absconded with PA's memory, or because the widget had just refreshed), it will now properly proceed to display the memos or contacts (previously, it would re-read preferences and the calendar, but then just display the calendar and you had to then tap menu | View Memos, or View Contacts to proceed).
• Now avoids logging the error/status message: PimlicalCalendarWorker.doWork() ignored because OS says Widget is not installed which was creating the WidgetDebugInfo.txt file (only when EnableDebugMode was set of course). This message has now been moved to PimlicalDebugInfo.txt to avoid creating that other file.
• On launch, Pimlical now checks for an initial install before asking for permissions. When OK is tapped (or Pimlical is relaunched after migrating data to the new sand-boxed location), it will then ask for the appropriate permissions (depending on whether the prior version of P/A has been uninstalled or not).
• Restored the prior minimum refresh interval for the Widget of 15m (during the arduous attempts to figure out how to bypass all the bugs in the Android OS and get the widget to refresh reliably, it had been temporarily set to 16m).
  

• V-3.8.15 switched from using a "Full" Wakelock to a "Partial" Wakelock because the Full wakelock has been deprecated for quite some time and there were rumors that Android-14 was going to finally remove that alltogether. I had also heard that Apps requesting a full Wakelock might be removed from the Playstore (fuss over battery life). However, that change did result in the display screen not turning on when an alarm triggered. Fortunately, there is an alternative approach - namely to have the Alarm and Snooze dialogs themselves turn the display on. The delay is pretty inconsequential (if the database has to be re-read, that will occur while the screen has not yet been turned on, but that's actually preferable behavior anyway!).
  

• Adds Menu | Debug function to force the refresh of the widget (resetting everything and telling the Android OS to re-establish the periodic refresh of the Widget). If that fails to refresh the widget, remove and reinstall the widget.
  

• Changed the mechanism yet again for refreshing the widget in an attempt to find SOMETHING that works reliably with the Android Work Manager function.
• Corrects an UncaughtExceptionError that could occur when viewing the Upcoming Alarms List and using the Toggle Alarm command on a repeat task (note that this action has no meaning unless you set the preference RepeatTasksHaveNoExceptionsList to False -- the default is True).
  

• The minimum Android OS version supported has now been raised to 6.0 (previously it was intended to be backwards-compatible to V-4.1). The filename has now been changed to PimlicalA_os60_3_08_14.
• Another fix for the testing of whether the phone is active when an alarm triggers (and the preference: AutoSnoozeDuringPhoneCall is set to True). Previous code (supplied by Google) did not work properly.
• The widget will now refresh if an Event Selection List is displaying (previously, you had to be in a main view with no dialogs open for the widget to be able to refresh). Also, this change was actually made in V-3.8.12.'
• Made some changes to how the Wake Lock is handled on alarms as there has been evidence that recent AOS versions might have changed the way they handle Wake Locks (without documenting it). This might explain cases that we have seen where the alarm DID trigger P/A, but AOS then puzzlingly terminated P/A thus preventing it from continuing to display the Alarm Dialog.
• Made some changes in the way the Widget refresh was handled to try and avoid cases where AOS was not rescheduling the Widget Refresh (this was happening for no apparent reason).
• Made a slew of small changes to the Widget to try and address the issue of AOS "forgetting" to refresh the Widget (seemed to help, but not fully resolve this issue).
  

• Changes default Alarm setting for AlwaysShowNotificationForAlarm to False (previously was true) now that full-page alarm dialog is supported again (does not affect updates - this is just the default install setting that's changing).

• Adds new preference: ForceFloatsToBeUntimed which parallels existing ForceTasksToBeUntimed preference. When set true (the default is false), timed floating events are displayed as untimed (so you can have ALL floating events always appear at the top of the day's display, even though they are untimed. Note that this does not affect alarms set on timed events (which will still trigger at the expected time) (subscription only).
  

• Fixes a possible issue of snoozing alarms because a telephone call was in progress when in fact the telephone call status was incorrect.
• The preference: ForceCalendarReadAfterWidgetRefresh now defaults to TRUE (previously default was False). This is the recommended (but not required setting). If P/A is not displaying all events properly after a widget refresh, make sure this preference is set to True (if upgrading from prior V-3.8.x release, set this to True).
• Should address an issue of removing the alarm from an item (by deleting it, toggling the alarm, etc.) but still having the device wake up at the prior alarm time (nothing happens, no alarm is sounded, but there were cases where the device would power on mysteriously).
• When displaying the available backups for preferences, Pimlical now always tries to display ALL nine possible backup copies (previously, Pimlical only displayed the number of backups set in preferences - which could be the default value of 5 if preferences were corrupted and reset back to the default, resulting in the non-display of some potential backup copies if the NumberOfBackups preference had previously been set to a larger value).
• Creation and Modification Date/Time on advance reminders are now set to 00:00:00 on today's date (that way, they show the correct date on which they were created, but by using 00:00:00 as the time, there won't be any conflict when the reminders are created independently on other platforms - and which may be independently changed on those other platforms).
• Fixes problem in Tasks View of using a Template to create a new task, but displaying a blank screen when exiting the Edit Dialog (rather than properly displaying the updated Tasks View).
• Fixes an issue where the Widget might not be reading all the records in a Google calendar if the main P/A application has been terminated by AOS (AOS can legitimately terminate P/A, but that should not affect the Widget).
• Fixes an obscure alarm issue caused by AOS re-activating Pimlical from the "recents" list under conditions where AOS apparently fails to check if the activity is already running, which in turn can cause Pimlical to reschedule alarms WHILE the alarm dialog is open. If the Alarm dialog then auto-snoozes due to not being dismissed, the rescheduled alarm ends up being unexpectely auto-snoozed (so an alarm scheduled for say 4 hours in the future, unexpectedly gets rescheduled to fire in 10 minutes (or whatever the snooze interval is).
• Fixes an issue with permissions and AOS 13. This was causing installation problems on some devices, and could cause the strange, immediate closure of Pimlical after launch when Pimlical was newly installed (on a device that did not have Pimlical previously installed, etc.).
• If Pimlical finds that the widget has not refreshed in an interval that is twice the normal refresh time, and there is no apparent reason why that's the case, the widget refresh is automatically triggered (protects against the Android OS going to "sleep" on this for no good reason.
• Now allows the widget to refresh if the Event Selection Dialog is open but includes a check to avoid proceeding with any function if the Widget or AutoSync is active (since the widget would have invoked a different filter, etc.).
• Fixed issue of generating a couple of benign error files on a totally clean installation.
• Now requests (but does not require) permission to post notifications (AOS 13 no longer automatically allows Apps to post notifications - Pimlical uses this to indicate snoozed alarms, AutoSync Active and Widget Active).
• Now Requests (but does not require) permission to disable battery optimization. This is highly recommended (but not required because Google won't list Pimlical in the PlayStore if it says it requires this setting(!) ) - if permission is not granted, there may be problems in handling alarms, and refreshing the widget.

• Fixes some obscure issues involving the installation and removal of the widget (that could still end up blocking P/A from running).
• Fixed some interaction issues between the widget and P/A.
• Fixed issue of widget not running because some dialogs in P/A (esp. with filter edit) were not marked as having been dismissed.
• Fixed menu | Exit command to ensure that all dialogs were cleared (there's a flaw in the Android OS where a program can be terminated with the indication that a dialog is still open when in fact it is not, so if you get a complaint that the Widget cannot run because P/A has a dialog open, try menu | Exit to clear it - that's safer than doing a Force-Stop on Pimlical).
  
• The selection dialog for restoring preferences now shows the file sizes and dates of both the SystemPreferences.dat file and the user preferences (default.xxx).
• Fixes issue of not displaying a past-due, repeat floating event, that has a display date in the future.
  

• The command to toggle the display of Untimed Items on and off can now be put on the command bar (legend: Tu), which makes it conveniently accessible for quick toggling (previously, it was only available as a menu item).
  

• Fixes an UncaughtExceptionError in the Widget if it was trying to put in a Date line as the very last line in the widget display (side effect from a change made in V-3.8.05).
• Adds a NEW entry to the default Worldtimezones.txt file of: -06:00 America/Mexico[MST] as Mexico no longer uses Daylight Savings (as of October, 2022).
• Includes a check for the Android OS unexpectedly calling Pimlical in such a way that it might register too many phone listeners (could cause an UncaughtException error if this indeed was happening).
• Fixed an issue in getting the Widget to automatically refresh after rebooting phone.
• Fixes an issue with alarms not getting set after a reboot (possibly an OS library update fixed this? Not sure anything was changed in Pimlical to address this specific issue).
  

• Includes new Preference: WidgetIsInstalled which defaults to false on install of P/A. If the Widget is installed, Pimlical changes this preference to True. If the preference is set to false, and even if the Android OS reports (sometimes spuriously) that the widget is installed, Pimlical will not activate the Widget after a reboot (previously, due to a bug in the Android OS, Pimlical was informed that the widget was installed when in fact it was not).
• Fixes issue of the Widget Refresh notification symbol not being displayed for the full time the widget was refreshing after initial installation of the widget.
  

• Fixes issue of event with old image path (to Pimlical as root folder) which was supposed to automatically try and switch to using the PimlicalImages folder in the sand-boxed path.
• Fixes some issues of attempting to launch Pimlical while Widget is refreshing and getting a blank Screen with the Pimlical Icon (rather than just returning to the home screen).
• Removed the 3-second delay on initiating refresh of widget as it does not seem to be necessary.
• Fixes an interaction issue whereby the Widget might get invoked again when user or an alarm was interacting while the widget was or was just about to perform a refresh..
  

• Fixes issue of having the widget continue to run, even though it has been removed. Problem was that on reboot of phone, it was automatically triggering the Widget (had assumed that the Android OS wasn't dumb enough to run the widget even though it was not installed!).
• Fixes issue of  losing an alarm that triggers immediately after the Widget has refreshed.
• Fixes issue of alarm triggering WHILE the Widget is refreshing (now forces abort of Widget refresh so alarm can be handled properly).
• Fixes issue in Pimlical Alarm Notification where the time shown for the Next alarm was wrong (missing correct UTC adjustment).
• Fixed a problem in the Widget that if memory had been taken by the Android OS, it was not properly re-initializing the timezone table resulting in a spurious exception error when trying to read a time zone specification in an event.
  

• Fixes issue of Pimlical Alarm notification showing the next alarm at the wrong time (UTC rather than in current time zone).

• Pimlical Widget will now display on the last line of the display, a date header for the next event. Previously, if there was not room for the date header AND the first event on that day, you would just see a blank line.
• The Toggle Alarm command rather than setting the alarm at the event time (if no alarm is set on the item), uses the appropriate preset (FloatAlarmPreset or ApptAlarmPreset) from Preferences.
• Now compiled with SDK level 33 (Android-13) libraries - supposedly will prevent Google from removing Pimlical from Playstore in August of 2023. Also removes a permission (not really needed now) that Google has now decided is "illegal" for an App unless it's a very specific type of App.
• Adds new permission for displaying notifications (required now in Android-13) - you may need to explicitly enable the display of notifications for Pimlical/Android as it appears Android-13 turns them off by default on install.
  

• The Pimlical Widget is now no longer a separate App, but rather completely rewritten so it could be included in the functionality of P/A, as Android-11 forces sand-boxing of Android Apps (which in turn made it impossible for the Widget to access P/A's data). So when P/A is installed, you can long-press an empty spot on the home screen, and see that PimlicalA is included in the list of available Widgets (subscription only)
• Adds new preference Option: AlwaysResetBeforeAutoSync - which, if set to True (default is False), will automatically reset the AutoSync connection before invoking AutoSync (since Dropbox now demands that the user login). If you set this preference and put the AutoSync command on the command bar - you can invoke AutoSync with a single tap (of course, you still have to log into dropbox, but this is certainly more conveneitn)  (Subscription Only).
• Adds new preference Option: AutoSyncDelayAfterReset - which specifies the number of seconds Pimlical should wait after performing the Automatic Reset (i.e. AlwaysresetBeforeAutoSync is true). The default value is 5, but some slower devices may need more time to avoid an error message appearing (some internal timing problem in the CloudRail libraries?).
  
• Adds new preference Option: ForceCalendarReadAfterWidgetRefresh - which, if set to True (default is False), will force a refresh of Pimlical's calendar if the widget has refreshed itself since there was last activity in Pimlical Calendar. Normally this would not be needed, but if you setup your widget filter with custom preference settings, it's possible that you might need to set this true to avoid having P/A's display affected by the Widget's filter and preferences.
• Adds new Preference Option: PostponeWidgetIfPimlicalActive - which specifies the number of seconds (default is 30) to delay the launch of the widget if the user has been actively interacting with Pimlical's calendar. Since the refresh of the widget has to lock the user out of the Pimlical calendar while it's refreshing (to avoid contention problems), it would be annoying to have this happen right in the middle of some manual updating, so this preference helps ensure that the widget only runs to refresh itself when it appears the user is not actively doing anything. This preference is ignored if the user manually invokes a refresh of the widget.
• Increases the number of lines possible in the widget display from 20 to 25 since higher resolution screens are making that reasonable.
• Adds ability to perform boolean searches in the Calendar Find function, as well as Contacts and Memos Find functions (AND and OR, using && and |||). Note that this can not be combined with a word search (i.e. Boolean searches are only performed on simple text strings) (Subscription Only).

• Adds new option for the Command Bar and Gesture Preferences: RA - Reset AutoSync - allows the reset autosync command (located in menu | Debug) to be accessed directly from a command button or gesture.
• A tap on the map icon in the Edit Dialog will now launch mapping program with the contents of the location field even if it's grayed out. This is useful if the Android OS (for completely unknown reasons) fails to display a link for a valid map address and shows the address as a grayed out value - as it WILL now find the address anyway (provided it was a valid address).
• Fixes issue of reporting problem in Android calendars where the date fields were apparently corrupt/not properly set.
• Fixes obscure issue that could occur when taking an instance of a repeat series and changing it into a new repeat series (not allowed in Android Calendars due to Google calendar restriction, but it is allowed in the Pimlical local calendar), whereby the repeat status would be lost on exit from the Edit Dialog.
• Fixed new problem of ignoring a tap on Location Icon in Event Selection List (or in Contacts View) in Android-11 (bug in Android OS? Undocumented change? No idea what the Google programmers were doing).
• When EnableDebugLog is set, posts from the Widget are now posted in the file WidgetDebugInfo.txt (this preference should only be set when studying issues with alarms and the Widget).
• Fixes an obscure issue with reporting a missing timezone when in fact the timezone did exist in the timezone table.
  

• Fixes an obscure issue in displaying dates that include the last year of the calendar (December 31, 2099) when the preference DisplayWeekNumbers is set to True (can cause program to hang).

• Now uses "Scoped Storage" as required by Android-11 and later (means that the contents of your prior Pimlical folder have to be moved to this new folder in Internal Storage:
  Android\data\com.pimlicosoftware.PimlicalA\files\Pimlical). If not done already, Pimlical will automatically move all your existing data in the Pimlical folder to this new folder in scoped storage. P/A is still compiled for Android-10 so that it can perform this move (but this release cannot be posted on the PlayStore because the PlayStore now refuses to list any Apps that aren't compiled for at least Android-11). Google users will have to wait for V-3.9.x and manually move their data (or switich one time to this release to get their data moved).
• When uninstalling Pimlical, the Android OS will now include a checkbox that if checked will PRESERVE all the data in the "scoped storage" folder for Pimlical (if not checked, that folder is removed and all local data and preference settings will be lost). Note that unless permanently removing Pimlical, you will always want to be certain you check that checkbox!
  
• Ensures that if the Alarm dialog is removed from the screen by the OS (for whatever reason), sounds and vibration are explicitly killed by Pimlical (in theory the Android OS is supposed to take care of this issue, but at least one user ran into a case where this did not occur, so it might be an Android OS bug that requires special handling).
• When using voice input to enter an event, an Uncaught Exception Error could occur if user included "Next" or "This" but forgot to put in the day of the week and nothing but spaces were found - this has been corrected.
  
• Adds a new preference: WidgetDateWidth (default is 0). If set to a value other than 0, this forces the Pimlical Widget to use that value for the Date Width. Some users have noted that the Widget was displaying the medium Date format (mm/dd/yyyy) when there was plenty of room to use the longer form of the date - this results from a failure of the Android OS to properly provide the width value for the widget. You will need to set it by trial and error to find the right value (and when set to a non-zero value, the configuration screen will put up a brief message to inform you of this override.
• Updates the widget to use Scoped Storage - for compatibility with Pimlical/Android. The Widget is also now part of P/A and no longer a separate App.
• Fixes an obscure, cosmetic/consistency issue: if you use popup command to Change Color and then long-press foreground or background color to use either  the Color Swatch Selector OR the RGB Sliders to select a color, the Edit Dialog appears rather than returning to the Color Selection Dialog with the correct F/B color selection displayed.
• Fixes problem of attempting to add a eighth phone number field (caused an UncaughtException error because only seven labels had been defined) - this adds an eighth label of "ALT." and avoids the error. Prior User Preferences also only included seven labels for the preference: ContactPhoneLabelOrder.
• When first presenting the Contacts Edit Dialog, if all fields in a section (phone, email, address, custom) are already in use, the Add button is now hidden. The Add button will re-appear if any item is removed, and will be hidden again automatically when all fields are in use (this avoids any confusion from attempting to add a field when all are in use anyway).
• On reading the calendar database, the field validation routines now check for an end date that precedes the start date (after adjusting for timezones, etc.)  and if so, sets the end date to the start date (Pimlical will never create a corrupt event like this, but some other calendar apps might do it).
• Updated Worldtimezones.txt file so that Timezones with DST rules always precede those without (in some rare cases, when handling google calendars, or calendars imported from other calendar Apps it can cause an issue if this is not consistent).
  
  

• Fixes an obscure issue in the Widget whereby the time of an event in another timezone could be off by an hour due to Daylight Savings Issues.

• Restores ability to use full-page alarm dialog in Android-10 and later versions. To use the full-page alarm dialog, set the preference AlwaysShowNotificationForAlarm to false and go into Special App Preferences in the Android System Settings and grant permission to Pimlical to overlay other apps (you will get a warning if you fail to grant permission with this preference setting when you exit preferences). This does not interfere with the prior notification alarm handling when that preference is set to True (which was the prior default).
  
  

• Adds a new preference: AndroidDeletesToUndelete (default is false). If set to True,  deleting an item in an Android calendar moves it into the local calendar with a special flag set, AND it now appears in the UNDELETE list. You can then UNDELETE the item (either by calling it into the edit dialog, or selecting it in multi-select mode and tapping the item) and Pimlical will retrieve the internal flag so it can move the event back into the original Android calendar (the item is not moved back if the original Android calendar no longer exists). Note that without this new feature, there was no possible way to use the UNDELETE function with items in an Android calendar, as Google/Android calendars have no undelete function.
  
  

• Fixes another potential issue of the AutoSync deferred message appearing constantly even when pimlical does not appear to have any dialogs open (using menu | Exit should now ensure that everything is cleaned up).
• Fixes an obscure issue where on attempting to retrieve a possibly missed alarm (while Pimlical was not running), a notification could appear with a strange time.
• Fixes a new issue with the Set Link to File popup command resulting in a complaint about not being able to find meta-data for provider with authority, rather than proceeding with opening the file (new issue in Android-12).
• Fixes a very obscure issue that was previously resulting on rare occasions with a WRITE ERROR when updating an Android calendar.
• Fixes a very obscure error where an alarm might not get rescheduled (resulting in a missed alarm) - occurring when user force-exited Pimlical WHILE the calendar was being read.
  

• When updating or creating a new contact and the contacts app was launched from the widget, Pimlical now saves the contents of the Contacts Edit Dialog if you switch to another app. Previously, under these conditions, the dialog was closed and all changes/updates were lost. This same change was also applied to Memos which have the same issue if launched from the widget.
• No longer allows blank contact or memo records to be created or an update which results in a blank contact or memo (for memos, either title or memo text must be non-blank, for contacts, one of first/middle/last/company name fields must be non-blank).
• Fixes issue of sometimes losing the newly-selected foreground color in the color selection dialog, after long-pressing the background color to choose a color swatch or set the color with the RGB Sliders.
• Restores a recently-lost ability of Pimlical to serve as the target of a SHARE operation from another application (such as contacts). For those users wanting to keep BOTH a local and Android contacts database in sync, and unable to use the merge/update feature (because many/most contact apps are not properly updating the modified-date field), the best way is often to make the additions/changes in the Android contacts app and then just share the result to Pimlical contacts.
• Fixes a potential issue of the AutoSync deferred message appearing constantly even when pimlical does not appear to have any dialogs open (using menu | Exit will now ensure that everything is cleaned up).
• Fixes issue that if you have a template set up for the Daily Journal, and you were using a custom font-size for the template, when the Daily Journal was created, the font size was wrong, because the index into the font table was incorrectly interpreted as an absolute font size (usually resulting in tiny type).
  

• Fixes an obscure issue of running into a low memory condition in the Android OS with the Edit Dialog already open (at which point, OK/DELETE buttons are grayed out) and then pressing the BACK button. At that point, Pimlical thought the Edit dialog was still open and this could result in AutoSync thinking it had to defer running, and it would also cause some screen gestures to be ignored. This could happen if you left the Edit Dialog open, switched to several other apps, etc. causing the Android OS to abscond with Pimlical's memory to provide it to the other running apps.

• Fixes a very obscure exception error that could occur during the advancing of floating events.
• Contains some diagnostic information for tracking down an obscure issue with AutoSync complaining that it cannot run due to current activity when in theory it should not be even attempting to run.
• Fixes issue of some events with the AutoDelete flag set remaining in database after the number of days to delete expired records preference indicates they should have been removed.
• Deleted records now preserve their original category information (previously, the category was intentionally set to Unfiled, but the reasons for doing that no longer really exist, so now items can be undeleted and they will be in the same category as they were originally in prior to deletion).
• If the Direct Download version appears as NOT LICENSED, a note appears in menu | About telling the user to note down their ReferenceID on the line below and send it to Tech Support.
  

• Adds a Copy icon at the end of each phone/email/address row in the Contacts View dialog. Tapping this icon copies the associated information to the Android Clipboard, so it can be easily pasted elsewhere (Subscription Only).
• Adds a special Action Tag: AdvancedRepeatOnlyInSameMonth.  If set, when handling an advanced repeat, if the first occurrence of the day of the week is in the following month, the instance will be discarded (normally it would just display on the first instance of that day of the week in the following month. For example, to have an event repeat ONLY on the fifth Monday of the month and skip months that have no fifth Monday, set a repeat on the 29th of the month, select Monday as the day to repeat on/after, and check this tag and the event will only appear on those months that have a fifth Monday. Remember, that advanced repeats may not display properly in other calendar apps that do not support these advanced type of repeats (Subscription Only).
  
  

• Fixes issue of ShortDescription field not properly exploding designated Action Tag.
• Ensures that after templates are deleted, that the SystemPreferences.dat file is written immediately (in case Pimlical prematurely exits before it gets updated).
• Fixes obscure issue on advanced repeat that if the first matching day of the week on or after the day of the month or year is in the FOLLOWING month, it was not displaying the instance on the expected day.
• Fixes new issue that in the Filter display, the most recently used filter was no longer being displayed with a  Blue background.
• Now recognizes Pimlical's Custom vCard tags for birthday/anniversary alarmSet and AlarmAdvance fields (it was generating them for vCard output, but was not recognizing them when reading a vCard field). This change means that those fields are now properly preserved over an export and re-import of a vCard file.
• Fixes problem with day of month for birthday and anniversary of a contact being the day before on vCard export (P/D did not have this issue).
• Fixes a potential (unreported) but very obscure case where there might be an issue with the parent of a repeat series not being properly marked as the irregular repeat parent if one of the repeat instances preceded the date of the parent event.

• Fixes an UncaughtExceptionError that can occur under some conditions when DebugMode is set to True and Floating advance takes place.
• Potentially fixes an obscure issue with an unexpected concatenation of category names when MultipleCategorySelection is set to True and a template or filter is using multiple category names.
  

• Fixes a very obscure UncaughtException error  in the display of contacts photos when the Android OS inexplicably is unable to find the default photo in the resources.
• Now hides the Find+ and Find Text fields if only the one-page recent icons list is displayed as entering a find string at that time could under some circumstances cause an exception error (that function is only available when the entire icon set is displayed).
• Fixes a relatively new problem in handling timezones from Google Calendars stored in the Android Calendar database (Home timezone was getting unexpectedly set in some cases, overriding the actual event timezone).
  

• In the Event Selection list, the category color swatch (at left) now uses the background color if the foreground color is set to {1,0,0} - which is the "pseudo-black" used to display a black color (as an alternative to {0,0,0} which is also considered to be the default foreground color which can be overridden).
• The special Action Tags <<date>> and <<time>> as well as any Call-Action Tags are now exploded in the ShortDescription field (as well as the description and note fields).
• When checking off a repeat task (and under some conditions, a repeat float- when it was the first instance being checked off) the rescheduled repeat item was being reset to the Home Time zone in some cases. It now properly preserves the timezone of the original repeat series.

• Fix in V-3.7.115 for multi-line descriptions appearing as separate alarms was incomplete - it has now been fully corrected in this release.
  

• The Event Selection lists now set a background color of the preference: DefaultBackGroundColor.  For those users wanting to set up a dark theme, this makes it possible to control the display in those Event Selection Lists. If the DefaultBackGroundColor is dark (RGB Components all less than 185), and the text color is black by default, then the text color is changed to white for contrast.
  
• The Toggle/Busy popup command will now change from Type Free or Tentative or Out Of Office to Busy (previously it would only change Type  to Free to type Busy and do nothing if Type Tentative or Out Of Office.
• Fixes a really obscure Uncaught Exception Error that could occur under low memory conditions when a contacts dialog was left open.
• Fixes a redraw issue in the event selection dialog when deleting this & future occurrences of a repeat event and preference EditDialogQuickReturn was set to False (although no longer displayed in the main view, it WAS still displaying on return to the selection list).
• Fixes a new cosmetic issue (that appeared at some point in some recent version), whereby a floating event deleted in an event selection list might not be instantly removed from the list (but would show as deleted when returning to a main view).
• Ensures that explicit end-of-line characters in the description field of an event are stripped prior to presentation in Alarm Notifications (previously, multiple lines appeared as multiple alarms).
• Fixed an Uncaught Exception Error that was occurring when attempting to change the value of the Preference: ContactCategoriesToSync and also MemoCategoriesToSync. This fix also corrects an issue in properly displaying all the Contacts and Memos categories.
• Fixes issue of the Day of the Week name displays in the multi-Day, Month and Multi-Month Views being hardwired to display a fixed background, rather than honoring the preference to control those backgrounds (as controls the DayView, date background).
• Fixes issue in Event Selection List whereby the vertical color swatch at the extreme left was being set to black when the category colors were black on a background color - now, if the foreground category color is white OR Black, Pimlical will use the background color for the category color swatch.
• The Event Selection list now paints the entire cell in the color used for the description field (previously, only part of the cell was colored that way - this change provides a cleaner appearance for the Event Selection List), and the date/time fields use the same text color as was used for the description field (again for uniformity, and on the assumption that the foreground/background colors the user picked contrast well).
• The Event Selection List now honors the preference IconsOnWhiteBackground when displaying icons. By default, that will result in icons now being drawn transparently rather than a forced white background. If you dislike this change, just change IconsOnWhiteBackground from its default value of False to True.
  
• The preference IconsOnWhiteBackground now uses a pure white background - previously it used the color in DefaultBackGroundColor, but when setting up a dark theme that didn't work well as the icon would be drawn with a dark background.
  
  

• Another Fix for the issue in 3.7.112 that V-3.7.113 did not fully address.

• Fixes an obscure issue in the advance of Floating Events at Float Advance Time when Pimlical has been removed from memory due to low memory conditions (this was a new issue that arose due to change in V-3.7.112).

• Adds new preference setting: PastDaysColor. This provides a potentially different background color setting for days in the past (so you can quickly realize you are looking at past dates). This is overridden by the ShadedDates preference (i.e. if you are coloring weekend days, they will also be colored on past days. The default value is white (same as the default value for DefaultBackgroundColor). (Subscription Only).
• 
  
  

• Fixes problem of not clearing out some fields when an exception to a repeat series is edited back into a repeat series (Google Calendar disallows this completely, and Pimlical complies when handling an Android calendar, but it DOES allow the user to do this with the local calendar). That could potentially cause some odd things to happen.
• Fixes issue of having the urgency setting from the preference DefaultFloatUrgency overwriting an urgency level of "none" in an existing float (the setting should have been only applied on creation as is the case with priorities).
• Fixes issue of the preference: DefaultTaskCategory not allowing an Android calendar to be set (so that Pimlical tasks can be displayed in an Android/Google calendar).
• Fixes an obscure issue that only occurs if DefaultApptCategory is left at the default setting of Unfiled whereby the initial startup warning can unexpectedly re-appear. Similar fixes have been applied to the ShowHelpOnStartup preference as well as the LastFloatingUpdate preference which could result in the floating update being unnecessarily invoked on occasion.
• Fixes an obscure issue when deleting the final instance of a Float or Task and having it unexpectedly re-appear because under some conditions, the deleted record is not written into the database, so an immediate refresh on the database restores the record without its deleted status.
  

• The preference DefaultContactsCategory now presets the category when importing contacts from the Android contacts database (previously, imported contacts were always placed in the UNFILED category).
  
  

• Removes the rarely-used feature of setting GoogleRefreshInterval to -1 in Android-10 and later, as Google apparently  made some incompatible change in Android-10 that now renders it problematic as Android terminates Pimlical with no error, no exception and for no apparent reason. It looks like it's related to the new restriction in Android-10 that an application cannot be launched from an intent triggered by a background receiver (a badly-conceived restriction that renders a lot of useful code completely useless).
• In iCalendar Export, Pimlical was inadvertently including the Pimlical Calendar version instead of the iCalendar Version - a user reported that one calendar app refused to import because of the version issue. Pimlical now includes the static VERSION:2.0 tag in the header.
• Fixes a very obscure issue with alarms on Android-10 and later, that if a user taps on the SNOOZE button, but then NEVER selects a snooze interval from the dropdown list (and does not tap outside the dialog or otherwise does nothing to dismiss that dialog), future alarms won't get rescheduled until the user does that (or otherwise interacts with Pimlical to get alarms rescheduled). If the device shows the lock screen, the user might forget that they have to unlock the device and select a snooze time from the drop-down list (or perhaps they hit the SNOOZE button by mistake and thought they had hit the DISMISS button, etc.).
• Fixes an obscure issue on the display of events where the DST rules differ (i.e. the rule in effect at the time the event or instance of a repeat series was being displayed, versus the rule in effect at the current date/time) specifically with respect to the dates on which  Daylight Savings is in effect (or not in effect at all) - under some conditions, the event (or instance of a repeat event) was not being displayed at the correct time based upon the date being displayed in the calendar.