Bug 403186 - Decimal offset coding gets cut off
Summary: Decimal offset coding gets cut off
Status: RESOLVED UPSTREAM
Alias: None
Product: okteta
Classification: Applications
Component: general (show other bugs)
Version: 0.25.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Friedrich W. H. Kossebau
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-13 18:09 UTC by Luca Weiss
Modified: 2019-01-14 01:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot showing the problem (3.85 KB, image/png)
2019-01-13 18:09 UTC, Luca Weiss
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Luca Weiss 2019-01-13 18:09:40 UTC
Created attachment 117444 [details]
Screenshot showing the problem

SUMMARY
When View => Offset Coding => Decimal is selected, the offset in the lower left corner gets cut off by the "Selection:" text

STEPS TO REPRODUCE
1. Open a file
2. Change "Offset Coding" to "Decimal" and view the "Offset:" text in the lower left corner

OBSERVED RESULT
The text is cut off

EXPECTED RESULT
The text shouldn't be cut off

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.53.0
Qt Version: 5.12.0
Comment 1 Friedrich W. H. Kossebau 2019-01-13 18:30:37 UTC
Thanks for the report. Offset display when switching the encoding Looks okay on my system (incl. when doing selections. So for now I guess this is an issue with the calculation based on the sizing info provided by the actual font used (or the logic in Okteta to use that info).

To try to reproduce myself, please tell which font you are using for the UI. E.g. with Plasma that can be seen in SystemSettings -> Fonts -> Tab Fonts -> General.
Comment 2 Luca Weiss 2019-01-13 18:38:21 UTC
That shows "Noto Sans 10"
Comment 3 Friedrich W. H. Kossebau 2019-01-13 21:33:38 UTC
Thanks. And indeed can I reproduce the reported cut-off with that font "Noto Sans 10".

So that seems to need fixing on side of Okteta's code, will see to get to that soon.
Comment 4 Friedrich W. H. Kossebau 2019-01-14 01:53:43 UTC
Unless I missed something in the Qt API, this might be a bug in Qt itself, at least by my initial experiments. Reported as https://bugreports.qt.io/browse/QTBUG-73002

So for now closing as upstream bug. Not sure I should invest into a work-around, for now curious on the feedback on that upstream Qt bug report.