ShapeDiver Team,
I’ve just noticed a strange behavior when working with Slider Number(s) in Shapediver. All my Number Slider input parameters were pre-configured to three decimal places (i.e. 0.123) and the range was set from 0.000 to 1.000. Such a range was designed to move a point along an internalised curve precisely.
When testing my definition, I accidentally set one of the Slider Number input parameters by typing “1” . It seems that the platform overrode the pre-formatted decimal places and the range was set from 0 to 1 (with no intermediate steps) and I did not find any way to change/refresh it? The only thing that works is to type a number with three decimal places manually. Another feasible way is to refresh the entire definition. But the same issue happens again.
I’ve uploaded a simple example which is here. Please have a look.
Generally, it is not a critical issue (known only for a developer) but I think it would be a good practice to retain the designed original formatting on the Slider Number input parameters and to have full protection from “accidental” inputs of the end-users. I hope you will find this feedback useful.
Oh, nice! Thanks for sharing @Joseph_Oster. I am not a frequent visitor here, but I did try to do a quick search here for a similar topic before posting my issue
The issue has been fixed in viewer version 2.18.0, the latest version currently live on app.shapediver.com
You might need to reload without browser cache, or empty your browser cache. Please give it a try.
Now I’m seeing a trivial cosmetic anomaly when I move INTEGER sliders… Three decimal places are showing while the slider is being dragged, though they go away and show the integer value when you stop dragging.
I haven’t tried more than three decimal places yet, will that work or is three the limit? One of my test models had a slider that needed four decimal places, so I adapted it to the two decimal place limit by labeling it “(1/100THS)” and dividing the value by 100. Instead of “0.0625” the slider says “6.25” 1/100THS, which is an awkward workaround but not a show stopper.
I’m very impressed with ShapeDiver. Keep up the good work.
The middle slider is set to four decimal places but shows only three, which isn’t so bad but the first slider (5 decimal places) and last slider (6 decimal places) round to integers again.
The ‘Edit Model’ page still shows only two decimal places.
Be careful please. Quick fixes are great but better to avoid them in the first place, especially on something this obvious. Thank you.
For comparison, this is the simple box test I posted two days ago, which now works fine at three decimal places (but not on the ‘Edit Model’ page which shows only two):
But when the browser is sized less than ~1024, the sliders move from the right side to the bottom, stacked in two columns. As you can see, all sliders display the correct number of decimal places in this arrangement but the third slider (‘Z’, which you have to scroll to see) is full width:
Agreed that the number boxes could be made a little wider in edit mode, such that up to 3 decimal places are shown. However for now we specifically chose to not make those boxes wider and show more than 3 decimal places, although the sliders support the number of decimal places to be higher.
