Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 23560: /trunk/ /trunk/doc/: wireshar
From: Sake Blok <[email protected]>
Date: Fri, 30 Nov 2007 21:04:24 +0100
On Fri, Nov 30, 2007 at 02:38:07AM +0100, Ulf Lamping wrote:
> Sake Blok schrieb:
> >> There are some other usability things that really needs to be solved:
> >>
> >> - if no capture file is loaded, both "View/Colorize Conversation" and 
> >> "View/Reset Coloring" are active and can be clicked - but nothing 
> >> happens. A usability "no go".
> >>     
> > Check, I will add sensitivity to these items.
> "View/Reset Coloring" is still active if no capture file is loaded - is 
> this intentional?

Yes it is, it makes sense to me to be able to clear previously used
temporary coloring after closing a file and before loading a new one.

Of course I could make "File - Close" clear these coloring rules, but
then again, maybe someone likes to keep them for the next file in the
analysis proces.

An enhancement would be to make it grey out when there are actually 
no temporary coloring rules active.

> Now I know what I don't like about the "Reset Coloring". It's too 
> unspecific what it will to - will it reset the "Coloring Rules" as well? 
> What about "Reset Conversation Coloring"?

It's not only conversation coloring, it's also "Coloring with filter".
Maybe "Reset coloring filters 1-10" or "Reset temporary coloring"?

> > PS Does "<ctrl>-space" work Windows for you? It doesn't on my laptop. In
> >    wanting to solve that, I built my first Windows development environment
> >    yesterday. To my surprise the "handrolled" Wireshark on my windows
> >    development box does indeed respond to <ctrl>-space. I'm wondering
> >    whether there is something else, just on my laptop, interfering.
> "<ctrl>-space" is reserved for showing the windows own window dialog - 
> the same that you'll get when you'll click at the top left of each 
> window. You might need to find a better hotkey ;-)

Isn't "<alt>-space" reserved for showing the windows own dialog?
"<ctrl>-space" seems to be handled differently by every application.

I managed to find what was blocking "<ctrl>-space", it was "Messenger
Plus!". It now works fine for me on Windows too.