• Inbox: This will take you to project mode, and select the inbox. At this point it's expected that you'll either want to start processing your inbox, or you'll want to add a new item. If you want to add a new item, just press return.
• Projects: This will take you to project mode. It will preserve your sidebar selection, and your focus (which prior to today it did not do). It will always change your view settings to show the defaults, which means that if you want to have custom settings you should either make a perspective, or add the old mode switcher from the toolbar customization menu.
• Contexts: This will take you to Context mode. Like projects, this will preserve your sidebar selection, focus, but will always show you the default view settings. Again, if you want to have different defaults, you'll need to make a perspective.
• Due: Like Contexts, but with settings that are designed to make it easier to see what you have due.
• Flagged: Like Contexts, but only shows your flagged items.

tell front document of application "OmniFocus"

synchronize

repeat while syncing

delay 1

end repeat

{last sync date, last sync error}

end tell

Fixed another sync incompatibility with cPanel WebDAV servers (such as those hosted by bluehost.com).

The fundamental issue we've been facing is that cPanel doesn't preserve the names of files uploaded by the client, so when OmniFocus goes back to look for something it isn't where it put it. (In fact, if you try to browse to those files using a web browser you'll find that they can't download them either.)

We've hopefully worked around this by tracking the WebDAV URL independently from the transaction name, so we can use the URL when we need to fetch data from the server but use the original transaction name when deciding how that data fits together.

Please note that the iPhone version 1.0 of OmniFocus doesn't yet have these fixes; they'll be in version 1.0.1.

• OmniFocus 1.1 adds the ability to synchronize your OmniFocus database between multiple Macs using your MobileMe iDisk, a WebDAV server, or a local or remote disk. To start synchronizing your data, pull up the new Synchronization Preferences pane.
• Synchronization happens automatically in the background, but you can also synchronize at any time by selecting "Synchronize with Server" from the File menu, or by clicking on the "Sync with Server" toolbar item or the Sync Now button in preferences.
• To add support for synchronization, OmniFocus 1.1 has a new way of storing data. If you have an existing database from 1.0, you will be prompted to upgrade it the first time you launch 1.1.
• We now synchronize some common settings between Macs and iPhones. Specifically, we now synchronize the inbox processing settings (which control what happens when you clean up), the "due soon" and default review intervals, whether groups are sequential or parallel by default, and the hierarchy separator.
• Synchronization replaces the old Database Location preference, so if you've previously relocated your database you'll be notified that we're migrating it back to its standard location and that you can use Synchronization Preferences to sync with another location.
• OmniFocus will not let you undo past changes that we've synchronized from another OmniFocus database, since that could lead to inconsistent results.
• If you're using WebDAV synchronization, you don't have to connect to the server in the Finder: just enter the WebDAV URL into OmniFocus and it will connect to the server directly whenever it needs to.
• Automatic synchronization happens one minute after you make a change to your local database. If you don't make any local changes for an hour, OmniFocus will synchronize with the server anyway to see if you've made any remote changes. (You can always initiate a manual synchronization at any time, of course.)
• If the server is unreachable when OmniFocus tries to sync, it will just save up the changes and for the next synchronization attempt. You won't have access to whatever changes are on the server, obviously, but you'll still have full access to your local copy of your data.

• OmniFocus now has the ability to move old completed and dropped items into an Archive document. This will help keep your document svelte and of a reasonable size for your iPhone or iPod touch. See the Move Old Data to Archive… and Open Archive items in the File menu.
• Added a new Style Preferences pane, where you can easily change font sizes, colors, and other settings. (You can also save and load your own style themes!)
• Command-Return can now create a project or context that isn't at the top level. For example, you can enter "Errands:Bank" Command-Return to create a new Bank context inside your (existing or new) Errands context.
• In Data Preferences, added the option to clean up inbox items that have been assigned either a project or a context. (Previously you could choose a project, a context, or both—but not "either.")
• Polished up some icons and the default styles.
• The Enter key now saves edits rather than editing notes. You can still edit notes using Command-', but if you prefer using the Enter key you can set the OOShouldEditNotesOnEnterKey preference to true using this command:

  defaults write com.omnigroup.OmniFocus OOShouldEditNotesOnEnterKey -bool true

  If you'd like to start weaning yourself away from using the Escape key to save edits, try this:

  defaults write com.omnigroup.OmniFocus OOShouldToggleEditingWithEscapeKey -bool false

