A tale of two crashes
Moderator: GZDoom Developers
A tale of two crashes
Which style of crash report do you like better? The one on the top or the one on the bottom? The one on the top requires you to copy-and-paste it into a post on the bugs forum. The bottom one requires you to click just one button. Feel free to answer in the comments.
Old versions of ZDoom report crashes like this:
The next version of ZDoom will probably report them something like this:
Edit: Update the second window to a newer design.
Old versions of ZDoom report crashes like this:
The next version of ZDoom will probably report them something like this:
Edit: Update the second window to a newer design.
Last edited by randi on Wed Feb 02, 2005 1:51 pm, edited 1 time in total.
- Mike.Reiner
- Posts: 55
- Joined: Mon Nov 15, 2004 7:35 am
Does the one at the bottom auto-post in the bugs forum so that people could suggest solutions, identify duplicates, share similar experiences etc or do they just go to you? If they do just go to you, do you normally find discussion of the type mentioned useful?
Other than that, I have no real preference. People may be more inclined to simply click a button everytime there is a crash rather than copy, log onto zdoom, make a new post and paste (ie old method). So you might get more info. However, some people are always suspicious of programs that contact the internet and they may not like it as much.
Other than that, I have no real preference. People may be more inclined to simply click a button everytime there is a crash rather than copy, log onto zdoom, make a new post and paste (ie old method). So you might get more info. However, some people are always suspicious of programs that contact the internet and they may not like it as much.
Last edited by Enjay on Wed Jan 26, 2005 5:25 pm, edited 1 time in total.
- Mike.Reiner
- Posts: 55
- Joined: Mon Nov 15, 2004 7:35 am
- wildweasel
- Posts: 21706
- Joined: Tue Jul 15, 2003 7:33 pm
- Preferred Pronouns: He/Him
- Operating System Version (Optional): A lot of them
- Graphics Processor: Not Listed
- Contact:
I'm undecided - the old one is more unique and less like Microsoft's "Oh, we know this program sucks, but tell Microsoft about it instead because the programmer doesn't need to know" error message, but the new one is more convenient-looking.
I'm not sure how the new one could be changed to look less like Microsoft's, but there needs to be some differentiation (so I don't just disregard the crash and click "Don't Send" every time).
I'm not sure how the new one could be changed to look less like Microsoft's, but there needs to be some differentiation (so I don't just disregard the crash and click "Don't Send" every time).
- Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49067
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
And that can easily happen. Many users simply assume that this is Microsoft's doing, ignore the crash log and potentially come to the forum whining 'I can't tell you what happened because I don't want to send the data to Microsoft.'wildweasel wrote: I'm not sure how the new one could be changed to look less like Microsoft's, but there needs to be some differentiation (so I don't just disregard the crash and click "Don't Send" every time).
That list would be enough to put some people off. Where are these files? Where did they come from? How easily can a user find them to analyse the content? Files with names like userinfo.txt may alarm some people "OMG it must have my credit details etc in it".The error report contains these files:
report.txt
minidump.mdmp
local.txt
userinfo.txt
What about the other questions - like how easily would these reports become forum posts? I can imagine someone wanting to send you a crash report, but possibly also wanting to report it publicly and discuss it. Thier "work" has now doubled if this doesn't report to the forum. Although, if a lot of these are generated, they would clutter the forum.