"RokuKC" wrote:
"EnTerr" wrote:
Actually, "FHD" is 1080 and the 4k is "UHD" - no?
Not in this case. Graphics resolution supporting FHD is synonymous with video resolution supporting 4K, at this time.
I don't recommend making tests based on model number, as that will not work right later if not sooner. :wink:
Um, wait... "everybody knows" that HD is 720,
FHD is 1080 and UHD is 1920 vertically - are you saying that 3840x1920 gets mis-labeled as FHD?
If so, wouldn't checking for
.height number be a better idea than the
.name string? I mean, at least the number 1920 or 1080 should be correct, right?
And regarding checking by model# - no need to carve the recognized models in stone, could provision the app with a regex that decides based on model# (i.e. `createObject("roRegEx", is_4k_model_ptrn, "").isMatch(model_no)`). It requires some sophistication of periodic provisioning from central server - but for those who have done it for other reasons - okay, that's just another key for the JSON property bag and when the Co releases a new model, tweak a file on the server and stay merry. E.g.
{..., is_4k_model: "^44", ... }
' oh noes, they released 4k model 6xxx, what we gonna do? ah okay: '
{..., is_4k_model: "^4[4-9]|^6", ... }