Hi, > Maybe look for examples where there is vertical scrolling, see how it is > built, and try to copy the patterns.
The pattern I tried was the same ie add a ScrollingViewPort. > Well, that seems to be the trend at least on Mac? For page content that is obviously cut off sure, but IMO not for items in a control where it's not obvious that you can scroll. > It isn't wrong, it just may not be what you need for your app. If you add > a property that has to be checked, that's a bit more code than making > assumptions about what kind of overflow you want. AFAIKS it's less code and less of a maintenance issue. If I copy those 400 lines of code as suggest and if the code changes in one file then it needs to change in the other, that can easily get out of sync and cause issues. > In the end for scrolling beads, I expect there will be one tuned to just > vertical. One tuned to just Horizontal. Which is fine but we don't have that yet. I’m a strong believer in getting it to work first, then optimise it, premature optimisation wastes time and often makes incorrect assumptions. The issue here was not vertical vs horizontal scrolling performance or application size but was horizontal scrolling not working at all and not being able to control the visibility of the scroll bars. Thanks, Justin
