Skip to content
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

User experience is very poor when cquery server startup-crashes #60

Open
HighCommander4 opened this issue Nov 28, 2018 · 0 comments
Open

Comments

@HighCommander4
Copy link
Contributor

When the cquery server startup-crashes (for whatever reason), the user experience is as follows:

  • A small line of pixels flickers near the bottom right corner of the window.
  • CPU utilization is 100%.

If you click on the small ine of flickering pixels, it briefly resolves into a dialog which reads:

cquery has crashed; it has been restarted.

which stays on screen for a split second, and then disappears again, and there are just flickering pixels again.

If you open the Output window, you sometimes see output related to the crash in the "cquery" section, and sometimes it's just blank.

This is a really poor user experience. A more reasonable user experience would be:

  • The extension tries to launch the server once.
  • If it crashes on startup, it shows a dialog saying why (e.g. whatever output or logs the server produced), and asks the user to restart the extension or stop trying.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant