OK. This is really a huge step forward but I have a few complaints.
First, could we put these protocols in alphabetical order? MGCP and
gryphon are both at the very end, this is really going to confuse
people.
Second, the refresh when I scroll through the list seems to be very very
slow ( I basically have to stop scrolling and wait for a redraw,
processor also shows as being walled for the duration of attempts to drag
the scroll bar down).
Third, I've found that the full name of the protocol is
not always very useful. For example, how confused is a user looking
for DHCP going to be? I know this problem is bigger than the new
filter construction dialog, but I decided to take this opportunity to
complain anyway.
Ed
On Mon, 1 Jan 2001, Guy Harris wrote:
> On Wed, Dec 06, 2000 at 03:39:51PM -0600, Jeff Foster wrote:
> > I have written some code to add a filter string lookup tree into the filter
> > dialog boxes.
>
> I've constructed a more elaborate such dialog box, based on that; it
> actually lets you construct an expression that tests a field, not just
> select a field from a list. The dialog box is modeled after that of
> Microsoft Network Monitor.
>
> If the field has a value_string table associated with it, you can select
> the value from a list of the names in that table, rather than having to
> memorize the values or look them up in some protocol spec.
>
> > The code adds another button on the filter dialog box, "Tree...".
>
> The button is now called "Add Expression...".
>
> > The code does have some problems with multiple filter dialog boxes.
>
> The filter dialog box code has problems with multiple filter dialog
> boxes, which should be cleaned up; the "Add Expression" dialog box is
> itself, however, reentrant (it uses no global variables).
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>