DirectOptionMenus are broken in 1.10.3, In both the SDK and distributable versions, it seems.
I’ve opened an issue for this matter here.
This has me a little anxious, as it’s somewhat blocking me: I want to release a small test-program for my key-mapper module (different to the previous one), and furthermore am hoping to move towards releasing a demo of my main project soon.
I could probably work with 1.10.2, of course. But then I miss out on the various fixes of 1.10.3–including some gamepad fixes that I’m hoping might work with my own gamepad.
If that’s what’s called for, then fair enough.
However, as noted in the issue linked-to above, there does seem to be a fix for this issue, added via a recently-closed pull-request. Would it then be feasible for a big-fix version of 1.10.3 to be made, incorporating that fix?
Further if a new version is built, may I request that the following pull-requests be reviewed for it? They implement some changes to DirectOptionMenu that would be useful to me.
- Menu-items retain their keyword properties after the item-list is changed
- Cleanup of menu-items when re-creating the item-list, and
- An “empty list” label for cases in which a DirectOptionMenu has no items.
(If only one of the above were to be included, I think that I’d want it to be the first: without it, DirectOptionMenus can become inconsistent with the style of the rest of the UI as soon as their item-lists are changed.)
If such additions are infeasible for a bug-fix build, then that’s fair enough! They’d be useful to me, and it seems worth asking, but the lack of them doesn’t break functionality, as far as I’m aware.