Zugg Software :: View topic

Wizard Joined: 14 Oct 2000 Posts: 1368

Sometimes when you press the "Send feedback" button and send feedback it fails to send, and you lose all the text you wrote and have to rewrite it. Now I have to re-report the bug report Crying or Very sad

.

Edit: It would be nice if it was possible to keep track of what bug reports have been sent so that you don't re-send already reported bugs. Also a category combo-list would be nice, and now when I am at it a title of the report could be good too :P.

Posted: Tue Aug 08, 2006 1:08 pm

In my experience, it fails to send when you are not online and it would be nice if they can be chained together, but unfortunately they are not right now. You can regain the last failed feedback by looking for bugreport.txt in the CMUD directory. It contains all the technical stuff Zugg would need and your comments. Of course since it's text file you lose the screen shot.

You can email bugreport.txt to Zugg.

Posted: Tue Aug 08, 2006 8:36 pm

Rorso: Unfortunately, I have little control over the bug report and feedback option. I'm using the same crash-dump reporting system for the send feedback option. And this code is written to work in an environment where the application has just crashed and memory might be corrupted. So there is a limited amount of stuff that this component can do in this environment. The most important part is to make sure it is able to send crash dumps. It's already much fancier than anything we have had before, so you might need to live with it's limitations.

As Tech said, if your crash dump isn't sent, then it gets saved to the bugreport.txt file. However, this does not apply to the Send Feedback option I'm afraid, since it's not a real crash dump.

There is no way to keep track of what bug reports have been sent. In fact, it's very useful for me to receive multiple crash dumps for the same bug. Our database backend is smart enough to combine reports from the same bug into a single trouble ticket. And many times the extra information from multiple reports of the same bug can be useful in tracking down the problem. It also helps tell me which bugs are the most reported, and therefore the most critical.

In order to keep track of bugs that have been sent, the crash dump system would need some sort of database, and that's just *way beyond* what is possible during a crash recovery process.

I've thought about categories, but in the past the vast majority of people just ignore the category anyway, and it doesn't really help me much on the backend either. Also, the more questions you ask from a user, the less likely they are to send a crash report. So that's why I'm trying to keep it as simple and painless as possible.

I'll check and see if it's possible to save the feedback text so that you won't lose it if it fails to send, but this will probably be a pretty low priority for now.

Posted: Tue Aug 08, 2006 10:11 pm

I looked at some of the madExcept options for the crash dump system. I enabled a new button called "Save bug report". It saves the crash dump to the bugreport.txt file, but also will APPEND multiple bug reports to this same file. It has built-in smarts so that it won't duplicate identical bug reports.

So, when you are offline, you will be able to use this "Save bug report" option to accumulate multiple reports in a single file, and then email me the bugreport.txt file when you are done and get online later.

I haven't yet determined how to save the feedback text though, so that will wait. I was just checking to see what I could do that was fast and easy right now.

Posted: Tue Aug 08, 2006 11:29 pm

That's great news Zugg.. I was doing a lot of offline testing... I'll be looking forward to using it especially on planes (the one place I seem to have free time these days) now that Cingular cellular card gets me net access almost everywhere else.

Posted: Wed Aug 09, 2006 5:01 pm

Hmmm...."CMUD on Planes". Maybe I can sell the movie rights Laughing