iRBiS's picture

DisplayDevice.Bounds not set

Project:The Open Toolkit library
Version:1.0-beta-1
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:closed
Description

GameWindow starts with its center at (0, 0). This is because the (newly-independent) bounds are not defined. The bounds parameter in the DisplayDevice constructor introduced in revision 2461 was not used, so I made use of it. I know this patch basically restores the previous behavior of DisplayDevice.Bounds but is necessary for those who wish to use the latest builds. Please delete this issue if it was inappropriate.

AttachmentSize
bounds-param.patch672 bytes

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
the Fiddler's picture

#1

Status:open» confirmed

Thanks for the patch.

I've already fixed this in my working copy, but haven't committed the fix yet because I'm working on a related issue (fullscreen GameWindows appear on the wrong location when multiple monitors are connected).

the Fiddler's picture

#2

Title:GameWindow startup location» DisplayDevice.Bounds not set
Status:confirmed» fixed

Fix committed to rev. 2471.

the Fiddler's picture

#3

Version:0.9.x-dev» 1.0-beta-1
Status:fixed» closed

Closing issues fixed in 1.0 beta-1.