Resolved/Unresolved column (Was: [Wireshark-users] Adding DSCP column in Wireshark 1.4.0rc1)

[Jaap Keuter <jaap.keuter () xs4all nl>]

-------- Original Message --------
Subject: Re: [Wireshark-users] Adding DSCP column in Wireshark 1.4.0rc1
Date: Wed, 23 Jun 2010 15:01:36 -0700
From: Guy Harris <guy () alum mit edu>
Reply-To: Community support list for Wireshark <wireshark-users () wireshark org>
To: Community support list for Wireshark <wireshark-users () wireshark org>


On Jun 23, 2010, at 2:54 PM, Jaap Keuter wrote:

> > That would required the option of having custom columns with unresolved values.
> > An interesting concept in itself.

> ...which might let us have the type of column and resolved vs. unresolved as 
> separate notions, even for non-custom columns.


Indeed for build-in columns too, where this option would be made available when 
the format string matches "%[ur].*".

For custom columns it would be made available when the header field has a 
FIELDCONVERT value != NULL.

It could be added here, as a checkbox item, on the dropdown menu, and enabled 
when applicable

  Sort Ascending
  Sort Descending
  No Sorting
----------------
  Resolved
----------------
  Align left
  Align center
  Align right
----------------
...

And it must be offered as an option in the column preferences dialog, of course.

Now we just have to work it into the data structures and column preference file.

Thanks,
Jaap
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe