<Skipp_OSX>
you can test the feature if you wish but all I really need to know is that it doesn't crash horribly or not activate menu items when it should
<Skipp_OSX>
To test feature you must know what is wrong in current build. If you don't, keyboard navigation works as long as mouse cursor is outside the menu, but not when it is inside the menu. You should see that keyboard navigation still works even when your mouse is over the menu even a supermenu with menu items. The mouse is entirely ignored when it is obscured.
<x512[m]>
IsCursorObscured is immediate NAK. It is fundamentally wrong at least because of its asynchronous nature (cursor obscured state may change anytime after being queried, so queried value means nothing).
<Skipp_OSX>
well test anyway
<x512[m]>
As I said before, you should always call obscure cursor without attempting checks that cursor is obscured.
<Skipp_OSX>
so obscure cursor in app server doesn't say what it says it does in the Be Book?
<Skipp_OSX>
every time you key down a nav key it re-obscures the cursor already.
<x512[m]>
> ObscureCursor() hides the cursor until the user moves the mouse.
<Skipp_OSX>
right
<Skipp_OSX>
so if the user moves the mouse the cursor is no longer obscured which is exactly what I want.
<x512[m]>
This is how Haiku behaves, I see no problem. Calling ObscureCursor() if cursor is already obscured is fine.
<Skipp_OSX>
I see no reason not to expose the obscure state from app_server, it works.
<x512[m]>
There are absolutely no need of IsCursorObscured.
<Skipp_OSX>
The menu feature depends on it.
<x512[m]>
No, it doesn't. Just always call ObscureCursor().
<Skipp_OSX>
I do
<x512[m]>
So why use IsCursorObscured()?
<Skipp_OSX>
so that the mouse will take us out of obscured and I track menu differently.
<Skipp_OSX>
the mouse way
<Skipp_OSX>
we're in a different menu tracking thread here
<x512[m]>
I am not even see obscuring cursor in menu as good idea. Is it done be BeOS? Other OSes seems not do that.
<Skipp_OSX>
as I said it is badly broken and not to go off of, they should have made obscure cursor public back then and did it my way.
HaikuUser has joined #haiku
HaikuUser has quit []
nipos has joined #haiku
<x512[m]>
"did it my way", "vision" is wrong approach and quick way to trigger controversy an d change rejection. Just fix bugs without altering behavior any you will be loved by everyone.
<x512[m]>
I see meaning on differencing Esc behavior depending on obscured cursor. There are separate shortcut for closing whole menu chain: Alt+Esc.
<x512[m]>
meaning -> no meaning
drumr has quit [Quit: Leaving]
drumr has joined #haiku
drumr has quit [Quit: Leaving]
drumr has joined #haiku
<Skipp_OSX>
I don't want to be loved by everyone I want the menu to work right
<AlienSoldier>
i want to be loved by the menu
Chain|Q has quit [Quit: [.life.support.system.failure.]]