Stability
- Deleting a named style could crash in cases where the named style was applied to two ranges of text in the same row, if the planets aligned and the moon blotted out the sun. Sadly, some folks hit this one before we were ever able to reproduce it. No more! The planets are permanently misaligned!
- Fixed crash when importing MORE files with attachments that we failed to understand. Also, we now understand more attachments in MORE files.
- Fixed crash when importing certain types of Acta files. Also, we now continue importing when we hit an attachment in an Acta file.
- Upgrading OO2 documents would leave the imported document in a state where you'd have to hit cmd-s twice to get any changes saved (once you'd done that, though, it would save as normal).
- Pasting more than 20 rows from an OO2 document into an OO3 document could crash IF the source OO2 rows had something in them that got turned into an attachment (a URL string or email address) and the destination OO3 was running in unlicensed demo mode. The automatic rollback code in this case wasn't cleaning up the attachments correctly.
- Adding a new AppleScript to your OmniOutliner scripts folder could cause a crash the next time you clicked on the scripts menu in OmniOutliner
- Reverting an edited document while a batch find session was active could crash
- Hoisting to a row containing an expanded QuickTime attachment (with the section title text view visible) and then un-hoisting could crash.
- Improved the unhandled error alert panel to avoid having it disappear in the case that another error happens while that alert panel is visible. This will make it possible for users to report the original error message in these cases. Also, in some cases, repeated unhandled errors could end up crashing the application w/o providing any useful information in the crash report
- Using batch find, if you entered some right-to-left text (in Hebrew, for example) and that yielded a match, the application could display the match result incorrectly or possibly crash.
- Some 3rd party context menu plugins were sending messages to our outline view w/o first checking that it implemented the message. We now implement the message rather than letting them crash us (and we contacted the vendor and they fixed their plugin too)
- Quitting with a miniaturized document containing an expanded QuickTime movie could crash (usually only if there was another miniaturized document)
Performance
- We've fixed some (relatively) low-risk & high-gain performance issues in loading and saving OO3-formatted files.
- Improved speed of the generation of the XML
- Improved speed of reading the XML and transforming it into Cocoa's text system's representation
- Avoid regular-expression checks for URLs in more cases
- We no longer add the pretty-printing whitespace nodes in the XML tree when the document is being saved compressed
- Removed some overhead for creating and destroying attachments (expensive in cases where your document has many attachments)
- Improved speed of the generation of the XML
Importing/Exporting
- Imported documents were previously not defaulting to storing with compression enabled. This impacted files upgraded from OmniOutliner 2, MORE, Acta, plain text or any other imported file.
-
NOTE: If you imported files with the previous release, please check the state of the 'Compress on disk' checkbox in the document inspector. Compressing the document yields a measurable performance improvement.
-
NOTE: If you imported files with the previous release, please check the state of the 'Compress on disk' checkbox in the document inspector. Compressing the document yields a measurable performance improvement.
- We now handle PICT attachments (which you can get, for example, by hitting cmd-shift-ctrl-4, selecting a region of your screen and then pasting into a row)
- Pasting in RTF with embedded links (say, by selecting some text from a web page in OmniWeb or Safari) wouldn't turn those links into attachment tags.
- We've switched back to using UTF-8 as the default string encoding for plain text, OPML, and such. We don't know what we were thinking with the whole Mac Roman thing.
- This will also fix issues with copying Unicode characters and pasting into plain-text destinations
- Also, this fixes the issue where sometimes exporting a document to plain text would silently do nothing.
- Now, you'll get a warning if the encoding selected in the Text Export preferences isn't capable of representing all the characters and we default to an encoding that can represent all characters. Tasty and good for you!
- Now, you'll get a warning if the encoding selected in the Text Export preferences isn't capable of representing all the characters and we default to an encoding that can represent all characters. Tasty and good for you!
- This will also fix issues with copying Unicode characters and pasting into plain-text destinations
- Clicking in a cell and leaving it could change your document in some cases. For example, if you had entered a date of "1/1/2007" and then switched the column to display only the month and day, clicking into the cell and then leaving would reparse the text in the cell and change the year to the current year of 2005. Now, the cell will not get reinterpreted unless you change the string representation.
- Clicking in a cell with a number format set that included a space would cause the cell to be cleared when you clicked out of the cell. For example, some locales have their thousands separator set to " " and some locales have a space between the currency symbol and the number. Apple's number parsing facilities didn't handle this, so now we do some cleanup before handing off to them.
- Summarized values could be lost in some edge cases. For example, if you added added a row, indented it to be under a parent with a value in a summarized column, hit undo and then edited the child's value in that column, the parent's value would disappear.
- Modifying a cell in a summarized column and then saving w/o leaving the cell would immediately dirty the document after the save (saving again would fix it). Our code to propagate the cell contents to the model on save wasn't working correctly.
- Miniaturizing an untitled document would cause an error message to be logged to the console, and would possibly cause further problems down the road (unclear if it did since we noticed this internally)
- A normal save or a save-as of a document would incorrectly reset your 'last export format' preference
- With your date format preference set to 'Germany (German)', entering a date of '21.01.2005' could get incorrectly turned into '21.01.2020'
- Control-key shortcut option for applying named styles didn't work on some machines. Silly coding error on our part.
- Left/right margin fields on the Margins tab of the Page Layout panel were swapped. Boy, don't we feel silly. Really, there is a reasonable explanation for it. Really.
- Export as DHTML is correctly marked Pro-only now
- Editing the OSUCurrentVersionsURL default in the application's Info.plist now correctly overrides the software update URL (necessary for site license situations, but not so useful for others)
