BugsCode-Jack·10 days ago
In Progress
Format: "Action" (Task): saving fails.
When I write text into the body of an "Action" Object, saving fails.
The text disappears on its own after closing the Object.
In addition, a syn-error appears on the right bottom.
Finally, an error warning appears, but it is not recognizable, because of the small font and the WAY too low contrast!
Here a screenshot of the error message -- I made it better visible by doubling the size and increasing the brightness & contrast:
I tried to add an existing Collection to the Object's header, so that there would be a chance that AnyTwo could save it to a certain and different place. But it didn't help.
6 Comments
Sign in to comment
C
Additional error message in a different format (and this time even recognizable, WOW!!!):
As of 0.1.6 the Action format (now called Task type) has no body, no editor, just properties.
Is this intentional or a temporary workaround for the issue described in this post?
By the latest Alpha changelog, this is intentional:
> Opening a task, or another item whose format has no text body, no longer shows an editor that silently throws away what you type — the body is read-only, and the title and properties stay editable.
I use the body of objects with Action layout on Anytype as disposable scratchpad, references, and also for some long living types that have a clear open/closed state (checklists, issues, etc). Guess I'll need to move those to Page type and custom properties :|
I also use the body as scratchpad and then, if the length of the contents call for it, change the type from Task to Page, Project or whatever.
However, with this new architecture, I see the Task as a simple container for fixed data that I can insert as a link on the top section of a page. For it to fit well in my workflow, I would need the ability to do, at least, some of the following:
- Linking to an existing task without having to scour for it through a long list of objects.
- Opening the Task link as a pop-up, or viewing its contents on hover, or inserting it as a card/synced block with full details.
- Creating a /task directly from a page.
- Inserting a filtered view of Tasks in a page.
I agree that, in its current implementation, Tasks are quite cumbersome to manage, but I am quite sure that enough of my requirements, or maybe an even better approach, will be there in due time.
Right now, Task type in Anytwo is kinda useless to me, specially since it won't be easy to change object type/format after creation. Maybe with discussions implemented in Anytwo and text formatting support for text properties it becomes usable in my existing workflows...