06-12-2023, 08:41 PM (This post was last modified: 06-12-2023, 08:42 PM by Nutul.)
Hi all,
updated yesterday to the 8.3.3, restarted, everything was OK.
Then today I had to restart the local UI to clear the browser's cache, and all of a sudden I no longer see the alphabetical indexes (in the TAG view, but they could also be missing from the ALBUM view, didn't check...). Probably this has also cleared some cached CSS (I cannot explain it otherwise).
@Tim Curtis
I seem to remember this already happened a while ago (maybe with 8.3.2, or 8.3.1?) and "we" fixed it... ;-)
Can you comment?
In a quick test, I was unable to repro the "missing alpha-indexes" on my moOde 8.3.3 player with Raspberry Pi 7" touchscreen after restarting the Local UI. This was on a fresh 8.3.3 image, not an in-place update from 8.3.2.
weird enough, I am testing it on my browser in developer mode. If I define the screen (with square pixel, as I use it) as 799 x 443 the indices don't show. If I define it as 800 x 444 they do.
The viewport, IMO is indeed 800 x 444 (while maxX and maxY are respectively 799 and 443)...
06-13-2023, 11:04 AM (This post was last modified: 06-13-2023, 11:05 AM by Tim Curtis.
Edit Reason: eta
)
To get the viewport size use the real screen and the setting below. Menu, Refresh after each change.
# Toggle viewport notification on/off
Code:
pi@moode:~ $ moodeutl -q "update cfg_system set value='viewport' where param='pkgid_suffix'"
pi@moode:~ $ moodeutl -q "update cfg_system set value='' where param='pkgid_suffix'"
(06-13-2023, 11:04 AM)Tim Curtis Wrote: To get the viewport size use the real screen and the setting below. Menu, Refresh after each change.
# Toggle viewport notification on/off
Code:
pi@moode:~ $ moodeutl -q "update cfg_system set value='viewport' where param='pkgid_suffix'"
pi@moode:~ $ moodeutl -q "update cfg_system set value='' where param='pkgid_suffix'"
06-14-2023, 11:54 AM (This post was last modified: 06-14-2023, 11:59 AM by Nutul.)
(06-14-2023, 11:41 AM)TheOldPresbyope Wrote: That's not what I get on my "official" 7-in Touch.
Odd to see an "off by one" error here.
Regards,
Kent
I'm using "square" pixel mode, don't know if that makes any difference... maybe I'll try in both modes later today.
Anyway, I am more keen to understand a 800 pixels wide viewport (min x = 0, max x = 799), rather than a 799-wide one...
Maybe something changed in the browser? older versions returned maxX / maxY instead? I cannot comment, as this is the very first time I use the "show viewport" thing.
(06-14-2023, 11:41 AM)TheOldPresbyope Wrote: That's not what I get on my "official" 7-in Touch.
Odd to see an "off by one" error here.
Regards,
Kent
I'm using "square" pixel mode, don't know if that makes any difference... maybe I'll try in both modes later today.
Anyway, I am more keen to understand a 800 pixels wide viewport (min x = 0, max x = 799), rather than a 799-wide one...
Maybe something changed in the browser? older versions returned maxX / maxY instead? I cannot comment, as this is the very first time I use the "show viewport" thing.
Quick test with a Pi 7" Touch and the viewport popup shows the following:
Pixel aspect ratio
- Default 799 x 479
- Square 799 x 443
AFAIK viewport is 0-based so an 800px wide screen with pixel ratio = 1 and no Browser zoom would have a viewport max width of 799px.
I'm not sure what could be causing viewport width to show 800px on your end.