On Thu, 2 Jul 2026 15:41:43 GMT, Martin Fox <[email protected]> wrote:
>> Is a no-menu case a valid one? I mean, is this something we should be able >> to do for completeness sake, or it totally makes no sense? > > A Mac application should always have an application menu. The no-menu case > would require a developer to add a copy of the application menu to every > MenuBar in every window in their application. That doesn't sound useful to me > but I could be wrong. > > Currently if the number of common menus goes to zero for any reason I use the > default application menu instead. It got complicated trying to make a > distinction between null, an empty list, and a non-empty list where all the > menus are hidden. `<rant>`Yeah, I love it when my window is on monitor one, and the application menu is on monitor 3. I guess it was a fine idea back then when the only CRT screen had 512 × 342 pixels, and by moving the mouse way up the application menu popped up. All of this is gone now, but the paradigm remains, like that flower which used to be pollinated by beetles that went extinct 100 million years ago`</rant>` Getting back to the issue - does it mean you are ok with removing the setter and only exposing the final `ObservableList`? What do other people think? ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/1881#discussion_r3514631671
