Improving "Bug Reports" feature of standalones

William Prothero prothero at earthednet.org
Fri Jul 17 17:30:48 CEST 2015


Tom:
I second that. Without this info, the bug report is pretty useless to me. I assume all bugs are caused by my code, and may be platform dependent, so this info is critical.
Bill

> On Jul 17, 2015, at 8:23 AM, tbodine <bodine at bodinetraininggames.com> wrote:
> 
> Hi all.
> 
> I use the built-in "Bug Reports" feature of the standalone builder, which
> provides basic info. via email when a user hits an error. Problem is these
> reports omit basic, key details, such as the platform and my codebase
> version number. And users never include those in their comments.
> 
> A typical bug report sends this info:
> Executing at [timestamp]
> Type: [ex.: Chunk: can't find stack]
> Object: [ex.: a stack name]
> Line Num: 366
> Hint: [ex.: a handler name]
> Comments: 
> 
> Is there a way to tweak the contents of the error report to add a product
> version number and platform stored in a global? 
> 
> Thanks,
> Tom
> 
> 
> 
> 
> 
> --
> View this message in context: http://runtime-revolution.278305.n4.nabble.com/Improving-Bug-Reports-feature-of-standalones-tp4694032.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode




More information about the use-livecode mailing list