You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using pi3d on a raspi that uses overscan the code is rendered outside of the window. Is it possible to read the .config file and account for the overscan so it renders in the right place?
The text was updated successfully, but these errors were encountered:
I would have thought it was possible to read and parse the config file.
Can you get the pi3d image in the 'right' place by hand tweaking the
values of x,y,w,h in the Display.create method? If so then you will be
able to write a python program to do the same. I will have a look at
this tomorrow (though I don't know if I can make my monitors need an
overscan adjustment)
Paddy
On 20/05/2013 02:30, Sdd18 wrote:
When using pi3d on a raspi that uses overscan the code is rendered
outside of the window. Is it possible to read the .config file and
account for the overscan so it renders in the right place?
—
Reply to this email directly or view it on GitHub #140.
Sdd18, Presuming you mean 'graphical display' rather than 'code'; It does seem to be easy enough to parse the /boot/config.txt file and find the overscan_left etc values. There is bit of a quirk in that the DISPLAY.max_width and DISPLAY.may_height values can only be accessed after you have created the display so you would have to do that, check the overscan values then DISPLAY.resize(x, y, w, h) with the values you calculate. If you can manage with the same overscan values for opposite edges then you can just use x and y values for the original DISPLAY.create and it will put equal margins on opposite edges - I'm not sure whether we should build this code into the Display class or not.
When using pi3d on a raspi that uses overscan the code is rendered outside of the window. Is it possible to read the .config file and account for the overscan so it renders in the right place?
The text was updated successfully, but these errors were encountered: