Search for a command to run...
Tcl/Tk Text Widgets For Debugging and Errors
I have over 40 years of programming experience using a variety of languages over the course of my career to develop real-time solutions for real-world problems.
Keyboards connect us to the world and, as a keyboard enthusiast, I am searching for the ideal keyboard.
No comments yet. Be the first to comment.
In this series I delve into the world of MQTT (Message Queuing Telemetry Transport) using Tcl/Tk.
MQTT Application - Goals and Objectives
Looking at an article for the book “Gist of Go: Concurrency,” I also stumbled across a reference to “High-precision date/time in SQLite” written by the same author, Anton Zhiyanov. I use SQLite in man
Happy 10th Anniversary - RUST!
Login failed. It appears you are offline
Modern Fortran: Tricks of the Software Engineering Trade by Damian Rouson Sometimes I think I'm one of the few programmers routinely using Fortran long after my Engineering studies too many years ago. As such, I'm pleasantly surprised when a new book...
Make GIT a Habit
When developing an application from scratch, it is often helpful to know what your code is doing while it is running or if it is still running at all. Although we can run our application in debug mode, we may not capture all the details we're interested in seeing.
Two text boxes appear at the bottom of our application: Script Status and Error Status. I use the following "debug" and "errors" procedures to print to the Script Status and Error Status text boxes, respectively.
The procedures are the same, other than the path to the textbox receiving the text messages. The procedure ignores messages when the debugVerbose variable is false.
When the "debugVerbose" variable is true, and the textbox widget exists, the procedure appends the text message to the textbox. If the widget does not exist, the "puts" command sends the message to the console.
set debugVerbose true
proc debug { args } {
if { $::debugVerbose } {
if { [winfo exists .statusMessages.debugMessages.debug.debugMsgs] } {
.statusMessages.debugMessages.debug.debugMsgs insert end "$args\n"
.statusMessages.debugMessages.debug.debugMsgs see end-2c
} else {
puts "$args\n"
}
}
}
proc errors { args } {
if { $::debugVerbose } {
if { [winfo exists .statusMessages.errorMessages.errors.errorsMsgs] } {
.statusMessages.errorMessages.errors.errorsMsgs insert end "$args\n"
.statusMessages.errorMessages.errors.errorsMsgs see end-2c
} else {
puts "$args\n"
}
}
}
The above procedures display text in their respective windows or to the console depending on the value of debugVerbose. Of course, we can use variables to manage windows independently.
Once we have finished developing our application, we can limit the displayed messages without overwhelming the user.