Was always on the first screen since the screen number was determined
incorrectly. Thanks to Christian Hönig for reporting the issue.

Reviewed-by: Daniel Molkentin