| Summary: | Minor Text Display Issue | ||
|---|---|---|---|
| Product: | [Applications] kstars | Reporter: | Fred <ruegs> |
| Component: | general | Assignee: | Rob <rlancaste> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | ||
| Priority: | NOR | ||
| Version: | 3.6.3 | ||
| Target Milestone: | --- | ||
| Platform: | macOS (DMG) | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Image of Mount Control window | ||
|
Description
Fred
2023-02-05 20:30:15 UTC
This is very strange indeed. I haven't seen this happen since I started helping with KStars back in 2016. I did a whole bunch of stuff with the QML code and I never saw it do that. I can confirm that after testing this evening that it does this on my system as well and it affects both "What's Interesting Today" and the "Mount Control Box". So whatever this is, it appears to be related to QML rendering in general. I played around a little bit this evening and I was able to make the issue go away for an element if I set renderType: Text.QtRendering on that element. But that is supposed to be the default, and I tried a couple of other ways that should set that globally in the software, but that was the only thing that worked. So my guess is this is some sort of QT Bug for QML rendering, especially because nothing has changed in the KStars QML files for a couple of years. Ok I think I have figured out the issue and I have a workaround. It looks like there is some sort of QT bug with renderType being set incorrectly for various components as I mentioned and setting the renderType for each item does seem to fix it. Unfortunately I wasn't able to set it globally, which is probably the reason for the bug in the first place because the default should already be Text.QtRendering. Here is my attempt to fix it https://invent.kde.org/education/kstars/-/merge_requests/840/diffs and if there are not issues with my change, I can push it through. It is not elegant, but it works around the problem and seems to fix it for us. (In reply to Rob from comment #2) > Ok I think I have figured out the issue and I have a workaround. It looks > like there is some sort of QT bug with renderType being set incorrectly for > various components as I mentioned and setting the renderType for each item > does seem to fix it. Unfortunately I wasn't able to set it globally, which > is probably the reason for the bug in the first place because the default > should already be Text.QtRendering. Here is my attempt to fix it > https://invent.kde.org/education/kstars/-/merge_requests/840/diffs and if > there are not issues with my change, I can push it through. It is not > elegant, but it works around the problem and seems to fix it for us. Thank you for looking into this Rob - I'll look forward to trying it out! Ok this build should include fixes for both the QML rendering bug displayed here and the port selector not showing up bug. www.indilib.org/jdownloads/kstars/beta/kstars-3.6.3.dmg Please try it out and let me know if it fixes it. (In reply to Rob from comment #4) > Ok this build should include fixes for both the QML rendering bug displayed > here and the port selector not showing up bug. > > www.indilib.org/jdownloads/kstars/beta/kstars-3.6.3.dmg > > Please try it out and let me know if it fixes it. Hi Rob - responded over on the INDI forum as well but things look good and it appears that all the text and information is now displaying correctly! Thanks for your work on this! Ok I think this is all fixed in the repo |