I'm still running on High Sierra (10.13.6) so do not have any option to enable Dark mode.
The version of Qt deployed on the macOS buildbot changed recently. When I previously tested with the development buildbot version 3.1.0rc0-1125-g263969168747 it reported "Compiled (64-bit) with Qt 5.12.1". The later versions where I saw transparent context menu issue reported "Compiled (64-bit) with Qt 5.12.4". I forced the development buildbot to rebuild the Wireshark 3.1.0rc0-1125-g263969168747 which now reports Qt 5.12.4 and now see the transparent context menu issue. This transparent context menu issue can be triggered in the file list on the Wireshark UI Welcom page. Looks like might be something specific to Qt 5.12.4. Best regards, Jim Y. On Sat, Jun 29, 2019 at 8:24 AM Roland Knall <rkn...@gmail.com> wrote: > Hi > > I cannot confirm those glitches on macOS. Especially the second one seems > very strange to me. At this point I think it would be best if you add a bug > report. If you are running the most recent macOS (Mojave), you could also > create a video very easily (cmd+shift+5 for the builtin screen recorder) > and attach that to the bug. > > Please CC me on the bug, as I am currently messing around with the context > menus, and it might be caused by that. But I would more prominently > suggest, that the used Qt version is buggy. Nethertheless, we have to > investigate. > > cheers > Roland > > Am Sa., 29. Juni 2019 um 07:47 Uhr schrieb Jaap Keuter < > jaap.keu...@xs4all.nl>: > >> Hi Jim, >> >> Any dark mode stuff going on? >> >> Thanks, >> Jaap >> >> On 28 Jun 2019, at 18:11, Jim Young <jim.young...@gmail.com> wrote: >> >> Hello, >> >> I almost exclusively run development versions of Wireshark when doing my >> day to day troubleshooting tasks and I typically (but not always) do the >> analysis on a macOS system. >> >> >> >> ___________________________________________________________________________ >> 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
___________________________________________________________________________ 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
