> On Montag 10 September 2007, Hans Meine wrote:
>> On Montag 10 September 2007, Duncan Webb wrote:
>> > OVERSCAN_Y_TOP and OVERSCAN_Y_BOTTOM. Can't get much clearer than
>> that.
>>
>> Certainly better than _YT / _YB.
>
> ..oh, but forgot to say that this is still quite unusual. "Normal" would
>
On Montag 10 September 2007, Hans Meine wrote:
> On Montag 10 September 2007, Duncan Webb wrote:
> > OVERSCAN_Y_TOP and OVERSCAN_Y_BOTTOM. Can't get much clearer than that.
>
> Certainly better than _YT / _YB.
..oh, but forgot to say that this is still quite unusual. "Normal" would be
just OVER
On Montag 10 September 2007, Duncan Webb wrote:
> OVERSCAN_Y_TOP and OVERSCAN_Y_BOTTOM. Can't get much clearer than that.
Certainly better than _YT / _YB.
> The main problem with X,Y is where the origin is, some geometry systems it
> is bottom left and others it is top left. So where is Y1?
That'
> XL,XR, YT and YB make more sense to me. It's a short step to figure out
what they mean, making the variable name less cryptic.
>
> Of course, even less cryptic is OVERSCAN_X_LEFT, OVERSCAN_X_RIGHT,
OVERSCAN_Y_TOP and OVERSCAN_Y_BOTTOM. Can't get much clearer than that.
>
> Anyone else???
Agree
XL,XR, YT and YB make more sense to me. It's a short step to figure
out what they mean, making the variable name less cryptic.
Of course, even less cryptic is OVERSCAN_X_LEFT, OVERSCAN_X_RIGHT,
OVERSCAN_Y_TOP and OVERSCAN_Y_BOTTOM. Can't get much clearer than
that.
Anyone else???
--- Hans Mein
On Sonntag 09 September 2007, Duncan Webb wrote:
> Would you like to follow the instructions in the contributing section in
> the wiki? http://freevo.sourceforge.net/cgi-bin/doc/Contributing
>
> You may also like to change X1,X2 to XL,XR and Y1,Y2 to YT,YB to make it
> easier for set up. Where the
Pirlouwi wrote:
> Hello Stephen,
>
> I have the same problem at home, and I wrote for that a little patch for
> freevo 1.7.1, which I adapted to 1.7.3. Here it is (in attachment).
> Could you test it on your configuration?
>
> I think I discovered a little bug, which I already have corrected in m
Sorry,
I forgot to mention that the two variables defined inside local_conf.py :
OSD_OVERSCAN_X
OSD_OVERSCAN_Y
have to be replaced by:
OSD_OVERSCAN_X1
OSD_OVERSCAN_X2
OSD_OVERSCAN_Y1
OSD_OVERSCAN_Y2
X1 represents the screen left shift
X2 represents the screen right shift
Y1 represents the screen up
Hello Stephen,
I have the same problem at home, and I wrote for that a little patch for
freevo 1.7.1, which I adapted to 1.7.3. Here it is (in attachment). Could
you test it on your configuration?
I think I discovered a little bug, which I already have corrected in my
patch :
in /skins/main/xml_
