Luis, I believe this bug is talking about the filter button on the Windows file dialog that doesn't work, which didn't the last time I checked SVN so it should remain open (or we need to open a new bug for it). The filter button works in the GTK file dialog just fine.
On Thu, Apr 05, 2007 at 07:33:23PM +0000, [EMAIL PROTECTED] wrote: > http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=942 > > > [EMAIL PROTECTED] changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|NEW |RESOLVED > Resolution| |WORKSFORME > Version|0.99.0 |0.99.6 > > > > > ------- Comment #6 from [EMAIL PROTECTED] 2007-04-05 19:33 GMT ------- > If I understand well this is a problem on how the word "filter" is > interpreted. > > Being it in the open file dialog someone will naturally interpret it as file > filter like in "*.cap" > > But being in wireshark the "filter" term is interpreted as a wireshark display > filter. > > I think the solution is to rename the field of the open dialog into "display > filter" > > > IMHO if the issue is about memory we should be using libpcap filters instead > of > wireshark ones. > > > -- > Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > _______________________________________________ > Wireshark-bugs mailing list > Wireshark-bugs@wireshark.org > http://www.wireshark.org/mailman/listinfo/wireshark-bugs _______________________________________________ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
