> > I thought I understood for a moment :-), but... I *am* using > > BBitmaps > > in libstorage. MimeDatabase::GetIconData(), which is called by > > BMimeType::SetIcon(), creates a temporary BBitmap that it uses for > > color conversions. Granted, SetIcon() is being called by > > libstoragetest, but it's still sitting in libstorage, which is still > > linked to libopenbeos. You're right, the confusion is nearing > > perfection. :-) > > Let's try again. :-) > (R5::)BBitmap needs a connection to the R5::app_server and therefore > an > R5::BApplication object, or more precisely a valid libbe::be_app. > libstoragetest is not linked against libopenbeos and thus a > BApplication created in it is an R5::BApplication that initializes > libbe::be_app. That's completely sufficient. It doesn't matter whether > or not the image (libstorage in this case) containing the code that > uses BBitmap is linked against libopenbeos, for BBitmap lives in libbe > and thus any functions/variables accessed by BBitmap code are searched > only in libbe and whatever libbe is linked against (libroot). > > As soon as the entity that creates the BApplication object is linked > against libopenbeos (before libbe), OBOS::BApplication will be used > and > R5::BBitmap must be left alone. This holds for the registrar for > instance. Got it. Thanks. :-) -Tyler