ID:135832
 Feb 3 2004, 10:19 am
|
|
It would be nice if images had support for screen_loc. Then I could create lots of images with much, much better effeciency, as they don't have all that access crud to allocate on New().
| |
Polatrite wrote:
It would be nice if images had support for screen_loc. Then I could create lots of images with much, much better effeciency, as they don't have all that access crud to allocate on New(). I believe an object in memory is transparently handled based on an object template (this isn't an informed opinion, but it's an estimate based on what Dan and Tom have mentioned about memory handling) -- objects only store variables which are different than the template; otherwise the variables just translate to the template. Thus, creating a /obj has very little overhead unless you add in your own custom New() routines. | |
I don't know if I fully understand the reasoning behind this. An /image is basically just a glorified fraction of an /obj, and serves as a counterpart to HUD objects. You don't need /obj capabilities for most HUD objects, it's true, but then you're not really losing a lot anyway.
Lummox JR