Forb Feature Request

[Forboding Angel]

THanks for the warning... I imagine that this is prolly a good idea, however, would you set infolog.txt to give more useful errors?

on gadgets the errors are ambiguous 99% of the time. Widgets aren't a whole lot better, but at least they spam the hell out of the console before spring goes tits up.

[trepan]

examples? (errors & associated sources)

[Forboding Angel]

If a gadget bites the dust in svn all I get is "Badstd:alloc". It's possible that this could be due to the changes to lua from 76b1 --> Svn, but it would be infinitely more helpful if the infolog or somehting showed what gadget/widget caused the crash and where it was in the script when it went tits up.

Widgets as a general rule are fine because they spam the console/infolog before dying, but gadgets are relatively silent in this manner.

[Argh]

Um, what about the Scream thingie? Is that what that's for, or is it for something else? I do all of my debugging with simple echoes in my functions, so that I can trace it and report values as it runs, myself, so anything that might make debugging less of a chore would be cool.

[FLOZi]

If a gadget bites the dust in svn all I get is "Badstd:alloc". It's possible that this could be due to the changes to lua from 76b1 --> Svn, but it would be infinitely more helpful if the infolog or somehting showed what gadget/widget caused the crash and where it was in the script when it went tits up.

Widgets as a general rule are fine because they spam the console/infolog before dying, but gadgets are relatively silent in this manner.

If a gadget dies properly it will give error messages exactly the same as a widget.

bad std::alloc is a differen't problem altogether.

[Forboding Angel]

Fair enough. As I'm not a lua guy there isn't much of a way that I can refute anything said here.

[imbaczek]

no reproduce'y= no fixy; see also: trepan's post.