Fixed
Status Update
No update yet.
Comments
mg...@google.com
mg...@google.com
ap...@google.com
I have the same issue. The floating toolbar keeps on stealing the focus. You can mouse click on text area but keyboard input wont work. Sometimes i can get the emulator to get the focus but it is so random. Sometimes clocing both left and mouse button on the emulator would fix it.
OS:
Xubuntu 15.10
OS:
Xubuntu 15.10
ap...@google.com
I have the same issue.
Clicking on the window title bar of the "device window" does not move the focus to the device but to the control button toolbar. I am unable to move the focus to the device via any other means (task bar or Alt-Tab etc.).
The workaround described by remcohaszing works, but I have to do this everytime after the device lost the focus, which is quite often, when developing.
So it's a real show stopper for me.
The only practical workaround I found is to set "focus on mouse over" instead of "focus on click" (which I don't like otherwise).
But even in this mode, when I move the mouse over the title bar (not the window contents) for the first time after the device lost it's focus by a *click* on another window, the toolbar gets the focus instead.
It works when I move the mouse to the title bar a second time *and* as long as I do not *click* somewhere outside the device window. Tabbing away is also like clicking.
So where is the difference between loosing the focus by click or tab against moveing the mouse?
My system is a current debian testing/unstable mix using xfce4 with xfwm4.
Clicking on the window title bar of the "device window" does not move the focus to the device but to the control button toolbar. I am unable to move the focus to the device via any other means (task bar or Alt-Tab etc.).
The workaround described by remcohaszing works, but I have to do this everytime after the device lost the focus, which is quite often, when developing.
So it's a real show stopper for me.
The only practical workaround I found is to set "focus on mouse over" instead of "focus on click" (which I don't like otherwise).
But even in this mode, when I move the mouse over the title bar (not the window contents) for the first time after the device lost it's focus by a *click* on another window, the toolbar gets the focus instead.
It works when I move the mouse to the title bar a second time *and* as long as I do not *click* somewhere outside the device window. Tabbing away is also like clicking.
So where is the difference between loosing the focus by click or tab against moveing the mouse?
My system is a current debian testing/unstable mix using xfce4 with xfwm4.
na...@google.com
I have narrowed the issue to using xfwm4 (I usually use 4.12.x and also tried 4.10.x).
I changed any corresponding options like "focus stealing prevention" and "honour ICCCM focus hint" and even disabled compositing, but all this doesn't matter.
I then tried several alternate window managers and they all worked including clicking, tabbing etc.:
openbox
fluxbox
jwm
lwm
I still don't blame xfwm4 alone, because I never ever had any other focus issue with xfwm4 since several generations. So I believe it's a combination of emulator's behaviour *and* xfwm4's behaviour.
Another hint: when I click on the avd and then on another window e.g. a shell window and then close this focused window, the emulator device gets the focus.
I changed any corresponding options like "focus stealing prevention" and "honour ICCCM focus hint" and even disabled compositing, but all this doesn't matter.
I then tried several alternate window managers and they all worked including clicking, tabbing etc.:
openbox
fluxbox
jwm
lwm
I still don't blame xfwm4 alone, because I never ever had any other focus issue with xfwm4 since several generations. So I believe it's a combination of emulator's behaviour *and* xfwm4's behaviour.
Another hint: when I click on the avd and then on another window e.g. a shell window and then close this focused window, the emulator device gets the focus.
Description
Component used: Lifecycle ViewModel SavedState
Version used: 2.9.0-alpha08
With the introduction of
CreationExtrasandviewModelFactory,AbstractSavedStateViewModelFactoryis no longer needed and should be deprecated or at least marked as discouraged since it forces the creation of aSavedStateHandlefor every ViewModel even if the ViewModel does not require one, causing pressure on the saved instance state size and additional book keeping.