Pin to taskbar
AnsweredI have the client pinned to the taskbar in windows. But each time i update workflowy this pin is lost and i have to pin it again. Not that big deal but a bit annoying.
-
Still have to pin workflowy after every update. And since you update the app OFTEN, the process of pinning the app over and over again is starting to feel like a standard procedure. Though this feels like some low hanging fruit that you can fix. Reducing little annoyances like this really can make a difference in how a program is valued...
-
This is a bizarre issue. Why does it keep disappearing. No other app does this, and I especially need workflowy accessible to fit into my workflow... it's ironic, but surely this is nearly trivial to fix.
Yes, I see Frank above claiming it's complex, but why is it that every single other application works perfectly fine and Workflowy is weird. It's not as if you are doing anything special here. Is it just that you've chosen a bad desktop wrapper app and need to wrap the wrapper (or change the wrapper)?
Is a workaround to have workflowy start on boot? Or does that fail with the same frequency?
-
I'm experimenting with creating a batch file with the contents:
START "" "C:\Users\ ... \AppData\Local\Programs\WorkFlowy\WorkFlowy.exe"
exitAnd adding this to the start-up folder for Windows in the hope that Windows will at least start workflowy automatically on boot, and this file should persist even if workflowy updates itself and unpins...
-
Hi folks! The team has grown somewhat over the last while and we may have the resources to get to the bottom of this. I've asked the developers to look into this!
REF: https://workflowy.phacility.com/T1915
(Internal link)
-
I haven't tested with a Workflowy update (won't be long though, I'm sure), but my workaround sort of works.
When I start up, Workflowy starts up too. And it starts because of a batch file that should not change when Workflowy updates.
When it starts, it appears in the taskbar as a running program. I've now unpinned it, because it's always running, because I don't close it.
So it sort of solves the problem, at least for my usecase (always having workflowy available).
Of course, it's a kludge, and I get a grey windows terminal pop up when the batch file executes, and it's not robust - but it's more robust than Workflowy unpinning itself, and means I never need to start it myself... it's always ready..
Please sign in to leave a comment.
Comments
12 comments