Announce: Material Skin

[cpd73]

I entered search then performed a search.

Just confirming... This shows Material fetching the list with the search input field, you then typed "Flaming lips", and Material fetched the search results. Now are you saying you go back from this list of search results? And the list shown when you go back needs to be refreshed?

There was no response at all when clicking back.

There won't be - Material keeps the list in memory and just reloads that. This is where the issue is, as in certain circumstances the list needs to be reloaded.

[slartibartfast]

Just confirming... This shows Material fetching the list with the search input field, you then typed "Flaming lips", and Material fetched the search results. Now are you saying you go back from this list of search results? And the list shown when you go back needs to be refreshed?



There won't be - Material keeps the list in memory and just reloads that. This is where the issue is, as in certain circumstances the list needs to be reloaded.

Yes when you return from the search results to the main search page you see a list of previous searches and this doesn't get updated with the latest search.

Sent from my Pixel 3a using Tapatalk

[cpd73]

I entered search then performed a search. There was no response at all when clicking back.

The attached log does not contain all of the response. If you look in your browser's console tab you will see they end with "..." - clicking that should expand to show all contents. I'm hoping in the search response it details what to do when back is pressed. Can you post the full log? Thanks.

[slartibartfast]

The attached log does not contain all of the response. If you look in your browser's console tab you will see they end with "..." - clicking that should expand to show all contents. I'm hoping in the search response it details what to do when back is pressed. Can you post the full log? Thanks.

Hope this is better.

[cpd73]

Hope this is better.

Thanks, that seems to have everything. Unfortunately, I see nothing that tells me the list should be refreshed on going back I could add a hack where if the command is "spotty items item_id:1.0 search:XXXX" that it refreshes on back, but that would be fragile and spotty specific. Hmm....

[slartibartfast]

Thanks, that seems to have everything. Unfortunately, I see nothing that tells me the list should be refreshed on going back I could add a hack where if the command is "spotty items item_id:1.0 search:XXXX" that it refreshes on back, but that would be fragile and spotty specific. Hmm....

Well it doesn't update in the default skin either unless you click "search". There is no "back" function in default skin, just in the browser.

Sent from my Pixel 3a using Tapatalk

[cpd73]

Well it doesn't update in the default skin either unless you click "search". There is no "back" function in default skin, just in the browser.

What do other control points do? e.g. iPeng, Squeezer, SqueezeCtrl, SB Radio?

[mherger]

Announce: Material Skin

> slartibartfast wrote:
>> Well it doesn't update in the default skin either unless you click
>> "search". There is no "back" function in default skin, just in the
>> browser.
>
> What do other control points do? e.g. iPeng, Squeezer, SqueezeCtrl, SB
> Radio?

As I mentioned a few postings up, this indeed is broken in Spotty (or
rather: not implemented). There's no refresh.

Would you have the refresh implemented if the data requested it?

[cpd73]

Would you have the refresh implemented if the data requested it?

Material already marks parts of its 'history' as needing to be refreshed. e.g. if a user was looking at the contents of a playlist, and the queue was saved as a playlist, when navigating back out of the playlist the list of playlists is refreshed (so that the newly saved playlist is shown). So, code is there to handle it, I'd just need to know that pressing item X in a list will imply the list itself needs to be refreshed when reloaded (i.e. go back).

[PasTim]

Should be.

Sent from my Pixel 3a using Tapatalk

Strange. I live in the same county, but F-Droid still shows version 0.1.4 (Android 10). I'm in no rush at all, but it seems a bit strange.

[slartibartfast]

Strange. I live in the same county, but F-Droid still shows version 0.1.4 (Android 10). I'm in no rush at all, but it seems a bit strange.

I originally had the version from GitHub and actually uninstalled that and reinstalled from F-Droid to make sure it was definitely there. It claims to have been there for 4 days now. Very strange. I will see what happens when the next update arrives although they are few and far between for the APK.

Sent from my Pixel 3a using Tapatalk

[Jaca]

I originally had the version from GitHub and actually uninstalled that and reinstalled from F-Droid to make sure it was definitely there. It claims to have been there for 4 days now. Very strange. I will see what happens when the next update arrives although they are few and far between for the APK.

Sent from my Pixel 3a using Tapatalk

I also had this problem before when LMS apk was originally installed from GitHub, F-Droid won't show any updates.. Unistalling and installing from F-Droid solved it..

[cpd73]

I also had this problem before when LMS apk was originally installed from GitHub, F-Droid won't show any updates.. Unistalling and installing from F-Droid solved it..

As they are signed with different keys you cannot update one from the other.

[PasTim]

As they are signed with different keys you cannot update one from the other.

I don't recall how I installed it originally. Still, I just uninstalled it with F-Droid, and reinstalled it, and it's still 0.1.4. Never mind, for now at least.

[carsten_h]

[*] Add 'Default player' setting[*] Add 'Only control default' setting

Hello!

If I am setting a default player und switching on "Only control default" the app (installed as apk from your site) crashes directly after start. I am not able to get it to work then. I have to uninstall it and install it again afterwards.

...This seems to only happen on my old Fire HD 8 (7th Generation) with Fire OS 5.6.8.0 (Android 5.1).
With a Fire HD 10 (9th Generation) with Fire OS 7.3.1.7 (Android 9) it is working without a problem!