1 | initial version |
Coloring rules use the syntax of display filters which don't currently support checking a preference value. That would make a pretty good Enhancement Request on the Wireshark Gitlab issues.
Until/if/when this is added, could you add another field to your protocol dissection and copy the preference value to it and use that in the coloring rule?
The field could be hidden or maybe should be displayed in the tree and marked with treeitem:set_generated([bool])
.
2 | No.2 Revision |
Coloring rules use the syntax of display filters which don't currently support checking a preference value. That would make a pretty good Enhancement Request on the Wireshark Gitlab issues.
Until/if/when this is added, could you add another field to your protocol dissection and protocol, copy the preference value to it and use that in the coloring rule?
The field could be hidden or maybe should be displayed in the tree and marked with treeitem:set_generated([bool])
.