Announce: Material Skin

[SamY]

it did not require any action my part, it just updated on it's own through autoupdates

That's puzzling to me but, then again, a lot of things are. ;-)

The update still hasn't hit the servers yet but should any time now. In the meantime, I installed it from the zip file and the problem is indeed fixed.

A thought just occurred to me. Do you have an entry in "Additional Repositories" that would pick up the new version directly from Craig's Github page? That would explain things.

UPDATE: It just hit the server so everyone should be getting updated shortly.

[slartibartfast]

That's puzzling to me but, then again, a lot of things are. ;-)

The update still hasn't hit the servers yet but should any time now. In the meantime, I installed it from the zip file and the problem is indeed fixed.

A thought just occurred to me. Do you have an entry in "Additional Repositories" that would pick up the new version directly from Craig's Github page? That would explain things.

UPDATE: It just hit the server so everyone should be getting updated shortly.

Yup, the repository used to be in the first post.

https://raw.githubusercontent.com/CDrummond/lms-material/master/public.xml

Sent from my Pixel 3a using Tapatalk

[SlimChances]

That's puzzling to me but, then again, a lot of things are. ;-)

The update still hasn't hit the servers yet but should any time now. In the meantime, I installed it from the zip file and the problem is indeed fixed.

A thought just occurred to me. Do you have an entry in "Additional Repositories" that would pick up the new version directly from Craig's Github page? That would explain things.

UPDATE: It just hit the server so everyone should be getting updated shortly.

Yes you're right I do have it in 3rd party unsupported repositories

[d6jg]

Update has appeared via regular plugins route. Everything seems back to as it was. I don’t use Alarms so can’t comment on that implementation

Edit. I did have to clear Safari cache

[SamY]

Update, should be handled now. Clickable items don't wrap. But if this message is sent as text it should now wrap.

Hey, Craig. You may recall this change you made during v2.10.0 development that allowed menu text messages to wrap and I remember testing and verifying that it worked with the Denon menus. However, the change does not appear to be in the current v2.10.1 release as the messages are again being truncated. Was this something that slipped through the cracks or was it intentionally left out?

[SamY]

Yes you're right I do have it in 3rd party unsupported repositories

As opposed to unreported suppositories.

[cpd73]

Hey, Craig. You may recall this change you made during v2.10.0 development that allowed menu text messages to wrap and I remember testing and verifying that it worked with the Denon menus. However, the change does not appear to be in the current v2.10.1 release as the messages are again being truncated. Was this something that slipped through the cracks or was it intentionally left out?

Yeah, confirmed. Will fix for 2.10.2 to make sure its fixed for your scenario, can you send me the JSON RESP message that corresponds to the incorrect display? See my sig for details. This way I can hard-code that into my dev version, and see the actual results.

[Shozzer]

Have just seen this post. I saw another comment about clearing the cache and tried it myself and all seems to be working as expected now, thanks.

Did you clear the cache?

Sent from my Pixel 3a using Tapatalk

[SamY]

Yeah, confirmed. Will fix for 2.10.2 to make sure its fixed for your scenario, can you send me the JSON RESP message that corresponds to the incorrect display? See my sig for details. This way I can hard-code that into my dev version, and see the actual results.

Here it is. For testing purposes, I expanded the message so that it would be sure to wrap:

[2:40:46 PM] JSON RESP: {"result":{"offset":0,"item_loop":[{"text":"AVR menu not active for this player abcde fghij klmnop qrst uvwxyz","icon":"plugins/DenonAvpControl/html/images/denon_control.png"}],"count":1},"id":0,"method":"slim.request","params":["cc:cc:4c:51:85:cb",["avpTop","0","300"]]}

These messages are also used (and truncated) in the submenus. Here is one from the Reference Level menu:

[2:49:36 PM] JSON RESP: {"id":0,"params":["b8:26:eb:c1:71:f0",["avpRefLvl","0",300,"menu:avpRefLvl"]],"method":"slim.request","result":{"offset":0,"item_loop":[{"text":"Unavailable when in Direct or Pure Direct modes."}],"count":1}}

You indicated previously that you would ignore the 'icon' attribute used in the first example, which is fine. However, I would like to keep it there if possible as it is displayed by other clients.

Thanks.

[cpd73]

Here it is. For testing purposes, I expanded the message so that it would be sure to wrap:

Thanks, and this is now fixed for 2.10.2

You indicated previously that you would ignore the 'icon' attribute used in the first example, which is fine. However, I would like to keep it there if possible as it is displayed by other clients.

Well using an icon gives even less room for the text, plus what does it actually provide? Of your two examples only the first ("not supported here") has an icon, and the user already knows they entered this plugin so showing its icon again does not add much.

[SamY]

Thanks, and this is now fixed for 2.10.2

Thanks!

Well using an icon gives even less room for the text, plus what does it actually provide? Of your two examples only the first ("not supported here") has an icon, and the user already knows they entered this plugin so showing its icon again does not add much.

Good point. I may go ahead and remove it in the next release.

[Ron F.]

APK Screensaver

I am having a new problem with the screensaver feature in Material, Github: "Adjust screensaver text positions." Parent:374a98, which was pushed immediately after the release of 2.10.1.

The screensaver looks OK in various browsers such as Chrome, Brave, and Fully Kiosk, but it does not render well in the lms-material-app, tested in versions 2.0 and 2.1; the Time display is now too large and spills out over the edges on both sides. In my apk setup, I am having a conflict between the Interface settings->Font size and Application->Scale. It looks like the rendering for Time in the screensaver has gotten much larger.

I have now set Interface Font size to Regular, and I set the APK Application Scale to something that makes everything minus the screensaver look good, and for now I will just live with the over-sized screensaver Time display.

I am using a Pixel 3a, Android 12, and looking at Plugins/MaterialSkin/HTML/material/html/css/style.css, I figure I am now getting a screensaver font size of 64px for Time instead of 48px, which is probably what I used to get, although I don't understand why?

[slartibartfast]

I am having a new problem with the screensaver feature in Material, Github: "Adjust screensaver text positions." Parent:374a98, which was pushed immediately after the release of 2.10.1.

The screensaver looks OK in various browsers such as Chrome, Brave, and Fully Kiosk, but it does not render well in the lms-material-app, tested in versions 2.0 and 2.1; the Time display is now too large and spills out over the edges on both sides. In my apk setup, I am having a conflict between the Interface settings->Font size and Application->Scale. It looks like the rendering for Time in the screensaver has gotten much larger.

I have now set Interface Font size to Regular, and I set the APK Application Scale to something that makes everything minus the screensaver look good, and for now I will just live with the over-sized screensaver Time display.

I am using a Pixel 3a, Android 12, and looking at Plugins/MaterialSkin/HTML/material/html/css/style.css, I figure I am now getting a screensaver font size of 64px for Time instead of 48px, which is probably what I used to get, although I don't understand why?

It seems to me that with zoom set to near maximum the screensaver font is much larger in landscape than portrait mode. Is it landscape mode where you see the issue?

Sent from my Pixel 3a using Tapatalk

[hsmeets]

Hi,

not sure if this is really a Material issue, but I noticed it after the latest update (2.10.1), it worked before than. Maybe Michael who maintains the Qobuz plugin is reading along too in case...

Qobuz offers booklets to be viewed, however since the latest (or previous version) of Material the availability of the booklet is still shown as before but it is no longer shown as a link/url to the PDF on the Qobuz server.

[castalla]

Using Material on FiiO M6 - display problem

The FiiO M6 is a mini android music player using a modified version of android 7.

Using LMS apk gives a now playing screen which doesn't display the metadata image when the track changes - just the generic disc image.
Squeezer shows the track images.

(see attached pics - sorry for camera quality, but I can't discover how to take screenshots on the M6)

I may be mistaken but I think this may be a recent change following the updates to accommodate the alarm displays.

All other apps on the M6 work without issues.