If I now start with 0 subdivisions in the UI, I start of the modal with two edges [also seen in the status bar], dont think this is intentional?
(mousewheel works fine though... so I could decrease to one [from 2] and up again)

This revision now requires changes to proceed.Dec 21 2021, 12:57 PM

Make more coherent the values of subdivisions and avoid 0

Now the subdivision minimum value is 1 instead of 0 because the primitives use this value as number of segments.

Not sure if the name "subdivision" is the best in the UI, because maybe would be relative to number of segments.

Harbormaster completed remote builds in B19561: Diff 46273.Dec 21 2021, 4:53 PM

More tweaks to values

Harbormaster completed remote builds in B19572: Diff 46285.Dec 21 2021, 8:04 PM

Missing in previous commit

Harbormaster completed remote builds in B19573: Diff 46286.Dec 21 2021, 8:05 PM

With the current version, I still get the discrepancy of starting with 0 subdivisions in the UI and getting 1 subdivisions reported in the statusbar.
I know the "end-result" is now in fact 0 subdivisions (which is good), going up and down with the mousewheel also works, maybe we could avoid the confusion by tweaking the statusbar to be the same as the Subdivisions in the topbar?
I know edges and subdivisions are not the same, but since "edges" are only internal, maybe we should stick to only subdivisions in the "user-visble" UI?

Also, please update the Diff title to be something more descriptive.
Thx, we are getting there

The value in the status bar looks the number of edges... this was like that since first implementation... I will change it to reflect subdivision value.

Antonio Vazquez (antoniov) retitled this revision from Fix T93999 to GPencil Subdivision value is not consistent with Box primitive and does not work with wheelmouse as expected.Dec 22 2021, 1:17 PM