Console/Debug Window
-
I was thinking of something that like, when you run Powder from the command prompt with the switch
"/d" (no quotes), a separate window would open and show everything that was happening in Powder in text form, and would also save as a log in the TPT folder, so if the Powder Toy crashes, we can give the developers info on it so they could identify info on the crash and fix the cause if possible. Also, in TPT without the /d switch at the command prompt, could there be a command you could use at the console to open the debug window?
Does this sound like a good addition and a possible addition? -
-
@MasterMind555 (View Post)
But I mean without using Visual Studio, I mean a window that is a part of the process its running from. (Powder.exe) -
@jamesoleruster (View Post)
Are you implying that some devs do not have a software capable of monitoring processes? -
I'm not implying that. What I'm saying is, a window that displays (say you enter !set type dust tnt in the console, debug window shows command and says "All DUST set to TNT" with the command entered above it, something like that) the info in a log type fashion running from the same process but different window. It would mainly be for those who only have the Task Manager, and/or aren't devs.
-
What's the point?
It would mainly be for those who only have the Task Manager -
what? Every Windows computer has a Task Manager. It's part of the operating system.
I mean like, if you want extra-detailed, go ahead and attach a debugger or as Mastermind suggested, Visual Studio. The things you need to add to realise your idea would be speed-consuming.
bool dbg = false;
for(short i=0;i<argc; i++)
if(argv[i] == "/d") dbg = true;
// and then to every single event you want a text in
if(dbg) sprintf(*console, "All %s set to %s", start_element, end_element);
I mean, you can do it in a mod, but it's pointless to add to the official if you already know that the console works reliably and that you can achieve a similar effect with another external process.
