I want to use the default key-loop calculation for most of my app except one view, where the views have a specific numbered order but visually are not left to right, top to bottom. when using the windows automatic key-loop setup, setting nextKeyView gets override it appears. I can override the property and return the next view, but then there are issues with leaving the loop now. When the last item has focus, the next key view should be the top-most view to the right, but instead it gets stuck. And shift-tabbing backwards goes to the last item before entering the key-view loop. Is there a best practice and example of how to do this?