• Worked around some NSDatePicker bugs on 10.4 that would sometimes cause the default due time preference to be offset by several hours (based on your local timezone).
• The Edit->Sort menu now has the option to sort your selected items by their due dates.
• Sorting by date using the Edit menu now always order dates in ascending chronological order rather than the reverse.
• Context mode now defaults to showing available actions (stuff you can do) rather than all remaining actions (stuff you haven't done).
• You can now copy from OmniOutliner and paste into OmniFocus.
• Importing a generic OmniOutliner document now places imported items at the end of the inbox, rather than creating a new top-level project for the import. (Importing a Kinkless GTD outline still behaves as before, creating folders and projects.)
• The Column Mapper dialog for OmniOutliner imports now starts out with the OK button highlighted, so you can just hit return to accept the default mappings.
• We now indicate that we allow linking when dragging a file between items, not just when dropping a file on a item.
• Improved the performance of "smart match" completion.
• If we can't sync with iCal because you don't have the default document open, we now report where the default document is and where your current document is.
• When grouped by context in context mode, pressing return with a parent context selected in the sidebar now properly assigns that context to the new action item.
• Fixed a hang in Find Previous.
• OmniFocus now displays status messages while upgrading and loading documents.

This update to OmniFocus focuses on adding support for additional languages, as well as fixing some stability and interface issues and other minor bugs.

Over the last few months, most of our attention has been focused on OmniFocus 1.1, where we've been adding support for synchronization, and on writing OmniFocus for the iPhone. We plan to release both OmniFocus 1.1 and OmniFocus for the iPhone in late June (if they're ready!).

• OmniFocus is now available in Japanese, French, German, Spanish, Italian, Dutch, and Simplified Chinese. Please let us know if you see any problems with any of these translations!

• OmniFocus should no longer crash when dragging images from mail while editing.
• Instead of crashing, just a log an exception when pasting rich text that has odd formatting properties and use defaults instead.
• Fixed a hang occasionally seen when using a two-button mouse.
• Worked around a Leopard bug (5728015) which would cause OmniFocus to crash after used the Help menu to search for a menu item.
• Fixed a memory leak.

• Improved OmniFocus' memory of which windows were open the last time you used it. (OmniFocus used to sometimes open windows that you'd previously closed, or forget their current position or size.)
• Right- or control-clicking on an item now changes the keyboard focus to that item before bringing up the contextual menu. This ensures that all the items in that contextual menu will be validated against the appropriate target item.
• The reset button on the view bar should show up when making changes while a perspective is active.
• Remove contextual menu items that were not applicable to sidebar items.
• Updated some labels in Data Preferences.
• Fixed a bug where the "Show in Context Mode" menu item would say "Show in Project Mode" until you first switched modes in a window.
• When Software Update finds an update with the same major version as the currently licensed application (e.g. OmniFocus 1.x), it should now correctly indicate that the update price is free.
• The license window will no longer continue to display "No license available" after a license is added.
• Fixed the help link in the Mail preference pane on 10.4.
• When a chosen keyboard shortcut is already in use by a menu item, we now present the full path that leads to that menu item.

• The code used in OmniFocus is now signed for Leopard's benefit. (For more information, see Leopard's code signing release notes.)
• Focusing on a project now saves any edits that are in progress.
• When synchronizing with iCal, we now set an appropriate local time to incoming dates without times. This should help solve synchronization issues for people in New Zealand who are using daylight savings time (where the local date differs from London's date when it's noon in London). It also means that we'll apply the default due time setting from Data Preferences to items created in iCal.
• Worked around an operating system bug which could delay automatic backups after waking a computer from sleep.
• License files will no longer be created with the "execute" permission enabled. (The files were never actually executable, and shouldn't be marked that way.)
• Removed a Console log message which would sometimes appear when executing AppleScript.
• The online help now correctly indicates that you hold down Option to copy a file rather than linking to it when dragging.
• Added logging to the Mail Rule processing script so that it's easier to for users to determine whether or not it's getting called by Mail.

• Updated our error handling support to catch more cases where there is a possible problem and promote it to a crash, so that we can then fix it. Since OmniFocus always keeps its data in a saved state, the net effect of this is that any such exception won't be able to cause data corruption.
• Copy a workaround for a bug in Mac OS X 10.5 that can cause a crash when using the keyboard to navigate between cells in the outline.
• Fixed exception where committing editing on a row caused that row to be collated into a different group.
• Fixed a few glitches in the AppleScript suite that could cause scripting errors.
• Fixed exceptions when parsing some European date formats. Updated the date parsing to log details about the date format if there is a problem parsing a date, allowing the user to more easily gather the relevant information in the future.
• Fixed an occasional hang when performing a manual check for updates when no updates are available.
• Clicking on a link to a recently deleted task will no longer cause an error.
• We now ignore and log exceptions raised from Growl.
• Fixed bug causing the available/due soon/overdue timer to fire too often in some cases.
• iCal syncing will now deal with unnamed calendars.

• The Perspectives menu now always has options to make a new perspective or save a snapshot of the current view settings into the current perspective.
• The Clear Perspective command has been folded into the Revert to Default View command, so you don't have to take two steps to get back to normal.
• Actions created in context mode should no longer appear to be missing their project, once it is assigned.
• Updated usage of shadows in the interface to match changes made in Mac OS X 10.5.
• Empty projects with a start date will now get the normal project icon once its start date passes instead of getting stuck with the 'pending' badge.
• The flag icon should now show up appropriately in HTML exports.

• Various small updates to the online help.
• Turned off some debug logging in the Clip-o-Tron 3000.
• Software Update will now only show you builds on the same track that you are running. So, if you want to see sneakypeek builds, you'll need to manually download one sneakypeek build main OmniFocus site.

• Fixed several issues that would prevent internationalization. No localizations are in place, but those are in progress for a future release.

• Show Perspectives
• Save Window as New Perspective
• Take Snapshot of Current Perspective
• Revert to Default View

Rearranged the Context filters to better match those in Planning mode, adding some extra filters in the process. The underlying functionality is the same (with some extensions), but Contexts that were previously marked "Available" and "Blocks next action" are now shown as "On Hold". This provides a clearer indication of how to implement Contexts that are paused or 'waiting for' some external criteria to be actionable.

Now, Contexts have three states: Active (previously "Available"), On Hold (previously "Available" with "Blocks next action" selected) and Dropped (previously "Unavailable").

The following filters are available, using the same terminology as in Planning mode and adding some extra functionality:

• All Contexts: Shows every Context
• Remaining: If a Context hasn't been marked Dropped, it will show up here and in the interface when picking a Contexts to assign to an action.
• Active: As in Planning mode, this lists all Contexts that have available actions
• Stalled: Again, as in Planning mode, this includes Contexts that either have no actions or all the actions are blocked
• On Hold: All of the Contexts marked On Hold (previously "Available" + "Blocks next action"). This can be used to 'pause' a Context if you personally cannot complete the actions. For example, you might be in Sequim but the action needs to be done in Skamokawa), or perhaps you have delegated the action to another person and your only course of action is to ping them about it.
• Dropped: These are the Contexts that are no longer relevant to you. Perhaps you've moved to a new job or home. But, instead of deleting the Context all together, marking it Dropped allows you to view completed tasks within that Context for archival purposes.

We feel that this cleanup and alignment with the project terminology will clarify the usage of Context. Please let us know via Help > Send Feedback (or the forums) if you see any problems caused by this change and we'll get them fixed right up. Well, maybe not Christmas Eve or day, but soon!

If you run into any bugs, you may opt to revert to an earlier build until we clean it up. Hopefully this won't happen, but since response will be slowed slightly during the holidays, it bears mentioning.

• Inactive shows all Contexts that have no available actions; note that some Active Contexts might be shown too if an Active Context is a parent of an Inactive one.
• Unavailable for all Contexts that have been marked Unavailable.

