So according to Sam, our resident Xorg expert, the only way to fix this
is to have Onboard set itself as a transient of the Dash window,
allowing it to then correctly get stacked above the Dash (which,
obviously, has the right hints set to stay above other apps).
I'm somewhat sure this will work as we already have Input Method support
working (specifically IBus) which happily throws up a GtkWindow above
the Dash and allows the user to click on it etc.
I also quickly converted Onboard's gtk-window to say it was type dock,
and it stayed above the Dash and could be used to drive search just
fine.
There are two ways we could do this, either I have Unity publicise the
Dash's xid over D-Bus or as a xproperty on the root window, or Unity
itself looks out for the Onboard window and makes it a transient when
the Dash shows (and maybe unset's when it hides).
I'm prepared to have a go at the latter, if nothing else than for a test
case, though it's obviously flawed in that it would be only useful for
Onboard (which, this late in the cycle, might well be acceptable).
Thoughts?
** Changed in: unity (Ubuntu Oneiric)
Assignee: (unassigned) => Neil J. Patel (njpatel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/739812
Title:
Must use hardware keyboard to perform search for applications in Unity
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/739812/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
