-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keyboard up/down in textbox in floating anchorable focusing DropDownControlArea #225
Comments
We also encounter that problem so I tracked it down to be introduced in 64b30e7 by @LyonJack and in particular by changing the base type of DropDownControlArea class from UserControl to ContentControl. |
I have maket sure that bug,I set the title bar‘s 'Focusable' as false,that make it not get the focus |
Hi @LyonJack, I can see that you have changed Focusable to false in generic.xaml of AvalonDock library and only inside the template of LayoutAnchorableFloatingWindowControl. That would probably mean that if a theme is applied the problem will reoccur and also it is not clear if in other usages of DropDownControlArea we won't see the same issue.
That way it will be 'automatically` changed to false in all XAMLs and places of usage and we avoid the need to do changes in many places. |
Hi there,
i noticed strange behavior in your avalondock version when i have textbox in floating LayoutAnchorable.
If textbox in floating layoutAnchorable has focus and you prey keyup/keydown this textbox loses focus (even if textbox has multiple rows and caret should move to next/previous line).
in this case, caret is in "second line" and key up/down will result into focus lost of textbox and dropDownAreaControl is focused instead (i checked that in Snoop).
If anchorable is docked or there are multiple anchorables joined together, up/down arrows works.
There you can find modified test app (but i only added textbox into properties window)
I noticed same behavior for combobox (also in example and richtextbox). And tried this in edi version 01_02 and didnt notice this behavior...
The text was updated successfully, but these errors were encountered: