
|
[haiku-appserver]
||
[Date Prev]
[11-2004 Date Index]
[Date Next]
||
[Thread Prev]
[11-2004 Thread Index]
[Thread Next]
[haiku-appserver] Re: fontserver issues
- From: Adi Oanca <adioanca@xxxxxxxxxxxxx>
- To: haiku-appserver@xxxxxxxxxxxxx
- Date: Mon, 22 Nov 2004 19:24:59 +0200
DarkWyrm wrote:
>>>1) In my development setup, I've got libappserver building as a >
>>>static
>>>library ATM and linking it into the app_server and Appearance
>>>2) FontServer.h/cpp declares a global FontServer *fontserver
>>>3) Appearance allocates an object to it.
>>>4) Appearance loads a decorator
>>>5) Decorator references the fontserver object (as defined in
>>>libappserver) and segfaults
>>
>>Well, first of all, I don't think you should do that. FontServer is a
>>server object afterall, and it's even a private class (at least, from
>
> what I understand looking at the code/headers). So why not use BFont,
> which is the libbe class which interfaces with the font server ?
>
>>Is there any reason why BFont isn't enough for you?
>
> Most definitely. The app_server decorators, being primarily server
> objects, depend on services provided directly by the app_server.
> Decorators make graphics calls by making use of the system's
> DisplayDriver. DisplayDriver depends on having an allocated FontServer
> instance. Appearance emulates certain services provided by the
> app_server in order to provide previews of the decorator in the current
> color set. Anyway, the solution hit me while I was lying in bed last
> night, trying to go to sleep. I got everything to build and work
> properly (obligatory screenshot attached), so I will be continuing my
> fixes and check them in later today.
What about implementing the decorator presented in Stubear's mockup? :-D
bye,
Adi.
|

|