I have an application which interacts with two or three other non-gambas applications and daemons and I am not absolutely certain these interactions are completely robust.
I had littered the code with PRINT statements to get console output at various critical points of the application. Soon it got too much and I thought I would replace the PRINT with DEBUG (getting location information in the output) and giving me a way to turn these messages on or off, leaving the reduced number of PRINT statements to appear in a "cleaner" console output. So far so good. The DEBUG statements have proved invaluable in helping me to get the code into a working state, but they do not appear at all when I run the compiled application in a console. I never did find the way, which I thought must exist, to turn these messages on and off. The manual suggests it is possible to see DEBUG output in the compiled app's console but is completely silent on how this might be achieved. Any suggestions? Richard ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
