My problem is not so much, that it would be much work (partly got it working already), but more, there is a reason for that behavior change in Qt. I am worried that if we change it back, there will be other hidden issues waiting for us.
Am Di., 3. Sept. 2019 um 20:16 Uhr schrieb Pascal Quantin < pas...@wireshark.org>: > Hi Roland, > > Le mar. 3 sept. 2019 à 17:39, Roland Knall <rkn...@gmail.com> a écrit : > >> Hi >> >> Those of you build Wireshark yourself or using a pre-distributed version >> of Wireshark with Qt >= 5.11 might run into this issue: >> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15879 >> >> In short, Qt changed the default behavior for the first column, and it >> therefore cannot be moved anymore, unless we explicitely allow it again. >> Personally I would prefer keeping it that way, because I can see additional >> overhead moving our way if we enable this functionality again. >> >> Reordering the columns (and therefore setting another column as the first >> one) using our column preferences is still possible. It is an inconvenience >> to not being able to do it with drag-and-drop and frankly I am annoyed that >> they change UI behavior mid-LTS phase. >> >> What do you guys think? Would this be a deal breaker for you, if the >> first column can no longer be moved around? >> >> Please let me know >> > > I have no idea how much work it would represent to "fix" that, but given > that it was possible before I guess we should expect a few bug reports over > time of people complaining about this (especially if you can still change > it in the columns preferences). > I find this limitation a bit awkward, even if I can accept it. > > Pascal. > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe