i've never really used the debugger but the ability to manually generate an error/warning "pop up" might be a tier2 only thing?
otherwise, i think the help files might be wrong/misleading with re: to what i distinguish as
error vs
warning.
to me, if it's an
error, the program will stop altogether and provide the error message (which it does, no matter what).
if it's a
warning, the program may carry on depending on SetDebugMode()
with that, what more functionality do you want beyond the above and below?
SetErrorMode(1)
this = LoadImage("this.png")
that$ = GetLastError()
last = timer()
do
if last + 3 < timer() then Print(100/0)
print (this)
print (that$)
print (ScreenFPS())
Sync()
loop
...in conjunction with the various SetErrorMode()s (which i just found out that you cannot change during runtime)?
Ie, Mode1:
meanwhile, looking at debugger stuff, i see there are 2 (completely) different
Log() commands. i guess if they were used properly (string vs float?), the
error-version could be helpful?
btw, if you want the warnings to pop up,
see the MessageBox function in MadBit's FileExplore ?
Oops, forgot about Message(). i only skimmed through blink's response.
