Not signed in (Sign In)

Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.

    •  
      CommentAuthorfrode_
    • CommentTimeMay 14th 2011
     
    Hi,

    I’ve just migrated from Scrivener 2 (got sick and tired of its reliance on rtf files), and I have to say that Ulysses 2 feels a lot better. I do, however, have a couple of feature requests:

    - Some sort of auto save, so I can write without ever hitting cmd+s. I know I can set up the backup function to mimic this, but I’m really missing Scrivener’s save every 2 seconds option.
    - When switching from console mode to regular mode, I’d really like Ulysses to keep the current caret position instead of jumping to other parts of the text.

    Keep up the good work!

    Frode
    •  
      CommentAuthorniklas
    • CommentTimeMay 14th 2011
     
    Well, saving in Ulysses works a bit differently from Scrivener (and most other apps). First of all Ulysses *always* saves your work, continuously. Try it: type something, quit, and reopen … see?
    The thing is that as long as you don't explicitly save a document it is saved in an "unsaved", or rather "working", state (with a bullet in front of it's name). The point is that you can then always revert to the original "saved" version of the document, until you decide to save. You can also click on the document in the browser and see its saved state in the preview below, for comparison.

    It is very nifty I must say and it is really nice to not have to worry about saving at all during writing.

    As for your second request, I *think* this is a bug, but I agree, it is annoying …

    Cheers, Niklas
    •  
      CommentAuthorfrode_
    • CommentTimeMay 14th 2011
     
    Thanks for the reply! This way of saving is even better than Scrivener's. In danger of stating the obvious: Ulysses is really well designed :)

    Frode
    •  
      CommentAuthormax
    • CommentTimeMay 16th 2011
     

    Thanks niklas, I couldn't have explained it better. For the second one: We are aware of that issue and will fix it in 2.1, which is not too far away.