A new version of Anytype for Desktop is released: 0.26.1 You can check out the full list of new features and bug fixes below, but some of the highlights are:
In this release we implemented an option to allow users to permanently delete their Anytype account, including objects stored on the backup node. This should address some of the concerns shared here.
You need to know what’s on the list for tomorrow? Now you know! We’ve added relative date filters to Set views
- You choose the date Relation you want to filter on
- You choose the kind of filter range
- You set the date range
You have many options to choose from, like showing all events with a due date exactly three days from now:
Let us know if your date range filter option or scenario is missing.
The Anytype desktop application has a shiny new app icon, so the desktop, Android and iOS icons are the same!
- Account: Permanently erase your Anytype account, recovery phrase, and objects stored on the backup node.
Note: You will have 30 days to change your mind. After 30 days, this is irreversible, and we cannot help you recover your data.
- Editor: Highlight block now changes style to paragraph when pressing backspace in empty block, like lists
- Editor: Objects in “move to” menu are now being sorted by “last modified” date
- Sidebar: Drag-and-drop Blocks directly to the sidebar to move the Block to another Object
- Sets: Date filters receive support for relative values
- Relations: Show featured relation star by default in the relations panel
- Editor: Dragging and dropping Blocks into columns was reworked and now works more consistently (good looking out @ignatovv)
- Sets: Sets sometimes were resizing incorrectly when making changes to Objects within the Set (thanks @Cernel1337 for reporting!)
- Editor: Chinese input methods when editing title or description in pages like Object Type or Set was fixed (thanks @Others we fixed it)
- Editor: Incorrect search order of options when searching for some languages in code block (thanks @Flip for noticing!)
- Editor: Inability to delete selected blocks that have nested children (thanks @hysci, this issue is now fixed!)