Tasks count numbers in the tags sidebar should depend on which view mode/tab is selected

[ghost]

I'm using GTG from Git (version: r5170.a795d66-1). Currently count numbers are shown when you display the tags sidebar. The problem is those count numbers are identical when selecting any of the following three tabs: active tasks, workview tasks and closed tasks. In reality those count numbers are valid just for the active tasks tab and should be different when selecting the workview tasks tab or the closed tasks tab.

[nekohayo]

It would be great if you (or someone you know or someone looking at this) can provide a patch for this.

[odoood]

Is this something that should be handled separately from #560 ? I'd like to take on this task if so, assuming this is still valid

[Neui]

What do you mean with "handled separately"? From what I can see they're different issues (but on the same component), but a problem is how you would "present" it to the user (like how would they choose?). I guess a "fix" for this issue could build upon a fix for that other issue, if it lays out some foundation (such as the UI issue), but this isn't a requirement.

I guess you could just always show the numbers of the currently selected view rather than of all tasks since if they want to do the latter they could just press the "all Tasks" tag.
Good luck figuring out a good way to implement such thing in liblarch+gtg, last time I looked into it (for an different issue) it wasn't great to deal with.

[odoood]

Since they're on the same component and related wasn't sure whether the approach to addressing this would be decided in conjunction with the other.

My thought for this is to have the task counts for both the selected view and all tasks for a given tag displayed, with the total in parenthesis next to the selected count. E.g. "My Task 5 (10)" for 5 of the selected view and 10 total of tag "My Task"

Haven't dealt with liblarch so thanks for the heads-up.

[nekohayo]

This was implemented in f336e44 and d0245fc (and a couple of older commits). However, it is sometimes buggy, see #1023.