I did a trivial hard-code binding fix for this issue in https://code.launchpad.net/~sil2100/unity-2d/trunk.lp839628 - but as Saviq noticed, this might not quite be the solution we are looking for. It's now a question who ultimately should be the one to pick up the F10 handling - the application, or unity? My fix makes unity-2d-panel be the one in control.
I did a trivial hard-code binding fix for this issue in https:/ /code.launchpad .net/~sil2100/ unity-2d/ trunk.lp839628 - but as Saviq noticed, this might not quite be the solution we are looking for. It's now a question who ultimately should be the one to pick up the F10 handling - the application, or unity? My fix makes unity-2d-panel be the one in control.