Search the Community
Showing results for tags 'Improved error logging'.
To improve Win Toolkit greatly and also a learning experience for me. I've decide do redo all exception handling, error boxes, log saving and uploading. I've been wanting to do this for a very long time as there has been a long standing issue when uploading error logs, which has affected about 95% of uploaded error logs. Basically the log file has weird ASCII characters, squares, etc... Which makes it unreadable. This issue of course helps nobody but rewriting it is a huge task! A lot of it will be backend code so you shouldn't really notice it. So now you're probably wondering how the changes will affect you. So here are the improvements I will be implementing. NOTE: No personal information is sent in logs. Just details about the computer hardware and the error details. Your benefits: Exceptions will be shown in YOUR language but when uploading and writing to a file. It will also add English if possible. This means in your log file, it will show both languages.Error logs file name will start with version number and then a unique error number. Easier to find a specific error. My benefits: Uploaded error logs will be uploaded in both languages so I can understand it.Upload logs will start with the unique identifier so that all errors which are the same will be group together. This will save me HUGE amount of time.Get rid of useless logs which help nobody Other Changes: Better log layout Error logs will automatically upload in the background there and then rather than at close. I may add a balloon tip near the clock to show when one has been uploaded/saved.Uploading will upload the string directly rather than the text file which is where most things of wrong with the characters.It's a huge task and I will be dedicating tonight to get it done. The biggest change you will notice is that exceptions will be shown in your language and bugs will get fixed quicker! Any questions, small requests or suggestions for this? Stage 1 (Done): Make new abstract class and efficient methods to get the job done.Record relevant details to help solve errors.Record more exception details such as stacktrace.BIG: Make logs readable from any language.Have a simple code to know which bugs are big, small or unhandled errors.Automatically give similar errors a unique ID so all the same bugs are grouped together.Show exceptions in user language.Stage 2 (W.I.P): Gradually upgrade old error messages into new ones with more detailShow more information to user by clicking a more detail button.