I, like many developers, use Log() a lot. But the log panel (on Log tab) gets cluttered up because I am tracking a lot of different information. I will use the Log to track variable values and also program flow. But I can't easily discern between them if they are all written to the same log panel. I need some way of filtering the types of info that is being written to the log.
There are 2 solutions to this:
1) I'd like to have a second log function called Log2() that will write to a second Log window that is on a Logs2 tab. So instead of seeing just one Logs tab in the IDE, there will be Logs and Logs2.
2) Another (better) solution is to have a Log2() function with another parameter, a filter string.
Syntax: Log2(FilterStr as String, LogMsg as String)
It can be called using :
Log2("MyFilter", "Normal Log String")
The IDE's existing Logs tab will have a Filter pulldown control, preferably a Check Listbox so more than 1 filter can be selected at a time. Or you could have a 2nd tab/panel that displays a checkable list.
When the user selects this Filter control, it shows a unique list of possible FilterStrs that were used so far in the program by Log2()'s first parameter :
"<All Rows>", "MyFilter", "MyBugTrace", "PgmFlow" ...
So each one of these possible filters corresponds to the 1st parameter values that were used by Log2(). Selecting one (or more) of these FilterStr's will display only the log message for that FilterStr.
This will allow the developer to easily filter the logs so he can view only what is important to him at the time. By selecting the appropriate log filter(s), he will be able to see the forest and the trees without re-running the app with different log stmts.
I think this will greatly improve the usefulness of the Logs tab and will make debugging and finding bugs much easier.
TIA
There are 2 solutions to this:
1) I'd like to have a second log function called Log2() that will write to a second Log window that is on a Logs2 tab. So instead of seeing just one Logs tab in the IDE, there will be Logs and Logs2.
2) Another (better) solution is to have a Log2() function with another parameter, a filter string.
Syntax: Log2(FilterStr as String, LogMsg as String)
It can be called using :
Log2("MyFilter", "Normal Log String")
The IDE's existing Logs tab will have a Filter pulldown control, preferably a Check Listbox so more than 1 filter can be selected at a time. Or you could have a 2nd tab/panel that displays a checkable list.
When the user selects this Filter control, it shows a unique list of possible FilterStrs that were used so far in the program by Log2()'s first parameter :
"<All Rows>", "MyFilter", "MyBugTrace", "PgmFlow" ...
So each one of these possible filters corresponds to the 1st parameter values that were used by Log2(). Selecting one (or more) of these FilterStr's will display only the log message for that FilterStr.
This will allow the developer to easily filter the logs so he can view only what is important to him at the time. By selecting the appropriate log filter(s), he will be able to see the forest and the trees without re-running the app with different log stmts.
I think this will greatly improve the usefulness of the Logs tab and will make debugging and finding bugs much easier.
TIA
