Skip to content

Issues.00237

Jump to bottom
Website user edited this page Jan 25, 2019 · 3 revisions

00237: see which tcl scripts were sourced

« 00236 | Issues | 00238 »

Summary: see which tcl scripts were sourced

Created: 2010–04–15 16:19

Status: Released

Category: Request

From: frankie

Version: 2.0

Released_In: 2.2

Description:

this is a request for a feature similar to the Help→About→Plugins dialog, which shows which plugins were sourced, and which ones had errors at initialization. Knowing which tcl scripts were attempted to load, found, and had errors would be a useful tool when troubleshooting modifications to config files and tcl scripts.

There are 4 main statuses we are interested in knowing for tcl script debugging:

  1. The script was never requested by a config file (in which case it wouldn't be in the list and would represent a config file problem)
  2. The script was specified in a config file but not found, or not able to be opened for whatever reason
  3. The script was specified, found, and able to be opened but gave an error when sourcing
  4. The script was specified, found, sourced, and had no errors

Comments

frankie October 18, 2010, at 09:44 AM: Also, it would be interesting to know if a script was found on the file-system or in a package file.

frankie October 18, 2010, at 03:06 PM: You can see this list to help with troubleshooting by going to "Help→Scripts". Yellow items correspond to scripts that were requested but could not be opened. Red items indicate items that were found and sourced, but had an error.

For interfacing through your own tcl scripts, you can see the entire list of scripts via the global variable "$dougscripts" and see the messages for an individual scripts with the command "doug.script_message_log <script_alias>" where <script_alias> is the alias specified in the config file. This will also match the name in the first column of "$dougscripts".

« 00236 | Issues | 00238 »

Associated Commits

| commit | bb53771ceb8444e84bc31ec12bd61a61090991ed [link] | || | Author: | Frank Graffagnino | | Date: | Mon Oct 18 15:10:08 2010 -0500 | | Message: | [@Issue 00237: Added "Scripts" to help menu for direct access @] |

Affected Files:

eng_graph.pkg | Bin 607980 -> 608065 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)

| commit | 8a07af58bdb394e18308e82232a1c0792d74fbf3 [link] | || | Author: | Brad Bell | | Date: | Mon Oct 18 08:36:37 2010 -0500 | | Message: | [@Issue 00237: added yellow color coding to indicate a script that was unable to be sourced. Also modified doug.script_message_log command to take a single argument ie: doug.script_message_log <script_tag_name> which will return the trace on the script @] |

Affected Files:

bin_Linux_FC3/doug | Bin 484710 -> 484874 bytes
 bin_Win32/doug.exe | Bin 705024 -> 705024 bytes
 2 files changed, 0 insertions(+), 0 deletions(-)

| commit | be5f8eafe009735e4f2c2f02b1c836d9ce11f894 [link] | || | Author: | Brad Bell | | Date: | Wed Oct 13 03:59:34 2010 -0500 | | Message: | [@Issue 00237 : Added script error logging that is accessable from the about dialog like plugin logging @] |

Affected Files:

bin_Linux_FC3/doug        | Bin 460071 -> 483522 bytes
 bin_Win32/doug.exe        | Bin 385536 -> 703488 bytes
 bin_Win32/dsp_manager.exe | Bin 23552 -> 23552 bytes
 eng_graph.pkg             | Bin 607407 -> 607848 bytes
 4 files changed, 0 insertions(+), 0 deletions(-)

Clone this wiki locally