Hmmmm... So maybe there should be an error level which is a pop-up warning in nightlies, but just a log message in stable releases?
Maybe a good idea, but it probably makes more sense to have a game-release-centric choice rather than engine-release-centric. So may me when you create a game, it could default to having "Show bug warnings" on, but you would have the option of tunring that bitset off when you release your game if you don't want players to know about bugs. Something like that maybe? Another possibility is to have a much less obtrusive type of pop-up for these mid-level bug-warnings. Maybe a small red box that just says something like: "BUG WARNING: " & short_error_text which pops up briefly without interfering with gameplay and then vanishes on its own in a few seconds, maybe with rate-limiting so it doesn't happen any more than once a minute. On Tue, Jan 29, 2013 at 01:54:00AM +1300, Ralph Versteegen wrote: > Thinking about error levels a bit more. Should we always show a > visible error message if you do something which is clearly a bug but > might not cause a major problem? Maybe only in nightly builds? There's > the risk that we mistakenly think a condition indicates a bug when > it's either a non-bug error or not an error at all. We have lots of > impossible looking stuff printed to c/g_debug.txt regularly, so I'd > rather avoid having thousands of checks to pop up visible debug > messages. > > Also there ought to be error levels for showing a visible error but > which don't encourage the user to immediately quit (they could still > give the option if there are lots of errors in a row). > > On 27 January 2013 18:51, <[email protected]> wrote: > > teeemcee > > 2013-01-26 21:51:43 -0800 (Sat, 26 Jan 2013) > > 455 > > debugc now uses ErrorLevel/ErrorLevelEnum constants with different > > definitions to before (mostly implemented this time) > > > > Also changed order of debugc's arguments, split fatal_error_shutdown > > out from showerror, fixed a crash if showerror is called before > > setmodex, and updated error levels in array.c and filelayer.cpp. > > > > I would like to start using debugc throughout the engine. The error > > levels aren't set in stone; I'm not totally happy with them myself. > > --- > > U wip/allmodex.bas > > U wip/allmodex.bi > > U wip/array.c > > U wip/common.bi > > U wip/common.h > > U wip/common.rbas > > U wip/common_base.bas > > U wip/common_base.bi > > U wip/const.bi > > U wip/filelayer.cpp > > U wip/vectortest.bas > > _______________________________________________ > > Ohrrpgce mailing list > > [email protected] > > http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org > _______________________________________________ > Ohrrpgce mailing list > [email protected] > http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org > _______________________________________________ Ohrrpgce mailing list [email protected] http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
