Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 1664] New: display filter character set not optimal, too l

Date: Mon, 25 Jun 2007 11:36:54 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1664

           Summary: display filter character set not optimal,  too large
           Product: Wireshark
           Version: 0.99.7
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: matthias.kuzmits@xxxxxxx


Build Information:
wireshark 0.99.7-SVN-22183 (SVN Rev 22183)

Copyright 1998-2007 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.10.12, with GLib 2.12.12, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with Net-SNMP 5.4, with ADNS, with Lua 5.1,
with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio
PortAudio V19-devel, with AirPcap.

Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0
(packet.dll version 4.0.0.755), based on libpcap version 0.9.5, without
AirPcap.


Built using Microsoft Visual C++ 6.0 build 8804


--
Since some time I have the problem that the character set of the display filter
is too big, so that it's not really usable. It consumes too much space of the
input window. The dropdown list is using the correct character set.

At the beginning I thought that this is caused by my private build environment
but in the meantime I have more information’s.

With wireshark 0.99.5 it was OK. 

I see the same bad behavior with the newer builds from the build bot like
wireshark-setup-0.99.7-SVN-22183.
If the newer version is installed fresh then it works until the next start of
wireshark. I found out that this is related to the presence of the "recent"
file in the "Personal configuration" directory. If there is no "recent" file
the codec is the same in the dropdown list and the input line. When a "recent"
file is present then we have two different character sets used for dropdown
(correct) and filter input line (to large).

I tried to use the Gtk+ 2.10.13 instead of the 2.10.12 as it's used by
wireshark but this didn't helped.
Somehow a different character set is selected, depending on presence of
"recent" file or not.


-- 
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.