Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Options
FeatureTree Scroll Speed Too Fast
john_mcclary
Member, Developers Posts: 3,898 PRO
The scroll speed of the feature tree does not play by the rules.
I have my scroll speed set to (3) in windows settings.
OnShape (or the browser) appears to be trying to "help" us by increasing the scroll speed on larger trees.
After some quick experimenting the speed it comes up with is based on how tall the tree "view area" is. (I hope that makes sense)
The problem is whatever scroll speed it comes up with, windows then multiplies it by window's scroll speed setting.
In the example below you see the last feature is MD #Shingle Trim a.
One click of the scroll wheel down with the scroll speed set to 1 will scroll down the tree by 7 lines. (in Chrome)
When windows scroll is set to 3 it's scrolling 21 lines. (equivalent of page down, if page down actually worked in the feature tree)
So any scroll setting above 3 in this case will mean one click down with the wheel will scroll more lines than what is shown in the feature tree at any given time. So the only way to get to some features is to manually grab the scrollbar and drag.
The tree should follow the same rules as every other app, 1 click should equal 1 line of scrolling in the tree, then multiply by windows setting. A user will be expecting a scroll speed consistent with all the rest of your apps. Not based off the current height of the tree multiplied your expectation.
In firefox the tree behaves much differently. Each click will be about 1 line in this case until you bump up your setting in windows to be more extreme. When I bumped it up to 100 lines per click, firefox scrolled 21 lines. In order to get it to scroll the 3 lines at a time I had to set windows scroll speed to 12.
So I don't know if this problem is browser specific, or OnShape trying to help us scroll, and each browser interpreting it differently. But it is something that should be addressed.
I have my scroll speed set to (3) in windows settings.
OnShape (or the browser) appears to be trying to "help" us by increasing the scroll speed on larger trees.
After some quick experimenting the speed it comes up with is based on how tall the tree "view area" is. (I hope that makes sense)
The problem is whatever scroll speed it comes up with, windows then multiplies it by window's scroll speed setting.
In the example below you see the last feature is MD #Shingle Trim a.
One click of the scroll wheel down with the scroll speed set to 1 will scroll down the tree by 7 lines. (in Chrome)
When windows scroll is set to 3 it's scrolling 21 lines. (equivalent of page down, if page down actually worked in the feature tree)
So any scroll setting above 3 in this case will mean one click down with the wheel will scroll more lines than what is shown in the feature tree at any given time. So the only way to get to some features is to manually grab the scrollbar and drag.
The tree should follow the same rules as every other app, 1 click should equal 1 line of scrolling in the tree, then multiply by windows setting. A user will be expecting a scroll speed consistent with all the rest of your apps. Not based off the current height of the tree multiplied your expectation.
In firefox the tree behaves much differently. Each click will be about 1 line in this case until you bump up your setting in windows to be more extreme. When I bumped it up to 100 lines per click, firefox scrolled 21 lines. In order to get it to scroll the 3 lines at a time I had to set windows scroll speed to 12.
So I don't know if this problem is browser specific, or OnShape trying to help us scroll, and each browser interpreting it differently. But it is something that should be addressed.
Tagged:
4
Comments
"Lines" are not all the same and in the OS looking at windows explorer vs the number of rows that might be in a list in the browser which can be set with CSS could be 3X based on the row height.
Scrolling the feature tree in Chrome seems to advance about a page worth of lines with a single wheel click. Firefox is still one line per wheel click.
I'm not sure whether something in Onshape changed, or if something in Chrome happened to change at the same time, but Chrome used to work the same as Firefox (one line per wheel click) before the last Onshape update.
I tried just working out of firefox, but chrome has much more performance while modeling. So I'll take the lesser of two evils for now and stick with crome for now
For Onshape developers, here is an example screen grab of what I am experiencing. As you can see, each wheel movement causes all of the visible feature items to scroll off the screen.
Interestingly, the Documents page still scrolls normally (1 to 2 items per wheel movement). It's only the Feature Tree that seems to be doing this.
Hell i don't even click the X to close a window.. just hold alt+f4 until the windows shut down message appears, hit enter and grab my coat and head home
Twitter: @onshapetricks & @babart1977
I also find I go to grab the roll bar an instead grab a feature and move it up the tree causing errors, just thought it was worth mentioning
Twitter: @onshapetricks & @babart1977
You make the request I'll put in my vote
Twitter: @onshapetricks & @babart1977