StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11879534
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-09T08:32:34.673
FavoriteCount
0
LastActivityDate
2012-08-09T08:38:39.287
LastEditDate
2012-08-09T08:38:39.287
LastEditorUserId
142637
OwnerUserId
142637
ParentId
11874952
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Your draw method is wrong. <pre><code>def drawMapArray(maparray): for x in range(mapWi,1): for y in range(mapHi,1): #Determines tile type. if maparray[y,x] == 1: screen.blit(grass1, (x*16, y*16)) </code></pre> <hr> The first error is <code>for x in range(mapWi,1)</code>. Have a look at the <a href="http://docs.python.org/library/functions.html#range" rel="nofollow"><code>range</code></a> function. You're using two parameters, so you loop from <code>mapWi</code> to <code>1</code>, which is not what you want. You want to loop from <code>0</code> to <code>mapWi</code>, so you have to use <pre><code>for x in range(mapWi): for y in range(mapHi): </code></pre> (using <code>xrange</code> would be even better, but that would be just a very minor improvement) Otherwise, nothing will be drawn on the screen. <hr> The second error is this line: <pre><code>if maparray[y,x] == 1: </code></pre> You'll get an <code>IndexError</code> because you mixed up the initialization of the array. It's actually <code>mapWi</code> high and <code>mapHi</code> wide. So, you should initalize it using <pre><code>groundArray = numpy.ones((mapHi,mapWi)) </code></pre> instead of <pre><code>groundArray = numpy.ones((mapWi,mapHi)) </code></pre> To illustrate it, just a little test: <pre><code>>>> numpy.ones((10,5)) array([[ 1., 1., 1., 1., 1.], [ 1., 1., 1., 1., 1.], [ 1., 1., 1., 1., 1.], [ 1., 1., 1., 1., 1.], [ 1., 1., 1., 1., 1.], [ 1., 1., 1., 1., 1.], [ 1., 1., 1., 1., 1.], [ 1., 1., 1., 1., 1.], [ 1., 1., 1., 1., 1.], [ 1., 1., 1., 1., 1.]]) >>> </code></pre> You'll see that using <code>(10, 5)</code> gives us an array of <code>height = 10</code> and <code>width = 5</code>. <hr> Sidenotes: <pre><code>for event in pygame.event.get(): if event.type == "QUIT": </code></pre> will do nothing. <code>event.type</code> is never a string <code>"QUIT"</code>. The type of the quit event is <code>12</code>, or better: <code>pygame.QUIT</code>; so it should read: <pre><code>for event in pygame.event.get(): if event.type == pygame.QUIT: </code></pre> Rewrite your mainloop like this: <pre><code>while gameRunning: drawMapArray(groundArray) for event in pygame.event.get(): if event.type == pygame.QUIT: gameRunning = False break #Updates display and then sets FPS to 30 FPS. pygame.display.update() fpsClock.tick(30) pygame.quit() </code></pre> to avoid calling <code>sys.exit</code>. Better: split your main loop into the three steps you usually do in a mainloop. <pre><code>while gameRunning: draw() # do all the drawing stuff in this function handle_input() # handle all input stuff in this function update() # update the game state in this function </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTile based game using pygame questions / problems
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USsloth
UserOwnerUserId
1. USsloth
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.