Thanks Ed. I did read the breaking changes.
I’m not using createFocusTraverser() or a custom traverser.
I was using
setFocusContainer(true) in several places which I replaced with
setFocusContainerType(FocusContainerType::keyboardFocusContainer). That’s correct, right?
Here’s some more detail:
In JUCE 6.0.8, I used to have some debug code that I placed inside
FocusHelpers::getIncrementedComponent(), that would print out for me the traversal of components via the Tab Key.
In JUCE 6.1.2, this is all changed/rewritten. It seems the place you would do this is now
FocusHelpers::navigateFocus(), but in here it now traverses every single component, not just the ones that I have told to
I may need to change my approach, but I was doing some things like:
Having a custom component that has
setWantsKeyboardFocus(true) so that clicking on it unfocuses other components, but then using
focusChangedByTabKey to pass the keyboard focus to the next sibling component. In other words, clicking it grabs focus so that it unfocused any other component. However, if you tab to it, the tab key effectively skips over it to the next component. But this doesn’t seem to work the same way at all.
void IncDec::focusGained (FocusChangeType cause)
if (cause == focusChangedByTabKey)
auto direction = ComponentPeer::getCurrentModifiersRealtime().isShiftDown() == false;
Now, in JUCE 6.1.2, it ends up somewhere else entirely, I’m not sure how… because it seems that
moveKeyboardFocusToSibling() no longer does the same thing. I’m trying to step through what’s going on but it’s complicated.
My understanding so far (I may be wrong) is that there used to only be the concept of KeyboardFocus Traversal; now however, there is “Accessibility Focus Traversal” and Keyboard Traversal is only a subset of that.
But is there any way to exclude a component from Accessibility Focus Traversal? I haven’t really tried the screen reading stuff yet; I’m still developing the app and I barely had the tab key changing focus the way I wanted it. But let’s say you don’t want a screen reader to notice a certain component. Is there a method to remove it from the transversal completely?