Infill Field

[jakersmith]

Cura Version

5.8.1

Operating System

Windows 11

Printer

Creality Ender-3 / Ender-3 v2

Reproduction steps

1. Opened Print Settings dropdown menu
2. Selected the "Infill Density" field (Infill pattern: Cubic Subdivision; only "Infill Density" and "Infill Pattern" fields are showing under the "Infill" category)
3. Erased everything in the field by pressing the backspace button OR highlighting all characters and pressing Enter

• This is where it first failed

4. Selected the "Infill Density" field again
5. Typed a single number character

• This is where if failed again

6. Selected the "Infill Density" field a third time
7. I was able to correctly type my desired percentage

Actual results

After erasing everything from the "Infill Density" field it would automatically deselect the field leaving it blank. When I selected the field a second time I as able to type a single character (number) before it automatically deselected the field again, leave that single character. After selecting the field for a third time I was able to correctly fill the field with my desired percentage.

Expected results

After erasing the "Infill Density" field I SHOULD have been able to immediately type out my desired infill percentage.

I have attached several screenshots, numbered, to show the various steps of this bugs as well as a video of the issue occurring.

Add your .zip and screenshots here ⬇️

Cura_InfillDensity.mp4

[HellAholic]

Hey @jakersmith ,
This is one of the things that's high on our list of things to tackle in terms of UX improvements. It is a tricky subject since the behavior (instant update) is linked to setting dependency, so the field immediately gets updated as another setting value requires it for calculations.

We have a ticket to improve this behavior but we need to figure out a few things and make sure it doesn't affect the calculated setting values.

[jakersmith]

Fantastic! Glad to hear it’s something you’re working on and I COMPLETELY understand having value dependencies and trying to not break more things by adjusting how this field operates. I just wasn’t sure if you guys were aware of this, and wanted to make sure it got documented. Thank you for the reply and for the great work you guys are doing!  ---- On Sun, 10 Nov 2024 10:35:17 -0800 ***@***.******@***.***> wrote ---- Hey @jakersmith , This is one of the things that's high on our list of things to tackle in terms of UX improvements. It is a tricky subject since the behavior (instant update) is linked to setting dependency, so the field immediately gets updated as another setting value requires it for calculations. We have a ticket to improve this behavior but we need to figure out a few things and make sure it doesn't affect the calculated setting values. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>