Apple provides 2 frameworks to do this and I’ve tried to switch to the latest and recommended framework (available since macOS 10.11), but this transition is not complete because the new framework still has missing features (features which existed in the old framework. Nevertheless, while making these changes I also added better integration with Contacts. ![]() It’s now, finally, possible to make filters and rules based on whether or not a given email address (such as the sender) matches a contact in a particular account and/or group. The initial implementation will likely have bugs. Changed: The email address related menu in, e.g, the headers view has a general option to “Create/View Contact”.One known bug is that changes in Contacts do not automically trigger smart mailboxes to be updated in MailMate. This is more robust than the previous approach. #Eaglefiler 1.7.2 serial seeker code#Ĭhanged: Rewrote AddressBook-based code for expanding groups from Contacts.Changed: Improved handling of user permission to access Contacts.Due to missing features in the Contacts framework, you’ll still have to open Contacts to edit a new/existing contact. For information about previous releases of EagleFiler, please see the version history.Fixed: Improved the use of distribution lists (while also minimizing its reliance on the AddressBook framework).Changed: Efficiency improved when printing something referencing external images.Changed: Completing addresses in the recipient headers is now based on the Contacts framework.Changed: Improved formatting of names based on entries in Contacts. Older versions are available for older operating systems. The distribution disk image is now signed.ĮagleFiler 1.7 works with Mac OS X 10.6.8 through macOS 10.12. ![]() Fixed a bug where edits to a record’s tags could be lost if you moved it without the tags bar losing focus.Fixed a regression where tagging from the Record menu didn’t work.Added a workaround for a PDFView crashing bug in macOS 10.12.Worked around an OS bug that caused problems for tag completion using composed character sequences.Fixed a bug that caused EagleFiler to report an error when opening a library on macOS 10.12.Fixed a bug where EagleFiler did not launch on macOS 10.12.Worked around an OS bug that could cause files in the To Import folder not to be imported promptly.Fixed a bug reading messages that have DOS linebreaks, which could lead to exported mbox files not importing properly and could affect the display and indexing of certain messages.Tried to work around an OS issue where sometimes libraries were not added to the Open Recent menu.Renamed “Mac OS X” to “macOS” throughout the app and documentation.How can I access my library from multiple Macs?.Improved the following sections of the manual:.Made some changes to the way EagleFiler generates mbox files to prevent Thunderbird’s importer from getting confused.On macOS 10.12, EagleFiler no longer shows its Select Next Tab and Select Previous Tab menu items because they duplicate the new system ones.EagleFiler reports a better error message if it finds that an Apple Mail message file is empty.The Errors window is better at displaying filenames containing slashes.When reporting that a file is damaged, EagleFiler now shows the relative path rather than just the filename, to make it clearer which file has a problem.EagleFiler now shows an empty Container column when the file is directly in the Files folder, as this is more clear than showing Records. ![]() When you use the Export… command to generate a new mbox file for the selected messages, EagleFiler now uses Unix- instead of Mac-style linebreaks, since more e-mail products now support the former. ![]()
0 Comments
Leave a Reply. |