StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20813250
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-12-28T10:01:07.713
FavoriteCount
0
LastActivityDate
2015-01-26T07:57:25.873
LastEditDate
2015-01-26T07:57:25.873
LastEditorUserId
2520789
OwnerUserId
2520789
ParentId
18645032
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
Actually there is a very simple solution to this. As Pinckerman did point out, you need to know the aspect ratio (screen ratio), but you will be using it in the SpriteBatch.Begin method, where you will pass the Vector2 scale through a Matrix.CreateScale(Vector3 Here, where Z is 1), and use it as final argument in the SpriteBatch.Begin method. Most other arguments in this case can be left Null. Basically what it does is, it tells the spritebatch to draw everything with an offset (the scale) applied to both position and size. This means that when, in my case, I place something on 640x400, no matter what resolution I run in the screen, it still starts off dead center of the screen. Quite useful if you ask me. Example from my current project: <pre><code>/// <summary> /// Resolution /// </summary> public static class Resolution { private static Vector3 ScalingFactor; private static int _preferredBackBufferWidth; private static int _preferredBackBufferHeight; /// <summary> /// The virtual screen size. Default is 1280x800. See the non-existent documentation on how this works. /// </summary> public static Vector2 VirtualScreen = new Vector2(1280, 800); /// <summary> /// The screen scale /// </summary> public static Vector2 ScreenAspectRatio = new Vector2(1, 1); /// <summary> /// The scale used for beginning the SpriteBatch. /// </summary> public static Matrix Scale; /// <summary> /// The scale result of merging VirtualScreen with WindowScreen. /// </summary> public static Vector2 ScreenScale; /// <summary> /// Updates the specified graphics device to use the configured resolution. /// </summary> /// <param name="device">The device.</param> /// <exception cref="System.ArgumentNullException">device</exception> public static void Update(GraphicsDeviceManager device) { if (device == null) throw new ArgumentNullException("device"); //Calculate ScalingFactor _preferredBackBufferWidth = device.PreferredBackBufferWidth; float widthScale = _preferredBackBufferWidth / VirtualScreen.X; _preferredBackBufferHeight = device.PreferredBackBufferHeight; float heightScale = _preferredBackBufferHeight / VirtualScreen.Y; ScreenScale = new Vector2(widthScale, heightScale); ScreenAspectRatio = new Vector2(widthScale / heightScale); ScalingFactor = new Vector3(widthScale, heightScale, 1); Scale = Matrix.CreateScale(ScalingFactor); device.ApplyChanges(); } /// <summary> /// <para>Determines the draw scaling.</para> /// <para>Used to make the mouse scale correctly according to the virtual resolution, /// no matter the actual resolution.</para> /// <para>Example: 1920x1080 applied to 1280x800: new Vector2(1.5f, 1,35f)</para> /// </summary> /// <returns></returns> public static Vector2 DetermineDrawScaling() { var x = _preferredBackBufferWidth / VirtualScreen.X; var y = _preferredBackBufferHeight / VirtualScreen.Y; return new Vector2(x, y); } } </code></pre> And usage: <pre><code> /// <summary> /// Draws the game objects to the screen. Calls Root.Draw. /// </summary> /// <param name="gameTime">The game time.</param> protected override void Draw(GameTime gameTime) { // TODO: Camera SpriteBatch.Begin(SpriteSortMode.Immediate, null, null, null, null, null, Resolution.Scale); Root.Draw(SpriteBatch, gameTime); SpriteBatch.End(); base.Draw(gameTime); } </code></pre> Hope this example code is helpful. NOTE: Doing it the way Pinckerman suggested isn't a wrong way, however I'm led to believe that apart from the obvious (initially more code, but in the long run way less), what Pinckerman suggested may also take up more performance. This is only a hunch, and it's merely based on the GPU probably being more efficient in calculations related to screen placement than the CPU. But don't hang me up on it. @Edit: To get Mouse coordinates in relation to objects on the screen: <pre><code>public Vector2 GetMouseCoords() { var screenCoords = Mouse.GetPosition(); // Or whatever it's called. var sceneCoords = screenCoords / Resolution.ScreenScale; return sceneCoords; } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POChange and scale resolution of XNA game
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USFalgantil
UserOwnerUserId
1. USFalgantil
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.