For our plugin, the workaround is working well, but only for menu items at the top level. If I create another submenu and add that to the top level menu, the items in the submenu still cannot be selected.
I made the following change in checkButtonState which seems to help:
original (with workaround):
if (! window.doesAnyJuceCompHaveFocus() && ! reallyContained)
new:
if (! window.doesAnyJuceCompHaveFocus() && ! reallyContained && ! isOverAny )
Hey all,
@rcohen 's fix worked like a charm for me. Was running into a similar issue with sub menus.
Seems weâre seeing a related problem, after applying that fix. After selecting an item, if we go back to the menu again, it has not retained the previous selection. Anyone else seeing that?
Hi Howard,
Is that after adding rcohenâs change to the commit?
We saw an improvment adding his change.
Best,
Rail
Never mind. Our team had not update with rcohenâs fix on our submodule. Dâoh! ![]()
hi all, our plugins are experiencing a similar issue on PT 2023.3 (only on Mac - both intel/m1), everything working fine on the previous version and in all other formats. The cullprit in our case seems to be that âfocusOfChildComponentChangedâ gets called when focus should have moved from one child component to another, and inside that call hasKeyboardFocus returns false, when it should return true. This makes some functionality of our plugin currently unusable, as we use this callback to hide a component which contains some knobs, and it gets hidden every time you try to control a knob.
I believe the issue is deeper than the fix proposed here, and in general something wrong is going on with keyboard focus in the new PT.
Let me know if it is usefull to provide a reproducible sample.
Really think Avid needs to fix it on their end. They made a breaking change that is affecting plugins we have no plans to update in the near future, but weâre getting calls from users about.
