Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Users <em>hate</em> it when they're trying to get something done and you interrupt them. (I know, I'm one of them.) And here, you're not even giving them the chance to pick the <a href="http://blogs.msdn.com/oldnewthing/archive/2003/09/01/54734.aspx" rel="nofollow noreferrer">default answer</a>. I totally understand why, but tread carefully. Interrupt their train of thought as little as you can possibly get away with.</p> <p>(By the way, after this, does the app terminate, or do you recover and let them continue with what they were doing?)</p> <p>So you're giving the user two options: "tell us what you were doing" and "get on with it" (but with way more words than that on the button, even in Take Two). You really want them to pick "tell us what you were doing", but as I understand it, you implement it by opening a Web browser. <em>Huge</em> interruption. Once the user is done, they'll have totally forgotten where they left off. They'll also hate you and won't give you useful comments. (Heck, by the time the browser finishes loading, they're likely to have gotten distracted by another app (or by restarting your app), and leave the Web page "for later", by which time they've forgotten any useful context.)</p> <p>Instead, why not put a text box right there in the dialog? Might be a little more work for you to wire up initially, but I think you'd get better feedback.</p> <p>I'm thinking something like this:</p> <p><a href="http://www.excastle.com/misc/so958196.png" rel="nofollow noreferrer">http://www.excastle.com/misc/so958196.png</a></p> <ul> <li>Excuse courtesy of the <a href="http://pages.cs.wisc.edu/~ballard/bofh/bofhserver.pl" rel="nofollow noreferrer">"The Bastard Operator From Hell"-style excuse server</a>. They have more.</li> <li>Start with the cursor in the "Tell us what you were just doing" text box, so it's <em>easy</em> for them to give you feedback: just a matter of typing something and hitting Enter (or clicking the button with only three words on it).</li> <li>Make "Finish crashing already" a hyperlink, so it's there but de-emphasized. Left-justify it so people don't immediately associate it with the Cancel button it really is.</li> <li>If someone does fill in the box and submit a bug report, your "hey, thanks!" dialog could mention "by the way, if you get this again, you can click the 'I've reported this before' hyperlink", and show a screenshot with a red circle and arrow so they maybe notice.</li> <li>Any other text you want can go in a sidebar with a different background color. Banner-ad blindness will keep people from even seeing it unless they're in a curious (and patient) mood.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow would you improve our Unhandled Exception Handler error message?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJoe White
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow would you improve our Unhandled Exception Handler error message?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYes, Keep it really simple. But for twenty users, perhaps it's easier to walk over and ask 'em what they did? Just a thought!
      singulars
      1. PO
      1. USJeremy McGee
    2. CONow this is the kind of thinking I love from StackOverflow. Thanks Joe! Your redesign is getting us much closer to the end goal of a non-threatening easy to use error message. @JeremyMcGee - We were 5 users two years ago, 14 last year, and 20 now. The walk around is getting harder and we're building in a process for future growth. But, I hear ya. Talking to the user is always the most effective. We almost always do regardless of whether we get a bug report or not.
      singulars
      1. PO
      1. USGollyJer
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload