Conversation
Option 1 - Exclude via Preferences -additional options to skip certain types of scripts (stack, card, group, button, field, widget, other) Option 2 - Exclude via comment -adding a commented line with the word "exclude" in it will cause that script to be skipped e.g. "-- exclude from script tracker"
|
What about using a custom property on the parent object? Currently for each group I check to see if it is a data grid and skip if so. I could extend that logic to look for a property on the object that would exclude it (and if a group, would exclude all children). Since this involves a binary change, I'll probably manually merge it. I'll pull this down this weekend and do the compare. Thanks for the input! |
|
A custom property would be a great idea... I feel silly for not thinking of it... One other exclusion idea I was thinking of would be an option to set a minimum threshold for lines in a script. For example, a threshold of 5 lines would skip over buttons that may only contain a mouseUp handler that calls a command on a script higher up the message path. |
|
See cd8c373 for how I addressed this idea/request. I moved the exclusions from being global to being stack specific. |
2 participants
Option 1 - Exclude via Preferences
-additional options to skip certain types of scripts
(stack, card, group, button, field, widget, other)
Option 2 - Exclude via comment
-adding a commented line with the word "exclude" in it will cause that script to be skipped
e.g. "-- exclude from script tracker"