Strange key behavior on Windows

[Paul Kitt]

I am running the 64-bit version of 0.12.0 on a Win 7 machine. Immediately after starting Stellarium, the arrow keys do not function until a mouse button is clicked once.

Paul

[Alexander Wolf (alexwolf)]

I can reproduce this issue only on Windows.

[Keatah (keatah)]

Apologies for being lazy and not looking for a duplicate before posting 1075671

I just discovered a work-around of sorts - like a triple click on the Stellarium desktop icon.

You double-click the desktop icon as usual. And then do a third click a moment later when the splash screen comes up. This third splash-screen-click is good enough to get 100% focus. The arrow keys work and the F3 search box input dialog works too.

[Alexander Wolf (alexwolf)]

I'm merge two bug reports because those bugs have one source of troubles.

[Alexander Wolf (alexwolf)]

I can reproduce this issue on linux with Qt 4.8.1.

[Pierluigi Panunzi (piellepi)]

Alexander, yesterday I posted a bug for a problem I found since versione 0.12.1: you answered me by email that it's a duplicate for this bug...
i'm not so sure it's a duplicate, so I copy and paste the bug report here, so it won't be hidden or forgot... :)

---------------------------------------------------
I have downloaded the Stellarium 0.12.2 Release Candidate 2 version for 64bit Windows.
  Unfortunately I found the same bug I signalled some time ago, but I'm not able to find again my old report.
  So I think to repost this bug again, hoping it will be soon corrected: this bug is really irritating! :O

  The big problem is this:

  - start WHATEVER version of Stellarium from 0.12.1 on and don't do anything except what I say now!
  - press F3 or Ctrl-F in order to open the "Find Object or Position" dialog box : suppose for example we want to find the star Acamar
  - as soon as you digit the first letter (the "A") it is INTERPRETED AS A COMMAND (in this case switching the Atmoshere status) instead of being ENTERED INTO the dialog box
  - if you go on entering other letters, they are always interpreted as COMMANDS.

  Really ugly!

  As a programmer I say that the bug could be easily solved:
  technically, when you press FOR THE FIRST TIME the key F3 or Ctrl-F,
  the dialog box is created, but it does not RECEIVE THE FOCUS (even if
  the blinking cursor is present in the input box) so subsequent keys
  are not inserted in the relevant input box: in this situation you
  succeed in inputing letters correctly into the input box, ONLY IF you
  REMEMBER to click prevously on it with the mouse...

  It's a recurrent bug as I said and it's very common to start
  Stellarium, searching for an object and finding yourself in a
  different scenario, just because your input in intercepted by the
  program and executed as single commands.

  Please, correct it !! :)

  Thanks again!
  Pierluigi

[Bogdan Marinov (daggerstab)]

The e-mail you are getting are automatic notifications sent by Launchpad when someone posts comments to a bug report you have opened. When you open a bug report, Launchpad subscribes you to all e-mail notifications for it.

For some reason, since several versions, on Windows the "sky" object does not receive keyboard focus after the program is started, even though it should. Since all window widgets are children of this object, it appears that the lack of focus propagates. (Or more precisely, the focus fails to propagate correctly to the children.) It's either some Qt bug, or some peculiar interaction of the way Stellarium uses Qt and the Windows-specific code in Qt.

[Alexander Wolf (alexwolf)]

This bug was introduced before merger of new keybindings.

[Alexander Wolf (alexwolf)]

Looks like this bug has been introduced since revision 5573

[Alexander Wolf (alexwolf)]

I guess this bug is gone on 0.13.0 alphas - can you check it?

[henrysky (henry-leung-2010)]

This issue cannot be reproduced on hp notebook with actual mouse with stellarium 0.13.0 alpha 7.2 on Windows 7 64bit and macbook air with trackpad with stellarium 0.13.0 alpha 7.2 on Windows 7 64bit bootcamp

[Alexander Wolf (alexwolf)]

Thanks for testing!