|
|
[fwputil_library]Description
fwpUtil_tagTraceThis tool emulates the "stack trace" features of a compiled language debugger. It can be used to build a sequence of exactly what code points have been processed, and what specific variable states are at those points. So, it functions as two roles. This is much cleaner to work with than creating manual test vars to capture var states. fwpUtil_timerThis tool provides an easy and clean method to have multiple "stop watches" inside your code. No doubt you've tried something like this: var:'startSomething' = _date_msec; I've used those too. You start with a couple, then add a few more, then they just get downright ugly after you stack up a bunch of them. Way too many variables to keep track of. This custom type provides a cleaner approach by storing all data inside the ctype under a single variable name, and some tags to extract the ones you want. fwpUtil_showVarsThis tool provides an easy to read display of variables. It can output all variables in Lasso's vars and globals maps, or output only vars you specify. It can also be configured to exclude certain variables. This would typically be used at the very end of a page for detailed debug output. Each variable is displayed with its name, value, and data type. The display of complex variables such as arrays, maps, and others that may have nested data structures are recursively navigated to format each level until a simple data type is reached (null, boolean, string, integer, decimal, date, or duration). Parametersnone Sample Usage
Source CodeClick the "Download" button below to retrieve a copy of this tag, including the complete documentation and sample usage shown on this page. Place the downloaded ".inc" file in your LassoStartup folder, restart Lasso, and you can begin using this tag immediately.pbDebugUtils_100.zip (350.05 kb)
Related TagsCommentsnone |
|||||||||||||||||