Quantcast
Channel: Recent Additions to 'Buttons and Textures - setting to nil doesn't remove them from the screen?'
Browsing latest articles
Browse All 5 View Live

forums/development/623/1

You cannot remove a button. Once it's created, it's always there and you are 100% responsible for hiding (or re-using) the button as appropriate. Buttons are not garbage collected, and in fact can...

View Article


forums/development/623/2

So how do people who use buttons for scrolling tables and the like deal with reusing? Something is fishy... All other frame type elements dislodge but buttons don't? I can understand if textures don't...

View Article


forums/development/623/3

No frame elements or textures are ever freed. Ever. If you have a scrolling list, you simply create the number you want to display (say 20) and then only ever display those 20. The chapter on scrolling...

View Article

forums/development/623/4

That makes sense I guess. A little disheartening, but sure clears up some of the behaviors I've seen. Well, in this instance I'd like to create four buttons (which I do by array). Then I'm calling...

View Article

forums/development/623/5

> That makes sense I guess. A little disheartening, but sure clears up some of the behaviors I've seen. >> Well, in this instance I'd like to create four buttons (which I do by array). Then...

View Article

Browsing latest articles
Browse All 5 View Live