[David Hampton <dhampton@xxxxxxx>]

> 1) I like the concept, however I don't like adding another data structure
> to hold the dissector information.  You could (should?) use the conversation
> data structure to implement this functionality.  There is an issue with
> retaining the settings during a 'redissect'.  I would rather see a data
> structure for the user information and an initialize routine that creates
> the conversations when the 'redissect' happens.

Where do I look to get an understanding of the conversation data
structure?

> 4) Change the 'protocol to decode as' to a scrolled list. I fear that this
> list may grow if your idea is accepted.

I'm unclear on what a scrolled list is.  Is it simply a list within a
scrolled window container?

David