Column visibility and width settings are now stored in window/view state now, instead of in preferences. This means that you have per-window and per-perspective column settings (important for printing).

Since Quick Entry was previously latching off the global preferences and can't now, Quick Entry now has its own set of preferences. And, since it had now UI to edit the column settings, it now needs some UI. There is now an action button in the lower left to toggle column visibility and column headers.

• Automatic Backup - clicking will reveal the file in Finder
• Clipping Added to Inbox - when clippings are sent to Quick Entry, no Growl will happen. Clicking will reveal the inbox item
• Task Available - the start date on a project or action has been reached; clicking will reveal it
• Task Due Soon - the due date on a project or action is within the 'due soon' range specified in preferences; clicking will reveal it
• Task Overdue - the due date on a project or action has been reached; clicking will reveal it

						tell application "OmniFocus"
						tell perspective "Staff Meeting Agenda"
						print without print dialog
						end
						end
					

• You can now specify whether clippings go to Quick Entry or straight to the Inbox.
• Installation of the Mail bundle to allow clippings from the message list can be performed in the user interface now, without resorting to Terminal.

• Added a menu status item. This shows the count of items needing attention in one form or other. The Inbox and No Context groups are listed, as are all of the active contexts. Counts are show next to each item in the menu; selecting the item will pop open that portion of the document with some appropriate filter settings. The UI for the menu status item when there are no actions needing attention is open to change too; feedback welcome.
• Added a dock counter and menu. The dock menu doesn't allow images, so the counts are shown as suffixes on the object titles.
• Added preferences for enabling counters in the sidebar, menu bar and dock (under Data for now, since these relate to Dates & Times which will be a section under this pane).
• Added a counter for the 'No Context' group in the Context sidebar. There is at least one case where the No Context counter is still wrong and we'll continue to work on it.
• Updated the logic for counters in Context mode to obey the focused projects for the window. Now you'll no longer be bothered by counters dealing with projects in your Home folder when you are focused on Work, for example. The menu status item and dock counters are global still and are intended to remain so.

• Perspectives are now created and edited "in place" on the perspective window.
• You should be able to drag a custom icon for a perspective, and have that icon persist.
• Perspective toolbar items should update on deletion, icon and name changes.
• The "Camera" button in the perspective window will update the selected perspective with the settings of your frontmost window, allowing you you to modify a perspective.

• Each perspective stores its own Page Setup information (this has been true for a while, actually). If a window isn't attached to a perspective, it uses a global shared Page Setup stored in user preferences.
• Added a Page Setup view that lets you configure a few options like a header, checkbox visibility, black & white conversion and row/note expansion.
• When printing, we now re-size the outline to fit within the width of the paper, as best we can. If the column widths don't permit this (they are too wide), then we scale the printout down so that it will fit within a single paper width. Finally, if the user has specified a scale factor in Page Setup, that is applied.
• Added pagination support.
• Handles print as drawn on screen now. Printing them as bullets was intentional, but confused some users.

• New actions created in an iCal calendar which synchronizes with more than one context will be automatically assigned to the first synchronized context.
• Inbox items assigned to a synchronized context will be published to the appropriate iCal calendar.

• It's much, much faster.
• It now preserves links in project and action names, and preserves full rich text in notes including links and attachments. (It does not yet preserve attachments in action names.)
• It now imports Deferred projects (into an inactive "Deferred" folder) in addition to importing the active and archived projects.
• It now imports all Kinkless information into its own top-level groups in both Planning and Context mode, so it's easy to find everything that was added (and possibly shuffle things around to clean things up).

Added a new 'parse tasks' AppleScript command. Our Quicksilver action may migrate over to this command instead of implementing the parsing in AppleScript. Or maybe we'll keep both; it's hard to say, but we do realize that the syntaxes are different at the moment.

Here is an overview of the way tasks are parsed from Mail, presuming they matched the criteria specified in the rule:

• The subject and body are concatenated into one block of text.
• The first line, or any lines that start with '--' are taken to be the first lines of new tasks. Other lines are notes on the preceding task.
• If you choose, you can add a note on the same line as a task using '//', for example "title // note". Anything after the last '//' in the line will be considered a note. Double-slashes in URLs will be skipped (so "http://www.foo.com" won't start a note in the middle of the URL).
• ">" or "::" can be used to specify a project. The double-colon is nicer for the iPhone keyboard since it is on the first shifted keypad (> is on the math symbol keyboard). The project string will be matched exactly as if entered in a project cell in interface.
• "@" can be used to specify a context, again with matching as in the interface.
• "#" can be used to specify dates, using our relative date parsing. If there is only one date, it is the due date, if there are two, the first is the start date and the second is the due date (the order they appear in the interface).
• "$" can be used to give a time estimate.

Some examples:

						-- Action > Project @ Context
						Note note note note note la la la
						note la la
						-- Another Action > Project 2 @ Context 3
						Note wheeeeeee

						I have empty lines in my note

						It's great

						-- Action 3 > Project 2 @ Context 3 // Same-line notes too, if you are into that kind of thing
						-- Action 4 > Project 3 @ Context 2 #friday // due Friday; due dates are more common and more important than start dates, yes?
						-- Action 5 > Project 2 @ Context 3 #monday #friday // Starts Monday; due Friday.
						-- Action 6 > Project @ Context #monday # // Starts Monday; no due date.
						-- Action 7 :: Project 3 @ Context 3 // Written on my iPhone; colons work in place of chevron.

						--Action8>p2@c2//no spaces needed, nor full names
					

• New Synchronization Preferences let you choose which contexts synchronize with which calendars, including the ability to synchronize many contexts to a single calendar or to leave contexts unsynchronized. Simply drag contexts onto the calendar you want them to synchronize with.
• Synchronization Preferences also include some simple checkboxes which specify whether to synchronize blocked and/or completed actions, and whether deleting tasks from calendars will delete the corresponding actions from OmniFocus.
• Since you can synchronize with any existing calendars, you are no longer limited to calendar names which have an "OF:" prefix. Among other things, not being forced to have a colon in the calendar name means that you can synchronize your action lists with an iPod.
• Since OmniFocus is no longer creating its own calendars, synchronizing should never again fail with the error "Cannot push calendars" and will preserve any existing notes you have assigned to a calendar.
• Synchronizing with iCal works better on Leopard. (The problem was that iCal on Leopard doesn't notice new calendars created by other applications. Since we don't create calendars any more, this is no longer an issue.)
• When entering a new task in iCal, you can provide a project name in square brackets to assign it to an existing project. (You can use the same abbreviation matching techniques that you can use in the application, and OmniFocus will use the first match. For example, "[dof]" might mean to assign my new inbox item to the "Develop OmniFocus" project.)
• The url field of a synchronized calendar task now contains a link to the corresponding action in OmniFocus, so you can open it from iCal.

• Last Review Date
• Next Review Date
• Action Count
• Start Date
• First Due Date
• Project Status
• Contains Singleton Actions
• Attachment Count
• Folder Name
• Containing Folder Names
• Context Names

These can be seen in the Finder Get Info panel and can be used to build smart searches or otherwise searched via Mac OS X's Spotlight service. If you have ideas for extra per-project metadata, please let us know.

Known issues: Double-clicking a matching project in Finder will present an error in OmniFocus rather than opening it. This'll be fixed soon. Using the system Spotlight menu to enter text and then selecting a matching project will do the same, and it will ignore the entered search text. This will take a bit longer to fix (but at least soon it should open up the right project). Finally, Finder smart groups are showing the project's unique identifier file name instead of the user-entered project name. It isn't clear why this happens -- might just be a bug in Mac OS X.

Added some work-in-progress, super-preliminary online help. First, let me quote the disclaimer:

Hello. This is the hilariously incomplete alpha version of OmniFocus Help. It's even more preliminary than the software itself, but at least it's unlikely to explode your data. Don't be surprised to find bad advice, sentence splinters, howling voids where there ought to be sections of text, or unintelligible notes from the author to himself.

That said, you'll find the new online help in the usual place, under "OmniFocus Help" in the Help menu.

Enabled clipping support that has been in progress for a while.

This uses the Mac OS X Services support to allow clipping of rich text from any application supporting services (hopefully the vast majority in this day and age...). The clipping is sent to Quick Entry, after which a series of plugins are invoked that perform AppleScript handlers to massage the data based on the source application.

For example, if you have MailTags installed, a link to the sender and message will be prepended to the note, the flagged state, due date, and project (if present in OmniFocus) will be copied over. The subject of the mail message will be set as the task title.

As of yet, there are only a few plugins, Mail with MailTags (we don't have a plain Mail plugin yet), OmniWeb, Safari and a fallback which does its best to capture information about the source of the clipping.

The plugin format is pretty simple, though not currently documented. You can look in the app wrapper at BuiltInClippingHandlers.plugin for the examples mentioned above, and come by the Omni Group Forums and chat about how to support your own apps. And of course, if you have feedback on what apps you'd like us to include support for, send us feedback.

The keyboard shortcut used to invoke the service can be specifed in a new clipping preferences pane.

Disabled the preferences for the web interface.

The web interface has been great for people who understand it and can support themselves, but it's not really the iPhone solution we hoped it might be: lots of people are just confused and frustrated by it and we don't have time to help everyone figure out how to set up dynamic DNS, navigate their firewall (assuming that's even possible), and so on—nor do we have time to implement all the features we'd really love for that interface to have. And it's fundamentally limited by the requirement that your Mac be awake and online whenever you want to access the interface.

If there's sufficient interest, we could probably release the web interface code as an open source project (it's written in Ruby on Rails, and talks to OmniFocus using our supported AppleScript APIs), but for now we need to focus on shipping the desktop app itself.

If you're already running the web interface, it will remain running for now. You can permanently stop it by running this command in a Terminal window:

launchctl unload -w ~/Library/LaunchAgents/com.omnigroup.omnifocus.web_interface.plist

We'll continue to look for good solutions for making your action lists available wherever you need them. (We continue to support synchronizing with Palms and smart phones that support task lists through our support of Sync Services and iCal, and we'll also be improving our printing support so it will be easier to bring your list with you on paper. And hopefully iPhone will support tasks soon!)

						tell application "OmniFocus"
						tell front document window of default document
						tell note of first inbox task
						insert "foo" at after first character using style of last character
						end
						end
						end tell
					

						tell application "OmniFocus"
						tell front document window of default document
						-- focus on a single project or folder
						set focus to MyProject

						-- add an item to the focus
						add MyFolder to focus

						-- remove some items from the focus, if present
						remove {MyProject, MyFolder} from focus
						end
						end tell
					

• Added a 'library' property to the sidebar tree to match the 'inbox' property that was already present.
• Made the 'inbox' property work in Context mode; this returns the top level tree for the 'Needs Context' smart group.
• Removed the 'task source' class; this is unneeded now that we have the correct tree structure in the sidebar. Instead you now use the 'tree' element of 'library'.
• Renamed the 'inbox source' class ot 'inbox tree' for better constiency.

• Active now lists any context with at least one available action, unless it has been marked as hidden.
• Available now lists all the contexts that haven't been marked hidden (this is what "Active" used to be).
• All shows all the contexts, of course.

						-- Get a list of perspective names
						tell application "OmniFocus"
						set names to perspective names
						end tell
					

						-- Make a new window with a given perspective:
						tell application "OmniFocus"
						tell default document
						make new document window with properties {perspective name:"New"} at end of document windows
						end tell
						end tell
					

						-- Adjust a window to conform to a perspective
						tell application "OmniFocus"
						tell default document
						tell front document window
						set perspective name to "Perspective 2"                                       
						end tell
						end tell
						end tell
					

						-- Get the name of the perspective of the front window; if any
						tell application "OmniFocus"
						tell default document
						tell front document window
						set perspective name to "Perspective 2"                                       
						end tell
						end tell
						end tell
					

						tell note of MyProject
						count of attachments -- This doesn't work in Cocoa scripting at all
						end
					

						tell note of MyProject
						-- create a new file attachment that links to an existing file
						make new file attachment with properties {file name:"hfs:path:to:my:file"}
						end
					

						tell note of MyProject
						-- create a new file attachment that copies an existing file into the document
						make new file attachment with properties {file name:"hfs:path:to:my:file", embedded:true}
						end
					

						tell note of MyProject
						-- save the contents of a previously embedded attachment to disk
						tell first file attachment
						save to "hfs:path:to:destination"
						end
						end
					

						tell cell "context" of MyRow
						perform action "AXPress"
						end
					

Updated the logic for computing effective start/due dates on tasks. Now, the parent's value clamps the allowed range for the child.

If you have a task group where the group has a start date of next week and one of the entries has a start due of today, the effective start date is next week (that is, you can use a start date on a task group to postpone the entire group).

On the due side, setting a due date earlier on the task group will force the entire group do be due earlier.

Note that the UI for displaying the effective vs. user-entered start and due dates is still yet to be done.

This is just talking about http: don't try to turn it into a URL.

• have a super spiffy bucket icon that will probably be replaced at least a few times while we work on it,
• are always parallel,
• and have no next action.

• What were you doing right before you clicked on the paperclip?
• What data is in the note?
• Have you crashed opening this note before?

Thank you: we're hoping some of you can help us track this down!

• When using the web interface on an iPhone, you can now scroll past the first page of actions.
• Fixed a bug in hiding the new action form when switching back to contexts.

• Repeating actions are only assigned a new due date if they had one previously.
• For items which repeat relative to their completion date, all dates move by however long it takes to move the item's preferred reference date (its due date, or if absent its start date) up to the completion date plus the repeat interval.
• For actions which repeat relative to their previous dates, all dates move by some multiple of the repeat interval (applied as many times as needed until the preferred reference date is in the future). This is more or less what we were doing before, except that we now prefer the due date over the start date as a reference date, and you can now repeat with intervals smaller than a day.

• For completed items we now try to read the completion date from the notes, rather than setting the completion date to the import date.
• If a Kinkless project was marked as complete, we now set the status of the corresponding imported project to "Done."

• Clean Up no longer leaves items in the inbox after they've been assigned to a context. If an action has been assigned to a context but not a project, you'll find it listed under that context.
• Actions no longer remain in the inbox after they've been completed. (We do archive them, but at the moment there's nowhere to find them unless you first assign them to a project or context! Where would you like to find completed inbox items that were never assigned a project or context? Please send us your feedback!)

