sniken
August 15, 2022, 10:39pm
1
For some reason when dragging a number slider the values go berzerk, i.e. instaed of stopping at 100 (0-100 step 0.1) they go to crazy high values, and the slider is somehow out of sync with the cursor.
I have this in Win11 with Versions .14 and .15., but in 2.13 it works ok.
Is this a known issue or user error somehow ?
1 Like
Hi @sniken
Can you post a screenshot of the behavior you are seeing?
As well as the specific Dynamo Version and (if applicable) host application (Sandbox, Revit,C3D, etc).
sniken
August 16, 2022, 5:37pm
3
when I move the slider the value explodes…
(sandbox 2.15/win11)
@ashish.ganta FYI - I wonder if this is a bug in WPF when running in windows 11.
1 Like
I have the same problem.
sandbox 2.15 / win 10
But only when the step is not an integer.
Otherwise it behave normaly…
@Ypolites ,
i can confirm that! i think it is bug…
KR
Andreas
there is a more indepth discussion of this issue here:
DynamoDS:master
← reddyashish:master
opened 07:45PM - 25 Aug 22 UTC
### Purpose
This change is in related to the issue mentioned here: https://gi… thub.com/DynamoDS/Dynamo/issues/13168
Even though no-one from the team was able to reproduce this, the user states that when the value in the slider is changed by moving the slider, the max value of the slider is set to a new value if the new value is greater than the previous max value.
The public T Value{} property is only triggered when the value in slider is changed by dragging it. As the value in the slider cannot exceed the max value and the max/min value should not be changed in this case. So, we shouldn't be needing those conditions.
### Declarations
Check these if you believe they are true
- [ ] The codebase is in a better state after this PR
- [ ] Is documented according to the [standards](https://github.com/DynamoDS/Dynamo/wiki/Coding-Standards)
- [ ] The level of testing this PR includes is appropriate
- [ ] User facing strings, if any, are extracted into `*.resx` files
- [ ] All tests pass using the self-service CI.
- [ ] Snapshot of UI changes, if any.
- [ ] Changes to the API follow [Semantic Versioning](https://github.com/DynamoDS/Dynamo/wiki/Dynamo-Versions) and are documented in the [API Changes](https://github.com/DynamoDS/Dynamo/wiki/API-Changes) document.
- [ ] This PR modifies some build requirements and the readme is updated
### Release Notes
The min and max value cannot be changed when the slider value is changed by adjusting the slider.
### Reviewers
@QilongTang @mjkkirschner
Hello,
in my side, the bug persist in Dynamo 2.16
my config
thanks for continuing to report this issue all, we’ve tracked it down to this change - Fix the API call to update the value on the slider. by reddyashish · Pull Request #12786 · DynamoDS/Dynamo · GitHub
looking for a fix for both issues.
sniken
October 24, 2022, 3:23pm
12
Thank you Michael,
is there a recommended Sandbox version/Build that has:
fixed the number slider issue
ability to make geometry
?
no, not at the current time - this fix is in 2.17 builds, but so is the update to a new unreleased geometry kernel.
sniken
November 17, 2022, 11:30pm
14
Is it true that the latest revit hotfix now installs dynamo 2.16.1
…and still has the slider bug ?
Hi, I still have this problem V2.16.1