At the moment there are plugins available forįirefox and for Safari. Integration with other Websites and Servicesīookmarking web pages and publications is very easy with our BibSonomyīrowser plugins - adding three useful buttons to your browsers.Here is an example in context from one of my recent projects. (Thanks to this answer for that insight.) When you create the popup preview window in your custom keyboard, you need to call tClippingEnabled(false) in order to get the popup window to display above the keyboard for Android API 22+. I describe that process at the end of this answer. It is more work, but you can make your own custom view to use as a keyboard. The problem described in the question above is just one of its many shortcomings. At least at the time of this writing (API 27), it hasn't been updated for a long time. Here is a video of API 26 exhibiting the problem, then I set the mClippingEnabled flag to false in PopupWindow.java and show the corrected behavior.įor anyone coming here in the future, I recommend not using KeyboardView. This may qualify for a bug report although the new constrained behavior may be the expected behavior. Other than using reflection, I don't see a way to correct the problem. SetClippingEnabled() works on API 22-26 to permit the preview key to pop outside the boundaries of the keyboard layout.
I also found this which also may be related. (Also see setAttachedInDecor.) This code does deal with the placement of the popup window, so it may be related to this problem. The only substantive difference I see between API 21 and API 22 is support for the FLAG_LAYOUT_ATTACHED_IN_DECOR flag. This is what the OP was seeing.ĪPI 24: Key preview is constrained to the boundaries of the keyboard but is otherwise clipped. Here is what I found with the various API levels.ĪPIs 17-21: Key preview is allowed to pop outside of the boundaries of the keyboard.ĪPIs 22,23,25-26: The key preview is constrained to the boundaries of the keyboard but does display in its entirety. Update: I took another look at what is going on. I have not found another way to disable clipping for this private PopupWindow, so this is just pointing a way to a resolution and not the resolution itself. Reflection will give access but is not ideal. The remaining question is: How to get clipping disabled? Unfortunately, mPreviewPopup is a private variable.
It says "screen," but it applies to the keyboard window as well. Setting this to false will allow windows to be accurately positioned. By default the window is clipped to the screen boundaries. Void setClippingEnabled (boolean enabled)Īllows the popup window to extend beyond the bounds of the screen. See setClippingEnabled in the documentation for PopupWindow. You can see that this approach works if you set a breakpoint at the above-referenced code and execute the following code: tClippingEnabled(false) If clipping can be disabled for the PopupWindow then the preview key will be able to "pop" outside of the keyboard view. The problem that you are seeing is because the PopupWindow is being clipped by its parent. The preview key is actually a PopupWindow created in the constructor for KeyboardView. How to overcome, so the preview for '5' and '2' are displayed at the same distance above their respective key as it is for '0' and '8'. The preview for key '8' is also shown above the button.īut the preview for key '5' is not shown above the button.Īnd the preview for key '2' is not shown above the button. The preview for key '0' is shown above the button. These screenshots illustrate the problem - the position of the preview for '0' and '8' is good, but for '5' and '2' it is not: Their vertical position is being constrained by the parent layout. I have created a custom keyboard, which works fine - except the preview views for the top two rows of keys are not displayed high enough.
0 kommentar(er)
