You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sort order is different between the Checklist and the Tasks plugin. If we know exactly what the checklist sort order is based on, then we should be able to sync them up. Could you please let us know?
The tasks developer ClaireMcrae says (on the Discord task-management channel):
Tasks has ‘sort by function’ for custom sort order, so if you can figure out how the other plugin’s sort is implemented, you can probably teach Tasks to use the same sort order.
If interested, we could pick that up in Tasks.
Use case
I use Checklist and I use prefixes of symbols and emojis to set the priority (sort order).
I would like to have a filtered list embedded in a note or canvas, sometimes. One way I can do this is with the Tasks plugin, but it has a significantly different sort order, especially when emojis are involved.
Alternatives
An embed feature for Checklist. (I'm guessing that's a lot of work.)
The sort order is different between the Checklist and the Tasks plugin. If we know exactly what the checklist sort order is based on, then we should be able to sync them up. Could you please let us know?
The tasks developer ClaireMcrae says (on the Discord task-management channel):
Use case
I use Checklist and I use prefixes of symbols and emojis to set the priority (sort order).
I would like to have a filtered list embedded in a note or canvas, sometimes. One way I can do this is with the Tasks plugin, but it has a significantly different sort order, especially when emojis are involved.
Alternatives
An embed feature for Checklist. (I'm guessing that's a lot of work.)
Greatly restrict the prefix characters I use for sorting task items. E.g. I think this order works in both:
`
^°©®+<~★ ¢$£¥€₱₹ 0-9 aAbBHowever the emojis are much better for quickly communicating a task item's purpose and priority.
Thank you!
The text was updated successfully, but these errors were encountered: