StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16152888
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-04-22T17:16:53.843
FavoriteCount
0
LastActivityDate
2013-04-22T17:16:53.843
LastEditDate
LastEditorUserId
0
OwnerUserId
2245917
ParentId
11380586
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I know the post is old but! If you're still interested, here's my take on the subject: The <code>Surface</code> objects returned by the <code>Video.SetVideoMode()</code> method and the <code>Video.Screen</code> property are not equal but they both use the same Handle, which is the pointer to the graphical data. I would say it's mostly a matter of style, both are valid ways to work on your main display surface. <ul> <li><code>Video.SetVideoMode()</code> leads to the following in Video.cs: <pre><code>public static Surface SetVideoMode(int width, int height, int bitsPerPixel, bool resizable, bool openGL, bool fullScreen, bool hardwareSurface, bool frame) { /* ... */ return new Surface(Sdl.SDL_SetVideoMode(width, height, bitsPerPixel, (int)flags), true); } </code></pre> ... calling the following internal constructor in Surface.cs: <pre><code>internal Surface(IntPtr handle, bool isVideoMode) { this.Handle = handle; this.isVideoMode = isVideoMode; } </code></pre></li> <li>Alternatively, this is the <code>Video.Screen</code> property definition in Video.cs: <pre><code>/// <summary> /// Gets the surface for the window or screen, /// must be preceded by a call to SetVideoMode /// </summary> /// <returns>The main screen surface</returns> public static Surface Screen { get { return Surface.FromScreenPtr(Sdl.SDL_GetVideoSurface()); } } </code></pre> ... calling the following internal factory method in Surface.cs: <pre><code>internal static Surface FromScreenPtr(IntPtr surfacePtr) { return new Surface(surfacePtr); } </code></pre> ... in turn calling the following internal constructor in Surface.cs: <pre><code>internal Surface(IntPtr handle) { this.Handle = handle; } </code></pre></li> </ul> If you compare the Handles of the <code>Surface</code> objects returned by <code>Video.SetVideoMode()</code> and <code>Video.Screen</code>, you will see that they are equal, which is all you need to know to make sure that you are actually working with the same data. Hope this helps! Sources: <a href="https://www.assembla.com/code/lightcs/subversion/nodes/trunk/sdldotnet-6.1.0/source/src/Graphics/Video.cs?rev=4" rel="nofollow">https://www.assembla.com/code/lightcs/subversion/nodes/trunk/sdldotnet-6.1.0/source/src/Graphics/Video.cs?rev=4</a> <a href="https://www.assembla.com/code/lightcs/subversion/nodes/trunk/sdldotnet-6.1.0/source/src/Graphics/Surface.cs?rev=4" rel="nofollow">https://www.assembla.com/code/lightcs/subversion/nodes/trunk/sdldotnet-6.1.0/source/src/Graphics/Surface.cs?rev=4</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing Video.Screen instead of Surface object in SdlDotNet
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USOlivier
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.