SRL Archive - MSI Suggestions

Less clutter for those who do not want to see it, but still there for those who do. It allows you to see the important stuff, and none of the unimportant details, for the non devs.

It would have to be defined and such (not too sure how to do that, tried once, got an exception)

something like this:

  If (DebugLevel =  DEBUG_SMALL_DETAILS) or {$ifndef SimbaDebugConsole}then
  writeln(DebugMSG);
  else
  begin
  DebugLn(DebugMSG)
  end; 
   

in place of the single writeln we have.

Because it would be a define, it could be commented out if someone wanted to see everything.
Thoughts?

Why not just use srl_Warn with a minimal debug level and set the global debug level likewise?

From: EvilChicken!
Why not just use srl_Warn with a minimal debug level and set the global debug level likewise?

I think he's talking about the actual console, not the debug box.

From: Coh3n
I think he's talking about the actual console, not the debug box.

I know he meant the console; I just posted something I thought the be a better alternative – one can simply disable all srl_Warns using a single line command; and whenever srl_Warns actually are used, one can mark and copy stuff from the debug box. As far as I know of, there is no such possibilities with command prompt windows?

The console can be hidden with the button in the menu bar..

From: EvilChicken!
I know he meant the console; I just posted something I thought the be a better alternative – one can simply disable all srl_Warns using a single line command; and whenever srl_Warns actually are used, one can mark and copy stuff from the debug box. As far as I know of, there is no such possibilities with command prompt windows?

Oh does all the debug lines also show up in the console? If that's all he wants, then yeah, nick, just use the srl_Warn thing. My bad. :o

Tbh, I have pretty much no idea what any of that means, or, more importantly, what i should do about it.
With what I'm saying, is everything gets (in this case, details), put in the console, and anything above debug_details gets printed into the debug box.

Sounds good, along with saving everything to file.

~RM

Wow, it took me this long to realize this thread was in the MSI section. >.<

AFAIK, RM is working on a new debugging system which, I'm sure, will have several debug levels for the user to choose (unless that was added back in recently).

From: Coh3n
Wow, it took me this long to realize this thread was in the MSI section. >.<

AFAIK, RM is working on a new debugging system which, I'm sure, will have several debug levels for the user to choose (unless that was added back in recently).

Indeed, I might as well just add this in there. :)

~RM

Sweet :)
Idk, its just that, i like it that way. I can see what i need to see at a glance, and for debugging, i can get far more detail, without cluttering the debug box. Looking forward to the new debug.simba, it looks pretty awesome from what i've seen.

You can now set the level to debug during script setup. The lower the number, the less it will debug. :)

You could also save all debug levels to the debug file, but only show the ones the user wants in the debug box.

From: CX gamer
You could also save all debug levels to the debug file, but only show the ones the user wants in the debug box.

That's exactly how it works. ;)

Ooh I'm sorry, I should have checked. Good job.