Type-Sizes are shortened and therefore unreadable

[knoxfighter]

Version and Platform (required):

• Binary Ninja Version: 4.3.6821-dev Personal (11d1af1d)
• OS: Windows 10
• OS Version: 10.0.19045 Build 19045
• CPU Architecture: x64

Bug Description:
The size value in The Types Widget are shortened, making them unreadable.
Changing the width of the Size column doesn't change that.
e.g. 0x118 -> 0x1...

Expected Behavior:
Until a few days ago, the type sizes are properly shown and only shortened if the Size column is not wide enough, please change it back to that behaviour.

[xusheng6]

Thx for the report. However, I do not think we have changed it recently on purpose. And this might be caused by us updating Qt

[psifertex]

We will still investigate a solution, that's definitely not workable. Does making the column wider at least still work to make them readable?

[knoxfighter]

No, making the column wider does not change anything. The only way to see the size of the struct is by selecting it and press L to open the resize popup.

[psifertex]

Sorry for the delay on this. I'm still unable to reproduce the issue. Can you give some more details as to what section in the type browser you're in? As well as an additional screenshot showing what happens when the last column is expanded in size?

[knoxfighter]

It happens in the type widget in the sidebar. Independent of the opened project.
I've added a screenshot of the whole sidebar with a the Size column made really wide.

[psifertex]

Which section of the types are you in though? User types? System Types? Library? Type Archive? It shouldn't matter but since I can't recreate it I'm trying to minimize differences. (Or are they all like that?)

[psifertex]

Also, does it do it on all files? Or just some? You can also try starting BN with a different QSettings directory which is where many of the saved UI features are saved in case that helps using the BN_QSETTINGS_POSTFIX env var.

[knoxfighter]

Which section of the types are you in though? User types? System Types? Library? Type Archive? It shouldn't matter but since I can't recreate it I'm trying to minimize differences. (Or are they all like that?)

They are all like that.

Also, does it do it on all files? Or just some? You can also try starting BN with a different QSettings directory which is where many of the saved UI features are saved in case that helps using the BN_QSETTINGS_POSTFIX env var.

Yes, it is like that for all files. and setting that env variable, does not fix the issue (all adjustments to the ui are reset obviously).