PiBox » launcher

While there were a number of problems in how the calculations were done for each area of the launcher display, it turned out the real problem was with the monitor itself. It appears to not actually display to it's borders. If I move the same SD card to another monitor, and reset the pibox-config file to have the correct dimensions for that monitor, then the display works fine. The broken monitor advertises one size but doesn't actually display that size. It might be a monitor config option but so far I've not found a way to fix it via the monitor itself. Might be possible with overscanning settings in config.txt.

Updates are being made to the launcher to fix the computation problems.

libpibox needs a function that can be used to re-load the monitor dimensions via tvservice -s for the launcher (and any other app that needs it). That will be tracked as a separate issue. It's purpose it to allow an instance of PiBox to be moved to another monitor and it will just work.

Looks like libpibox already gets the proper fb0 size via piboxGetDisplaySize() using sysfs. However, the size of the display reported by tvservice -s is wrong. So I need to stop using that for getting display size and only use the sysfs.

This means that firstboot probably needs to change to get display size from sysfs like piboxGetDisplaySize() when generating pibox-config. And pibox-config should be updated on every boot because the display might change if they move the RPi around.

Note: it's also possible that I may need to choose the smaller of the virtual display size (via sysfs) and tvservice -s. For now, I'll just use sysfs with the caveat I may need to choose between them if sysfs doesn't just work on the various hardware I have.

This fix is specific to the init scripts for generating a proper pibox-config on each boot. If individual apps need updating (like to read sysfs directly via libpibox) then those issues will be tracked separately.

Changes tested, committed and pushed.

Closing issue.