Known Issues

Alpha 0.1

# Issue Status
1 Control frames (provided by the ControlFrame class) are not currently functioning properly by default.  When a control is created it sets its Frame property to a new instance of ControlFrame.  The user should simply need to enable the frame by setting control.Frame.Enabledto true.  However, when set to true, the default state of the frame is not rendered properly around the boundary of the control.

Update 1:  The cause is due to the ScreenManager rendering the control’s default close button and title bar text even though the default state of the Frame object has its top, bottom, left, and right borders disabled.  You can get around this issue temporarily by setting the top border’s Enabledproperty to true and ensuring it has a size big enough to fit the font size of the title bar text.

Update 2:  There are a lot of properties that must be set properly on the Frame object before it will render properly, the number of properties and options exist to give users more control in making just the right type of border they want.  However, creating custom borders is currently a tedious process.  Until a more convenient method is developed, it’s best to use the Frames static class to get a properly constructed Frame object.  You can currently use the CreateSimpleFrame() method or the SimpleSquared_TitleBarTop_InnerBorder preset.  More presets may be added in the future.

Fixed in 0.1.1
2 The close button (X button at the top-right) of a Frame object is not yet functional Fixed in 0.1.1
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: