python - Pygame: strange behaviour of a drawn rectangle -


i'm trying make lifebar class game in pygame. i've done this:

class lifebar():     def __init__(self, x, y, max_health):         self.x = x         self.y = y         self.health = max_health         self.max_health = max_health      def update(self, surface, add_health):         if self.health > 0:             self.health += add_health             pygame.draw.rect(surface, (0, 255, 0), (self.x, self.y, 30 - 30 * (self.max_health - self.health) / self.max_health, 10))       print(30 - 30 * (self.max_health - self.health) / self.max_health)

it works, when tried down health zero, rectangle surpasses left limit bit. why happen?

here have code try on own (just run if explanation of problem wasn't clear):

import pygame pygame.locals import * import sys  width = 640 height = 480  class lifebar():     def __init__(self, x, y, max_health):         self.x = x         self.y = y         self.health = max_health         self.max_health = max_health      def update(self, surface, add_health):         if self.health > 0:             self.health += add_health             pygame.draw.rect(surface, (0, 255, 0), (self.x, self.y, 30 - 30 * (self.max_health - self.health) / self.max_health, 10))         print(30 - 30 * (self.max_health - self.health) / self.max_health)  def main():     pygame.init()      screen = pygame.display.set_mode((width, height))     pygame.display.set_caption("prueba")       clock = pygame.time.clock()      lifebar = lifebar(width // 2, height // 2, 100)      while true:         clock.tick(15)         event in pygame.event.get():             if event.type == pygame.quit:                 sys.exit()          screen.fill((0,0,255))          lifebar.update(screen, -1)          pygame.display.flip()  if __name__ == "__main__":     main()

i think it's because code draws rectangles less 1 pixel wide, , though pygame documentation says "the area covered rect not include right- , bottom-most edge of pixels", apparently implies does include left- , top-most edges, giving results. arguably considered bug—and shouldn't draw in cases.

below workaround avoids drawing rects less whole pixel wide. simplified math being done bit make things more clear (and faster).

    def update(self, surface, add_health):         if self.health > 0:             self.health += add_health             width = 30 * self.health/self.max_health             if width >= 1.0:                 pygame.draw.rect(surface, (0, 255, 0),                                   (self.x, self.y, width, 10))                 print(self.health, (self.x, self.y, width, 10))

Comments

Post a Comment

Popular posts from this blog

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

i'm implementing inapp billing in android app. works well, however, i'm trying decouple broadcast receiver activity manifest. suggestion in android's trivialdrive sample: // important: dynamically register broadcast messages updated purchases. // register receiver here instead of <receiver> in manifest // because call getpurchases() @ startup, therefore can ignore // broadcasts sent while app isn't running. // note: registering listener in activity bad idea, done here // because sample. regardless, receiver must registered after // iabhelper setup, before first call getpurchases(). currently there's class extends broadcastreceiver : public class iabbroadcastreceiver extends broadcastreceiver { /** * intent action receiver should filter for. */ public static final string action = "com.android.vending.billing.purchases_updated"; private final iabbroadcastlistener mlistener; public iabbroadcastreceiver(iabbroadcastlistener listener) { m...
Read more

python Tkinter Capturing keyboard events save as one single string -

is possible store keyboard events 1 string? code below stores 1 char , prints it. card reader or bar code reader, contains collection of character/ string not 1 character @ time. goal save char pressed text variable. from tkinter import * root = tk() def key(event): text= event.char text+= event.char print ("pressed", text) def callback(event): frame.focus_set() print ("clicked at", event.x, event.y) frame = frame(root, width=100, height=100) frame.bind("<key>", key) frame.bind("<button-1>", callback) frame.pack() root.mainloop() currently, creating text variable , everytime key() function gets called, , text stores last character typed. you can define text module level variable , , use module level text inside key function - text = '' def key(event): global text text+= event.char print("pressed", text)
Read more

sql server - Why does Linq-to-SQL add unnecessary COUNT()? -

here tables: create table customer ( cid int primary key, name varchar(32) ) create table ord ( oid int primary key, cid int foreign key references customer, address varchar(20) ) here's linq-to-sql statement: var aaa = c in db.customer select new { c, o = c.ord.tolist() }; and here's inexplicable query generated linq-to-sql: select [t0].[cid] [cid], [t0].[name] [name], [t1].[oid] [oid], [t1].[cid] [cid2], [t1].[address] [address], (select count(*) [dbo].[ord] [t2] [t2].[cid] = [t0].[cid]) [value] [dbo].[customer] [t0] left outer join [dbo].[ord] [t1] on [t1].[cid] = [t0].[cid] order [t0].[cid], [t1].[oid] i want understand how rid of count(*) part. it's entirely uncalled for! linq needs count(*) in order determine number of entries returned o = c.ord.tolist() .
Read more