Cura: GUI glitch when scrolling [Version 4.7]

Created on 25 Aug 2020  路  16Comments  路  Source: Ultimaker/Cura

Application version
Version 4.7

Platform
Windows 10 64-bit

Printer
Ender 3

Reproduction steps

  1. Open list of print settings.
  2. Scroll.

Screenshot(s)
image

Actual results
While scrolling, numbers will disappear and reappear. If you release the mouse button while the numbers are gone, they will remain gone until either (1) you continue scrolling or (2) the mouse cursor enters a box where the numbers should be. The values are retained, this appears to be a graphical glitch only.

Expected results
Numbers should not disappear; they should always be visible. This was the behavior in Version 4.6. I uninstalled Version 4.6, retained my user files and settings, and installed Version 4.7 and saw this behavior start.

Project file
N/A, not related to a project.

Log file
N/A, no log file will be created in duplicating this issue.

Additional information
No additional, relevant information is available.

Uranium Bug

Most helpful comment

I held off installing 4.7.1 and was using 4.3 for a long time. But I finally installed it this week. Sure enough, the flashing text when scrolling down (but not scrolling up). It's not a deal-breaking problem, just annoying. I just thought I'd confirm.

All 16 comments

I also have this issue since 4.7 beta.

I also have this issue since 4.7 beta.

Then why didn't you report it? It's now very unlikely to be fixed for 4.7.

I think it's also in the current master branch...

I think it's also in the current master branch...

Stands to reason, since 4.7 isn't that much different from master at the moment. But it must have something to do with drivers / setup, since not everyone has the issue.

I could reproduce this issue ~but only in the (AppImage) build, not when running from source~. Here is a recording of how it looks in animation:

http://dulek.net/work/setting_list_glitchy.webm

Pretty much as described. But four observations:

  • Like 90% of the time it's okay. In this video I purposely stopped scrolling while it was gone.
  • It never happens when scrolling up, for some reason.
  • It doesn't affect some settings. Which settings it affects seems to depend on their position on the screen.
  • It doesn't happen when using the scroll wheel. Only when dragging the scrollbar. That's probably why I hadn't seen this before, since I always use the wheel.

Edit: Actually no, it's also when running from source. That reduces the chance that it's a bug in Qt.

It does this on Mac OS X 10.10 Yosemite, too.
Mostly, but not always, scrolling towards the bottom of Settings (Experimental).
More likely to occur when scrolling with mouse pointer over the scrollbar, or dragging the scrollbar.

Same issue here. Windows 10, Cura 4.7 and still present on 4.71. Scrolling down the Print Settings causes the values to disappear or flicker. They reappear when scrolling stops.

Doesn't seem to happen when scrolling up. Never had the issue before in Cura 4.5, 4.3, 4.1, and earlier versions etc--seems new in 4.7 and 4.71.

I did a bit of investigation into this and it makes absolutely _no_ sense that it's doing it. If I change the font of the text box to anything but what it is now, the bug disappears. It's probably not what you want to hear from a developer, but I honestly have no idea what the hell caused this.

Probably running into the same problem as this guy: https://forum.qt.io/topic/54693/listview-text-disappears-when-scrolling-delegate-is-text-over-image/5
But there is no solution there either.

I did a bit of investigation into this and it makes absolutely _no_ sense that it's doing it. If I change the font of the text box to anything but what it is now, the bug disappears. It's probably not what you want to hear from a developer, but I honestly have no idea what the hell caused this.

This bug doesn't change if the "weight" settings in theme.json are altered - I've been using an edited version since the "Extra Bold" look started.
I've gone back to 4.6.1, as the Layer View in 4.7 is patchy (literally). I'm using Yosemite (OS X 10.10.5), which may the reason for layers not displaying correctly, as the Cura version 4.7.1 seems to be for OS X 10.11 and higher.

Wouldn't it be possible to compare the change commits between 4.6.2 and 4.7 beta and adding them some at time to see which commit caused this?

I'm using Yosemite (OS X 10.10.5), which may the reason for layers not displaying correctly, as the Cura version 4.7.1 seems to be for OS X 10.11 and higher.

Since Cura 3.4 we're using Qt 5.10, which supports down to MacOS 10.11, not Yosemite. Our build server is also on 10.11 so CuraEngine has the same requirement. I don't know what could be going wrong in unsupported old versions but since Qt is involved it would make sense that the rendering is buggy. This hasn't changed since Cura 3.4.0 though.

Wouldn't it be possible to compare the change commits between 4.6.2 and 4.7 beta and adding them some at time to see which commit caused this?

Yeah that would make sense. However the commits that could influence this are spread out between the Cura and the Uranium repositories which makes a normal git bisect a bit more involved. This is how I would approach tracing down bugs like this though.
There are also 1134 commits between 4.6 and 4.7 on the Cura repository alone, so it's no small task in any case.

So you can't only select the minor versions like 4.6.2 vs 4.7 beta rather than 4.6 to 4.7? Pretty bad. :\

I'm using Yosemite (OS X 10.10.5), which may the reason for layers not displaying correctly, as the Cura version 4.7.1 seems to be for OS X 10.11 and higher.

Since Cura 3.4 we're using Qt 5.10, which supports down to MacOS 10.11, not Yosemite. Our build server is also on 10.11 so CuraEngine has the same requirement. I don't know what could be going wrong in unsupported old versions but since Qt is involved it would make sense that the rendering is buggy. This hasn't changed since Cura 3.4.0 though.

That probably explains it, though layer view was OK until 4.7. Oddly, most of each layer's missing render appears if "Helpers" is checked, even though that seems to mean show Brim or Skirt.

So you can't only select the minor versions like 4.6.2 vs 4.7 beta rather than 4.6 to 4.7? Pretty bad. :\

Oh you can. There are 1030 commits from 4.6.2 to the beta.

I held off installing 4.7.1 and was using 4.3 for a long time. But I finally installed it this week. Sure enough, the flashing text when scrolling down (but not scrolling up). It's not a deal-breaking problem, just annoying. I just thought I'd confirm.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rudowinger picture rudowinger  路  3Comments

JRRN picture JRRN  路  3Comments

ferociousdiablo picture ferociousdiablo  路  3Comments

StanislavJochman picture StanislavJochman  路  3Comments

mnswamp1 picture mnswamp1  路  3Comments