[feature]: hide Left/Right buttons when not enough tags

[Marco-Christiani]

There are two left/right arrow buttons in hq-tag-row that do not appear to have a function. Expected behavior may be to cycle through selected tags or periods of time?

PS This is great, thank you for sharing your work!

[arkadianriver]

Thanks!
Yeah, I should probably hide the buttons when the aggregate tag width is less than the width of the containing box. That's all they're for: they're an alternate way horizontally scroll the list of tags besides Shift+scroll, nothing fancy like you describe :O)

[Marco-Christiani]

Are you accepting new feature requests? I had some thoughts but don't want to bother you if this is a simple side project.

[arkadianriver]

Not committing to implement anything soon, but yeah, I'm happy to hear any ideas, particularly from those who might wanna use it.

[Marco-Christiani]

I would love to use this to monitor tasking across projects. Right now I use the Projects+ Todo+ extension to track the todo files across repos. It would be nice if this app had an option to aggregate separate todos into one view, or just load a view for each todo its given and a way to navigate through each view. This would be fantastic (although I am not an express dev so I cant help much). Just my two cents.

As an aside, I think the Projects+ Todo+ extension had some functionality for aggregating todo files which would have solved this issue but I am not 100% sure because the vscode action currently errors out.

[arkadianriver]

Nice idea. I was thinking of something similar for multiple people. Each person would have their own todo file to maintain. As it is now, you can use tags starting with @_ to represent resources assigned, and a different Gantt chart stream starts in parallel for each resource. Separately maintained files would make it easier on the PM for sure.

For your multiple project todo files, it could definitely take advantage of the project pages and combined archive, but I don't know how the Gantt chart would order the active items for the separate projects. We couldn't assume they'd be working in parallel in case the same person is working on multiple projects, and we wouldn't want to list all the tasks one after another in one long stream giving whole projects priority over others. Interleaving the tasks across projects might be an option, but I'm not sure how realistic that is. What do you think?