LociOiling Lv 1
Devprev release 39 fixed problems with seeing shared solutions, but there are still several issues:
- Downloading shared solutions remains very slow, usually taking 30 seconds or longer.
- The new "Downloading Solution List" dialog with the animated clock is slow to appear, taking around 10 seconds after an action starts.
- The "Downloading Solution List" dialog disappears before the download has actually finished.
- When a download fails, there is no error indication. The left-hand side of the Open/Share Solutions dialog remains blank. Previously, an error message, "There was an error getting shared solutions from the server", appeared on the left.
- When uploading a shared solution, the "Downloading Solution List" dialog appears, and takes quite a while to complete. The solution just uploaded does not appear on the left hand side. The "Refresh Shared Solutions" button repeats the download, and the shared solution normally appears on the second try.
- Getting shared solutions still fails often. For example, at the moment, I can't see the shared solutions on puzzle 2472, even though they were there earlier today. Server issue, seems the same on main and devprev.
Other functions, such as the puzzles menu, the cookbook, and the compound library also depend on downloads from the server. They're inconsistent in how they handle timeouts. The puzzles menu may show a "Downloading Puzzle Files" dialog with an animated clock. The cookbook and the compound library don't have a similar dialog.
The cookbook in particular often appears empty when a client first starts. The "Refresh Cookbook" button normally fixes that, but it appears it can fail as well. There's no error message that appears when it fails.
For consistency, any potentially blocking action should put up a "loading" message with a cancel button. An error message should appear if the action times out.
The compound library window refreshes itself every so often. It appears that other actions can continue while that's happening. So a "loading" message doesn't seem necessary. An error message if a refresh fails would be helpful, however. Ideally, a failed compound library refresh would leave the previous results displayed.

