a few questions...
i have just been wondering...
1. are there any swimming graphics for dink?
2. is it possible (with experience) to edit the dink engine so that during debugging you could see what part of the script is being executed? or maybe a stand-alone application that acts as a debugging dink emulator that can play certain parts of a dmod and show the user what is going on? or maybe creating error messages showing what is wrong during testing?
1. are there any swimming graphics for dink?
2. is it possible (with experience) to edit the dink engine so that during debugging you could see what part of the script is being executed? or maybe a stand-alone application that acts as a debugging dink emulator that can play certain parts of a dmod and show the user what is going on? or maybe creating error messages showing what is wrong during testing?
1. Not that I know of
2. Yes, just put the line debug("text"); into the script. And then find it in the debug textfile. I've always found it easier though to use say(); commands to visualise where the script is.
2. Yes, just put the line debug("text"); into the script. And then find it in the debug textfile. I've always found it easier though to use say(); commands to visualise where the script is.
1. ok
2. i was kind of thinking more of a way to see what is being executed inside a script. checking a debug log isn't going to do that
2. i was kind of thinking more of a way to see what is being executed inside a script. checking a debug log isn't going to do that
2. Won't using the
debug("Starting to execute so-and-so");
so-and-so;
debug("Done with so-and-so");
routine sort of answer your needs? If there's a specific point in the script you think is causing the crashing, you'll see if it gets past that point... Or what is it that you want to be able to do with it?
debug("Starting to execute so-and-so");
so-and-so;
debug("Done with so-and-so");
routine sort of answer your needs? If there's a specific point in the script you think is causing the crashing, you'll see if it gets past that point... Or what is it that you want to be able to do with it?
i want a real-time app that lets you veiw the scripts function while being executed, and the ability to continue one line at a time.
or maybe an app with the entire DinkC in it that checks the .script files for invalid lines or syntax errors etc. hmm... maybe i could make a checker... but a realtime view would be good, so i could see exactly where any bugs occure. i don't want to have to blindly edit code which i might mess up even more (i have done it before in PureBasic, but thanks to its in-built debugging functions i soon found at that it was working fine, and it didn't freeze, it was just very busy completing a loop waiting for network events to happen) do you get what i mean?
or maybe an app with the entire DinkC in it that checks the .script files for invalid lines or syntax errors etc. hmm... maybe i could make a checker... but a realtime view would be good, so i could see exactly where any bugs occure. i don't want to have to blindly edit code which i might mess up even more (i have done it before in PureBasic, but thanks to its in-built debugging functions i soon found at that it was working fine, and it didn't freeze, it was just very busy completing a loop waiting for network events to happen) do you get what i mean?
OK, now I see...
Try bugging Phoenix. Maybe he'll add the debug feature to EDC.
Try bugging Phoenix. Maybe he'll add the debug feature to EDC.









