https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13540

Christopher Maynard <christopher.mayn...@igt.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Apply as Column and Column  |Apply as Column should
                   |Drag & Drop misbehave if    |always add the new column
                   |there's a column to the     |to the right of the Info
                   |right of the Info column.   |column, if it exists or to
                   |                            |end if it doesn't.
           Severity|Normal                      |Enhancement

--- Comment #12 from Christopher Maynard <christopher.mayn...@igt.com> ---
(In reply to Stig Bjørlykke from comment #11)
> I would like to keep the "Apply as column" as it is even if adding the new
> flow (which I think sounds nice).

No arguments from me.  Keep it as is, with the exception of *where* the column
gets added.

> I made this behavior.  I think the reasoning was that when not having the
> Info column last (who does this?) it would not be intuitive to put it before
> the Info column.  So I put it last.  I think this was some time before
> version 1.0.
> 
> When using a default-like setup with Info column last the added column must
> be put before this to avoid that it's hidden to the right of the screen. 
> And at that time (using GTK) it was easily possible to move the column to
> the wanted position :)

I think it makes the most sense for all new columns to be added to the left of
the Info column whether the Info column is the last column on the right or not,
or added as the last column on the right if there is no Info column.  I think
this is the most consistent behavior and would also accommodate us crazy folks
who happen to have a column to the right of the Info column, but don't
necessarily want *all* new columns added to the right of the Info column, just
1 very specific one.

-- 
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via:    Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
             mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

Reply via email to