• OmniFocus no longer publishes contexts which don't accept a next action.
• OmniFocus no longer publishes completed actions by default. This behavior is controlled by the new SyncShouldPublishCompletedActions preference.
• OmniFocus no longer publishes blocked actions by default. This behavior is controlled by the new SyncShouldPublishBlockedActions preference.
• Renamed the "SyncCanDeleteTasks" preference to "SyncCanDeleteActions" so that we have a more consistent naming scheme.

• We now set the iCal priority for an action based on whether it's flagged and/or a next action. The ordering is: flagged next actions (high), flagged actions (medium), next actions (low), and all other actions (none). If you set an action's priority to medium or high in iCal, we'll flag it in OmniFocus.
• We display a status indicator while synchronizing, and play a sound when we finish.
• Synchronizing with iCal no longer adds a start date to actions which didn't have one.
• iCal summaries now include the project name.

• OmniFocus no longer pulls actions out of calendars which aren't associated with an OmniFocus context. (It used to pull them into your OmniFocus inbox and delete them from your calendar. Now it only pulls in new actions that are assigned to an OmniFocus calendar.)
• OmniFocus no longer publishes actions from inactive projects.
• OmniFocus no longer publishes projects which have a default context as though they were actions.

• When dragging to an outline, we now always use the vertical position of the mouse to determine where you'll drop something. (We still pay attention to the horizontal position of the thing you're dragging so that you can drag a name straight up or down in the sidebar to reorder it without accidentally indenting.)

• Note: This was broken in builds before revision 87382.

• Warning: Please back up both your OmniFocus database and iCal database before experimenting with this new, untested feature!
• Tasks now synchronize the following properties:
  • Name
  • Note
  • Completion Date
  • Start Date
  • Due Date

• defaults write com.omnigroup.OmniFocus SyncCanDeleteTasks -bool true

• defaults remove com.omnigroup.OmniFocus SyncCanDeleteTasks