Hey guys,

We're currently using a TreeView and having issues with it not scrolling entirely entirely to the bottom. I've attached a gif as an example (with a whole bunch of info redacted for privacy reasons - it's not actually that ugly!) - this is using the default Noesis template but we are having the same issue with our own custom implementation of a ScrollViewer and a TreeView & TreeViewItems. As you can see, in the default Noesis template the scroll wheel scrolling works just fine, but gamepad support is our priority.
Gif doesn't seem to be playing inline, but opening it in another tab works :)

I don't know if this will be helpful, but the layout pictured in this screen includes a TreeView with an explicit height, but it still has the issue even if we set the vertical alignment to stretch and let it occupy the full screen.

At this point I'm wondering whether this is a bug or if we're missing something, but either way we really do need a fix and any help would be much appreciated!

Thanks in advance!

Hi El, Dorian here!

Thanks for bringing this up! We've just managed to reproduce this on our end, and at first glance, this appears to be a bug in how Keyboard-Navigated Items are displayed in a ScrollViewer under certain circumstances (in my case for example, I was able to get the same result as you using a TreeView with a fixed Height, enveloped in a ViewBox).

We're currently investigating this; here's the Ticket we're using if you want to follow along: #5107

Thanks again, and catch you again soon!

- Dorian

Thanks for checking that one out Dorian!

I'm wondering if there's a hacky workaround for now that you can think of that we can implement into our custom TreeView until that fix comes through, so we can get that gamepad support working nicely?
Much appreciated!

Hi El!

The following may not work in your case, but if you're open to giving any of the below a try; there were a couple things in my test file that got me a visual/mechanical result similar to what you're looking for:

1) I'd say as a primary option, in the TreeView ItemContainer's Style, removing the Style's built-in Padding (setting all four quadrants to '0') consistently gave the desired result.
(In Studio, in the TreeView ItemContainer Style, you'll need to hover over the 'Padding' Property, click its 3-Dot menu, select 'Convert to Local' from the context menu, and that will then unlock the ability to input '0,0,0,0' here)

Additionally, the following also may also produce the desired result:
2) Removing the ViewBox enveloping the TreeView Element (if applicable)
3) If you are open to doing so, removing the fixed-Height from the TreeView Element may work.

Let us know if any of these work in the immediacy until we can get a proper fix out for y'alls,

- Dorian

Heya Dorian --
Thank you for the suggestions! Unfortunately it didn't work for us, but I'm sure it would be helpful for others having the same issue! We've got a custom implementation & templates so there wasn't any padding or viewboxes in the first place :( I'm wondering if there's something hacky we can do in the code behind maybe?? We have a custom scrollviewer but there doesn't seem to be any issues when using it elsewhere, just in the TreeView. would you be able to recommend something we can put in our custom TreeView code behind that could be a temp fix?

Thank you again!

Hello,

When navigating through a TreeView using the keyboard, each TreeViewItem uses the element named PART_Header in its template to decide what should be visible. I just noticed that in our NoesisTheme the PART_Header element is setting some Margin, and the element is placed inside the selection border, so that is why it appears cut when navigating to the edges of the TreeView. We will fix it in our theme styles.

Make sure the PART_Header element in your TreeViewItem template also covers the entire selection border.

Hope this helps.

Hi El, Dorian here again!

Just wanted to let you know that if you update your version of Noesis Studio to the latest version, you'll get the fix we made to resolve this.
(Will be in any version above 3.312-beta)

Let us know if this does the trick, or if you continue to run into issues.

Thanks again for taking the time to bring this to our attention, it's super appreciated!

- Dorian