Soft Apps

Explain the problem as you see it

There are so many errors in terms of "If a node has content and your caret is at the beginning of it and you hit Backspace, it will delete the node and merge this node's content with the node above it" how something is supposed to function and doesn't.

Keyboard shortcuts no longer work properly

...and I am bilingual myself but this has to be the one of the most poorly written paragraph in the English language "Initialization expressions are convenience functions, but are not live updating. So they won't change any prior field values from before you created the initialization functions, and you can change them after Tana fills a field if they need a manual touch." It seems a non-english-first-language speaking individual is drafting these documents. It literally makes my brain spin reading this stuff.

Why is this a problem for you?

...

Suggest a solution

Ya'll just received $15m in VC funds. Please hire a professional content curator or assign someone on your team and keep your documentation up to date, accurate, and written in proper sentences for proper comprehension. Guys, some of us are paying $200 a year, please up your game and show you're serious.

Explain the problem as you see it

1. @ mentions on empty nodes and hitting Shift+Enter does not work (creates a reference node)

2. copying the node/reference with Cmd/Ctrl+C, then paste into empty node with Cmd/Ctrl+V and hitting spacebar or any other key does not work (creates a reference node)

Why is this a problem for you?

...

Suggest a solution

fix

Explain the problem as you see it

This is becoming a major problem for me. I suspect 90% of Tana users are in a domain that requires some form of math formatting.

Why is this a problem for you?

It's already expensive as it is. Please at least provide additional formatting options; I am literally forced to move to a different tool because of lack of a simple and silly formatting feature

Suggest a solution

Stop your AI and other feature implementations and provide basic functionality first. If it's that difficult to implement, at least write a quick code to allow multiple consecutive sub/superscript character formatting.

Explain the problem as you see it

No one seems to grasp inline tags. I've raised the question on Reddit and Slack and there seems to be a whole lot of confusion in regards to inline tags.

Why is this a problem for you?

There is zero documentation in regard to the use of inline tags. The only documentation is that you can create them via the context menu, that's it. I've been struggling to grasp inline tagging for a long time and I can't seem to find anyone or any tutorial explaining inline tagging. In theory I know what @reference, inline #tag, and #supertag do and how they appear but can't differentiate in which context one provides a benefit over the other and vice versa. I'm aware that:

• @references: appear in the Library page

• inline #tags: do not appear at the end of a node in the Outline page & only in the Schema Page

• #supertags: creates a #tag at the end of a node as well as in the Schema Page

Suggest a solution

Please provide more documentation on the characteristics of inline tags and how they differ to inline references and node supertags. Providing some examples would be of tremendous help.