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
When synchronizing notes the first time, that's a long-running job. Seeing clear progress reporting really helps, especially first-time users who don't know what to expect.
The "Download n% complete" message shows up on the status bar, but then disappears after some time or some event, I'm not sure which. When the status bar remains empty for more than a few seconds while a long-running job is running, it becomes difficult to tell the difference between "running" and "stopped". If there is some way to make status reporting more persistently visible, that would really help.
I don't know enough about Qt-based applications to know whether this is a common limitation from Qt or something that we could reasonably try to improve in this application. I'd even be willing to dive in and try to improve things if someone else would suggest a sound strategy.
The text was updated successfully, but these errors were encountered:
Yes, I know about this problem and its also annoying to me.
Its not only in first sync, but also when e.g. "sync error" happens.. and other situations.
So I definitely want to fix this, I'm now yet sure how. But it should be one of "next steps".
When synchronizing notes the first time, that's a long-running job. Seeing clear progress reporting really helps, especially first-time users who don't know what to expect.
The "Download n% complete" message shows up on the status bar, but then disappears after some time or some event, I'm not sure which. When the status bar remains empty for more than a few seconds while a long-running job is running, it becomes difficult to tell the difference between "running" and "stopped". If there is some way to make status reporting more persistently visible, that would really help.
I don't know enough about Qt-based applications to know whether this is a common limitation from Qt or something that we could reasonably try to improve in this application. I'd even be willing to dive in and try to improve things if someone else would suggest a sound strategy.
The text was updated successfully, but these errors were encountered: