
|
[haiku-appserver]
||
[Date Prev]
[05-2006 Date Index]
[Date Next]
||
[Thread Prev]
[05-2006 Thread Index]
[Thread Next]
[haiku-appserver] Re: BWindowScreen broken
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-appserver@xxxxxxxxxxxxx
- Date: Tue, 02 May 2006 21:55:08 +0200 CEST
Hi Rudolf,
"Rudolf" <drivers.be-hold@xxxxxxxxxxxx> wrote:
> Maybe a bit offtopic? Posting anyway, hope someone picks this up.
BWindowScreen probably needs app_server support, too, so... :-)
> BWindowScreen is currently broken.
> I investigated a bit:
> Turns out the drivername returned is the wrong one:
> The system comes up with graphics/vesa. On my system this should be
> graphics/10de_0324_010000.
>
> You get the picture ;-)
>
> I guess the search algorithm didn't take into account that there
> could
> be more than one driver in a system! (although here it's just one,
> plus
> the fallback vesa one)
There is no real search algorithm, though. Right now, only the first
usable driver will be opened. The method that is responsible currently
looks like:
status_t
AccelerantHWInterface::GetDriverPath(BString &string)
{
// TODO: hardcoded to vesa for now. Fix me
string = "graphics/vesa";
return B_OK;
}
I'll fixed it now if you don't mind, although I think BWindowScreen is
broken anyway - we'll see.
Bye,
Axel.
|

|