[Bug 45810] Re: (Dapper) Doesn't start if the cursor is in the middle of the screen.

[kko]

VincentRC: Good catch. I hope you don't mind that I made a slight
grammatical change to the bug's title to make it unambiguous.

Same thing happens in Breezy with:
Qt: 3.3.4
KDE: 3.4.3
Katapult: 0.3.1

I did some further testing on this, and here's how Katapult behaves
under different window focus settings:

"Click to Focus": Moving the mouse does not affect Katapult. Clicking on
Katapult window does not affect it, i.e. behaves as expected.

"Focus Strictly Under Mouse":
- When mouse is in the Katapult area (center of screen) when Katapult hotkey is pressed, shows a faint effort to show Katapult, but disappears thereafter. Katapult somehow fails to properly grab the focus.
- When mouse is elsewhere, Katapult is able to start properly. See however also the last note.

"Focus Follows Mouse" AND "Focus Under Mouse":
- When mouse is in the Katapult area (center of screen) when Katapult's hotkey is pressed, it starts properly. However, see following.

"Focus Follows Mouse", "Focus Under Mouse" AND "Focus Strictly Under Mouse":
- When Katapult has been started, and mouse is moved on top of it, it stays focused. If you quickly move mouse off Katapult and then back on, Katapult starts to fade and then briefly stops fading (when you bring the mouse back) and then continues fading, i.e. doesn't regain focus.

** Summary changed:

- (Dapper) Doesn't start everytime the cursor is in the middle of the screen.
+ (Dapper) Doesn't start if the cursor is in the middle of the screen.

** Summary changed:

- (Dapper) Doesn't start if the cursor is in the middle of the screen.
+ (Dapper & Breezy) Doesn't start if the cursor is in the middle of the screen.

** Changed in: katapult (Ubuntu)
       Status: Unconfirmed => Confirmed

-- 
(Dapper & Breezy) Doesn't start if the cursor is in the middle of the screen.
https://launchpad.net/bugs/45810