-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Misc. Feedback on v4.0.0 #116
Comments
Yeah, I found the new command flow to be essentially exactly what I was after—I never really found anything else I personally wanted to iterate after the latest release.
your feedback
|
I'm glad to hear that you were happy with the new architecture we discussed!
Haha, no worries :). I wish you a good experience with macOS! I've never regretted being on Windows/Android, rather than macOS, until I wanted to buy a health tracker and learned how much worse (particularly in accuracy, but also in UI, app support, etc.) even the best Android smartwatches are vs. the Apple ones =(. Re: 4, that might well have been me, my memory is just bad T_T. Re: 7, I would find this feature genuinely desirable, but not if it requires any meaningful effort on your part to implement. Anyway, I figured FlowLauncher plugins would have some ability to display themed colors in FlowLauncher commands, but maybe they don't? If not, maybe just insert two quotation marks, i.e. display commands like -- Finally, since my original post I've noticed another point where your FlowLauncher plugin feels better than the native TogglTrack app: The latter only autocompletes entries from the last 1-2 months. I try to keep my time entry phrasing consistent over time, and for rare time entries this is much easier via the FlowLauncher plugin since its autocomplete covers more than just the recent ones. |
Hahah, cheers! Definitely loving it so far (macOS less... but I've hit it with yabai sufficiently hard that it's submitted to my desires 😂).
I don't expect it to... I've added it to my to-do list, I reckon I'll manage to find some time to implement & release this long weekend...
I vaguely remember playing around with something like this (possibly I'll have another try, and fallback to quotes if needed.
YES; I'm glad you noticed—this is also a massive thing for me, and frustrates me to no end with the Toggl first-party interfaces and even Timery, the otherwise-stellar alternative I'm using on my MacBook. Having to run a report to try to find a previous description is frustrating as hell. I can't remember if the autocomplete covers the last 366 days (Toggl's single-request API limit), or if it's extra keen and tries to paginate until nothing is found... either, it's much better 😛 |
This one might warrant being listed as a Feature in the Github readme. Something like "auto-complete even for non-recent time entries", or a more eloquent phrasing of that. Or maybe just "more comprehensive auto-complete". |
Good idea, thanks! |
Closing in favour of #117. |
Follow-up to #28 and #90.
Hey there, once again apologies for the very belasted feedback. Unfortunately, I'd made a mistake of promising to "systematically test the new command flow", which made this task seem so daunting that I actively procastinated on it^^. So this time I figured I'd just post what I notice within an hour.
Usage
Regarding my recent usage of the plugin: I'm still using a bunch of different tools to enter time entries: mostly the desktop app, occasionally the FlowLauncher plugin, sometimes the mobile app. As mentioned previously, one pro of FlowLauncher over the desktop app is that the former interacts much better with Windows 11's virtual desktops. Whereas when the TogglTrack app is open in one of the other desktops, then clicking its taskbar icon switches my desktop right when I wanted to track time. So this causes a context switch and interruption right when I wanted to start tracking some productive activity.
Out of curiosity, how do you like the new command flow yourself? You mentioned you'd created this plugin because you didn't like the desktop app, so I imagine you've been using the new command flow a lot more than me.
Feedback
t take a walk
.tgl continue ta
-> Enter". That's because the "take a walk" entry is never the top-most entry. But that's fine, "t ta
-> Alt + 3" works just as well.t
ort
ort
), it would be neat if the other TogglTrack commands were a bit higher. Currently the top five results are "Start an empty time entry now", three Usage Tips, and the current running time entry. So all commands like "edit", "delete", "reports" etc. are offscreen. I figure some of those Usage Tips etc. don't need to appear until the potential time entry has at least one letter.t edi
for "edit"), then I see 20 time entries and only then the "edit" suggestion. I do like that "edit" is not appearing above the first time entry suggestion, but this priority level seems a bit low. Also, in this situation, maybe the Usage Tips should be prioritised below the plugin commands.day-5
, notday -5
. Whereas for tasks it's exactly the other way around, i.e. only<task> -t -5
works, but not<task> -t-5
or<task>-5 -t
.The text was updated successfully, but these errors were encountered: