How about writing a MiniSecondLife class that inherits from SecondLife, but doesn't instantiate things automaticaly.
On 10/30/06, Michael Cortez <[EMAIL PROTECTED]> wrote:
Can we not have the ObjectManager be something that libsecondlife automatically starts up? Depending on what projects people are working on, having unnecessary (or duplicate) call back handlers getting registered by the library by default can have adverse effects. I love the work that's going on with the ObjectManager, but for example today it was throwing off bench marking of asset download code. If possible, can these various managers for things like Objects, Parcel info, chat, etc -- be loaded on demand by application developers using the library, rather then there by default? A default sample application could illustrate how to turn on the various components that people would like to use. Just imagine what it would be like if the InventoryManager was on by default, and was downloading your inventory on each login? Eeeeek :) BTW would you be interested in me working with the TextureEntry class, so that'll automatically download and cache textures that are encountered? -- Mike C. _______________________________________________ libsecondlife-dev mailing list libsecondlife-dev@gna.org https://mail.gna.org/listinfo/libsecondlife-dev http://www.libsecondlife.org/
-- --Jesse _______________________________________________ libsecondlife-dev mailing list libsecondlife-dev@gna.org https://mail.gna.org/listinfo/libsecondlife-dev http://www.libsecondlife.org/
