Comment # 4
on bug 11369
from Jeff Morriss
(In reply to arthur.yurov from comment #3)
> I've posted a side by side view of the Legacy UI and the new UI of what it
> looks like when I filter by our protocol name. I also demonstrate in this
> screenshot that the details of the packet are still properly displayed, the
> only issues exist in the packet info of the header at the top.
OK so this isn't (just) about "show packet in new window."
Does it display properly when there's no display filter?
If so, do you have some if(tree) checks in the code? They're largely
unnecessary now.
Do you have some checks on whether your dissector writes to COL_PROTOCOL or
COL_INFO? The code that updates those columns is what appears to not be
running in this case.
> The plugin was developed using 1.99.3 branch, and I'm running it in 1.99.8
> version of Wireshark (Problem exists since 1.99.3). Do we think creating the
> plugin in the latest 1.99.8 branch could make a difference with this UI
> issue?
"Developed" or "compiled?" If you mean "compiled" then, yes, it could quite
possibly have an effect. Dissectors normally need to be compiled against the
major.minor version used. But in the master (development) branch the API/ABI
changes regularly (and without notice) so it's really a good idea to keep it
freshly compiled.
You are receiving this mail because:
- You are watching all bug changes.