Display Size doesn't fit

[merryprankster02]

I went with a different display then the one you listed and while everything works great now from a code perspective, if i have the pi connected to a monitor or a tv when i plug it into the small screen/case that i had intended run this on, the display is too large and you can only see the direction one way and the otherway is cut off. I went into raspi-config and set the resolution to 800 x 480 which is what the manufacturer lists. This seems to work fine for the regular desktop but not the subway time output. Is there an easy way to resize the output so that it will fit this screen correctly or would it make more sense for me to get a different screen and use this one for a different project down the road. Any assistance will definitely help and i apologize for asking you my previous question about tkinter since it would have been irrelevant if i had atually been using the raspian os instead of a basic ubuntu installation.

[lightalan]

Hummm.... That's interesting. The subway clock should resize itself according to the monitor size. Unless there is something wrong in your config that's reporting back the wrong display size. You can try forcing your display size on lines 177 and 178 of subway.py and see what happens.

…

On Mon, Jan 27, 2020, 7:35 PM merryprankster02 ***@***.***> wrote: I went with a different display then the one you listed and while everything works great now from a code perspective, if i have the pi connected to a monitor or a tv when i plug it into the small screen/case that i had intended run this on, the display is too large and you can only see the direction one way and the otherway is cut off. I went into raspi-config and set the resolution to 800 x 480 which is what the manufacturer lists. This seems to work fine for the regular desktop but not the subway time output. Is there an easy way to resize the output so that it will fit this screen correctly or would it make more sense for me to get a different screen and use this one for a different project down the road. Any assistance will definitely help and i apologize for asking you my previous question about tkinter since it would have been irrelevant if i had atually been using the raspian os instead of a basic ubuntu installation. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#7?email_source=notifications&email_token=AK7LEU62PLOI3Q7BHBERM3TQ754WPA5CNFSM4KMKPI22YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IJCT3OA>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK7LEU6S5KM6D4Z3I2CULXLQ754WPANCNFSM4KMKPI2Q> .

[merryprankster02]

Ok, i will give that a shot a little later on this evening when i have some more time to play around with it. Thanks again for the quick reply. I will definitely try forcing the resolution in the code and see if that fixes it. Do you know what the resolution was of the screen that you used out of curiosity? This is the one that i went with https://www.amazon.com/gp/product/B07S82CN57?ref=ppx_pt2_dt_b_prod_image

As per its instructions that came with the screen, i installed a new driver prior to plugging it in and ran the following commands:

sudo rm rf LCD-show
git clone https://github.com/goodtft/LCD-show.git
chmod _R 755 LCD-show
cd LCS-show/
sudo ./LCS5-show

which then forced it to reboot. It was at this point that I noticed that there was a little tiny switch on the back of the board for the screen which I hadnt noticed and that was why the screen was black. Once i turned it on is when i noticed that it wasnt sized correctly so i rebooted again went into raspi-config and manually set the resolution there. Like i said this fixed the native desktop but the output is still off.

I will let you know what happens when i hard code in the resolution.

[lightalan]

The monitor I used was this one which is 1280x800. https://www.amazon.com/dp/B07FZZ95WN/ref=cm_sw_r_em_apa_i_Qn5lEb0RVM5WA

…

On Mon, Jan 27, 2020, 8:41 PM merryprankster02 ***@***.***> wrote: Ok, i will give that a shot a little later on this evening when i have some more time to play around with it. Thats again for the quick reply. I will definitely try forcing the resolution in the road and see if that fixes it. Do you know what the resolution was of the screen that you used out of curiosity. This is the one that i went with https://www.amazon.com/gp/product/B07S82CN57?ref=ppx_pt2_dt_b_prod_image As per its instructions i installed a new driver prior to plugging it in and ran the following commands: sudo rm rf LCD-show git clone https://github.com/goodtft/LCD-show.git chmod _R 755 LCD-show cd LCS-show/ sudo ./LCS5-show which then forced it to reboot. It was at this point that I noticed that there was a little tiny switch on the back of the board for the screen which I hadnt noticed and that was why the screen was black. Once i turned it on is when i noticed that it wasnt sized correctly so i rebooted again went into raspi-config and manually set the resolution there. Like i said this fixed the native desktop but the output is still off. I will let you know what happens when i hard code in the resolution. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7?email_source=notifications&email_token=AK7LEU4ZSFOHCF4SCZNERCDQ76EMLA5CNFSM4KMKPI22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKBXCEI#issuecomment-579039505>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK7LEU6LCVPF7YOGHROSVADQ76EMLANCNFSM4KMKPI2Q> .

[merryprankster02]

hmmm, so i tried to play around with this last night and tried several methods to force the resolution but none worked. I tried the raspi-config, within your code, and lastly i tried to override everything and set it fron within the boot config.txt file. WHen i did the last one i happened to be watching the screen during the reboot and I noticed that it stays with the new resolution for a majority of the boot but at one point you can literally see the font size changes as it scrolls through the boot instructions. After doings some research it appears that a lot of people seem to have similar issues when using the really small displays with rpi which have resolutions below less than 1280 x 800 which i believe is the fault for rpi. When i have some more time, I will see if i can find anyone who actually got this resolved completely but it is starting to look like i might want a different display. Again, thanks for all of your help with this project. If i end up getting a different screen, i might also try and see how this runs on a pi zero so i can use the pi4 for something for resource intensive.

…

On Mon, Jan 27, 2020 at 8:52 PM Alan Light ***@***.***> wrote: The monitor I used was this one which is 1280x800. https://www.amazon.com/dp/B07FZZ95WN/ref=cm_sw_r_em_apa_i_Qn5lEb0RVM5WA On Mon, Jan 27, 2020, 8:41 PM merryprankster02 ***@***.***> wrote: > Ok, i will give that a shot a little later on this evening when i have > some more time to play around with it. Thats again for the quick reply. I > will definitely try forcing the resolution in the road and see if that > fixes it. Do you know what the resolution was of the screen that you used > out of curiosity. This is the one that i went with > https://www.amazon.com/gp/product/B07S82CN57?ref=ppx_pt2_dt_b_prod_image > > As per its instructions i installed a new driver prior to plugging it in > and ran the following commands: > > sudo rm rf LCD-show > git clone https://github.com/goodtft/LCD-show.git > chmod _R 755 LCD-show > cd LCS-show/ > sudo ./LCS5-show > > which then forced it to reboot. It was at this point that I noticed that > there was a little tiny switch on the back of the board for the screen > which I hadnt noticed and that was why the screen was black. Once i turned > it on is when i noticed that it wasnt sized correctly so i rebooted again > went into raspi-config and manually set the resolution there. Like i said > this fixed the native desktop but the output is still off. > > I will let you know what happens when i hard code in the resolution. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > < #7?email_source=notifications&email_token=AK7LEU4ZSFOHCF4SCZNERCDQ76EMLA5CNFSM4KMKPI22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKBXCEI#issuecomment-579039505 >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AK7LEU6LCVPF7YOGHROSVADQ76EMLANCNFSM4KMKPI2Q > > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7?email_source=notifications&email_token=AOMCRTXE4ADNQI5H4FEFVUTQ76FULA5CNFSM4KMKPI22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKBXUWQ#issuecomment-579041882>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOMCRTUBTF2XJPB3YI5CG7LQ76FULANCNFSM4KMKPI2Q> .