3 ms·

I'd suggest allowing bug reports directly from the app. You can capture highly useful context with the report. You have highly technical people here eager to he

• Keavon 2y ago
  We have this for crash reports. Perhaps that's a good idea to add a menu button for reporting other bugs. Do you have suggestions as to how to make that discoverable?
  • deskr 2y ago
    1. When this red error message is displayed, I'd have loved to see a "report this bug/issue/incident" next to it. That button would have opened a dialog box for me to write in, and telling that the context would be shipped with my bug report. To me it looked like a crash, but I do understand that programmatically it wasn't a "crash" or an unhandled exception. 2. Since this is a pre-alpha/alpha/beta version, there's nothing wrong with a green button with a picture of a bug anywhere in the interface. Just open a dialog explaining that although horrified, you'll be thrilled to learn of any bugs.
    • Keavon 2y ago
      Ah yes, you made me realize we could check if the node graph isn't open and tell the user to report a bug in that situation, which must have arisen from a tool or other WYSIWYG aspect of the program causing a node graph error. But we wouldn't show it if it arose from the user just noodling around with the nodes. That's a good idea that'll be worth us implementing, thank you for the suggestion.