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
I am using Zeal 0.3.0, 32-bit on Windows 8.1 64-bit.
Anytime I open the Docset dialog to download new and update existing docsets, I am unable to close the dialog. I am presented with an error message, "Please wait for all operations to finish" even if I have not issued any download or update actions. Thus, I cannot continue to view the downloaded docsets as in the snapshot attached
Also, I made a directory on my secondary harddrive's partition to keep all my docsets (due to storage size issues). Unfortunately, Zeal does not persistently save the path to the docsets hence I have to update the path in the Preferences dialog each time I want to use Zeal. This is similar to the issue #609.
I hope these issues would be resolved
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related requests.
lockbot
locked and limited conversation to collaborators
Sep 16, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am using Zeal 0.3.0, 32-bit on Windows 8.1 64-bit.
Anytime I open the Docset dialog to download new and update existing docsets, I am unable to close the dialog. I am presented with an error message, "Please wait for all operations to finish" even if I have not issued any download or update actions. Thus, I cannot continue to view the downloaded docsets as in the snapshot attached
Also, I made a directory on my secondary harddrive's partition to keep all my docsets (due to storage size issues). Unfortunately, Zeal does not persistently save the path to the docsets hence I have to update the path in the Preferences dialog each time I want to use Zeal. This is similar to the issue #609.
I hope these issues would be resolved
The text was updated successfully, but these errors were encountered: