Programming C, C++, Java, PHP, Ruby, Turing, VB
Computer Science Canada 
Programming C, C++, Java, PHP, Ruby, Turing, VB  

Username:   Password: 
 RegisterRegister   
 Never Use View.Update
Index -> Programming, Turing -> Turing Tutorials
Goto page Previous  1, 2
View previous topic Printable versionDownload TopicRate TopicSubscribe to this topicPrivate MessagesRefresh page View next topic
Author Message
DemonWasp




PostPosted: Tue Dec 15, 2009 4:16 pm   Post subject: RE:Never Use View.Update

Mario's background scrolls past him, does it not?
Sponsor
Sponsor
Sponsor
sponsor
mirhagk




PostPosted: Wed Dec 16, 2009 8:09 am   Post subject: RE:Never Use View.Update

no i said where the background remains the same. Kinda like a static background image or even just a blank black background or something
Tyr_God_Of_War




PostPosted: Wed Feb 10, 2010 4:29 pm   Post subject: RE:Never Use View.Update

But the area behind where Mario was needs updating as well. Make sure to keep track of that.
evildaddy911




PostPosted: Sat Jan 07, 2012 11:13 am   Post subject: Re: Never Use View.Update

on the same note, Time.DelaySinceLast() is slightly better than Time.Delay() or delay(), delay() causes a delay no matter what, while Time.DelaySinceLast() only delays if it is needed, and only as much as is needed, causing most lag to disappear.
Dreadnought




PostPosted: Sat Jan 07, 2012 5:38 pm   Post subject: Re: Never Use View.Update

@ evildaddy911

1 - Your necroing.
2 - Time.DelaySinceLast is not "slightly better" than Time.Delay. Rather its functionality (which is different from Time.Delay) is more useful in common situations (namely animation). It should not be regarded as a direct substitute for Time.Delay.
Display posts from previous:   
   Index -> Programming, Turing -> Turing Tutorials
View previous topic Tell A FriendPrintable versionDownload TopicRate TopicSubscribe to this topicPrivate MessagesRefresh page View next topic

Page 2 of 2  [ 20 Posts ]
Goto page Previous  1, 2
Jump to:   


Style:  
Search: