Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vdr] Re: cOsd tArea explanation
After looking more, I find out that the returned error is:
"ERROR: cOsd::SetAreas returned 5"
5 -> oeWrongAlignment
But according to the CanHandleAreas (which is called by SetAreas),
oeWrongAlignment is returned when
Areas[i].x1 > Areas[i].x2 OR Areas[i].y1 > Areas[i].y2 OR Areas[i].x1 < 0 OR
Areas[i].y1 < 0
Nothing is related to the bpp value.... and x1,y1,x2 and y2 are all the
same...
(228 < 623 ok ... 50 < 99 ok ... 228 > 0 ok and 50 > 0 everything seems to
be allright...)
I really don't understant the mistake....
-----Message d'origine-----
De : vdr-bounce@linuxtv.org [mailto:vdr-bounce@linuxtv.org]De la part de
Maynard Cedric
Envoyé : jeudi 8 juillet 2004 19:28
À : vdr@linuxtv.org
Objet : [vdr] cOsd tArea explanation
Hi all,
Well, I'm fighting with those tArea and trying to understand why :
tArea Area = { 228, 50, 623, 99,2};
osd->SetAreas(&Area,1);
just work fine and why
tArea Area = { 228, 50, 623, 99,1};
osd->SetAreas(&Area,1);
Won't..
The main difference between the two is the number of color (right? 4 for the
first, only 2 for the second)
So why with less color this area won't show?? (and the CanHandleAreas()
return false obviously)...
If someone can explain me where I went wrong, I'll be thanksfull!!
Home |
Main Index |
Thread Index