-
Notifications
You must be signed in to change notification settings - Fork 411
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Change the way I store hidden columns
Prior to this change, I copied Wireshark and kept a hidden-columns key in the toml file, with the column expressed using its tshark spec e.g. "%Yut", "%Cus:tcp.port:0:R", ... But this doesn't distinguish between two columns that have the same spec - should the user want to configure columns that way. Wireshark has this problem too; if you have two identical columns, hide one, then quit and restart, both columns with the same spec are hidden. I suppose this means Wireshark added the gui.columns.hidden field after gui.columns.format was established. Now, instead of storing a termshark column spec as the tshark spec and its display name, I use a trip - tshark spec, display name, and visibility. Therefore, if the user has 5 columns configured, the column-format string list in the toml file will be 15 elements long.
- Loading branch information
Showing
3 changed files
with
21 additions
and
53 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters