You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// Initially we used 'upper_popup->OpenParentId == window->IDStack.back()' to differentiate multiple menu sets from each others
7100
7100
// (e.g. inside menu bar vs loose menu items) based on parent ID.
7101
-
// This would however prevent the use of e.g. PuhsID() user code submitting menus.
7101
+
// This would however prevent the use of e.g. PushID() user code submitting menus.
7102
7102
// Previously this worked between popup and a first child menu because the first child menu always had the _ChildWindow flag,
7103
-
// making hovering on parent popup possible while first child menu was focused - but this was generally a bug with other side effects.
7103
+
// making hovering on parent popup possible while first child menu was focused - but this was generally a bug with other side effects.
7104
7104
// Instead we don't treat Popup specifically (in order to consistently support menu features in them), maybe the first child menu of a Popup
7105
7105
// doesn't have the _ChildWindow flag, and we rely on this IsRootOfOpenMenuSet() check to allow hovering between root window/popup and first child menu.
7106
7106
// In the end, lack of ID check made it so we could no longer differentiate between separate menu sets. To compensate for that, we at least check parent window nav layer.
7107
7107
// This fixes the most common case of menu opening on hover when moving between window content and menu bar. Multiple different menu sets in same nav layer would still
7108
7108
// open on hover, but that should be a lesser problem, because if such menus are close in proximity in window content then it won't feel weird and if they are far apart
0 commit comments