808htfan wrote: 
> Thanks for working on this...
> 
> I need to be more specific about my problem:
> 
> That last step, where you tap/hold the '+' sign, I meant that tapping on
> the track name itself doesn't work to bring up the little pop-up menu
> (different, smaller one).  
> 
> BTW, I have Preferences-->Controls-->Default Play Action: set to Always
> Ask.
> 
> Also, if I hold the '+' sign instead of the track name, things work the
> same as in your video.
> 
> Thanks

Not sure if you've noticed, but the items in the pop-up when a song is
playing is different from when it's not playing.  That's because when
it's not playing, the pop-up is generated by the app, while it is
generated by the server when it is playing (the option to show a pop-up
when something is already playing was added to LMS either in 7.8 or
7.9).  Basically, when the app sees that the command that will be sent
to the server will generate a pop-up, it will not create it's own.

This is important because the problem you're encountering used to be a
bug on the server. Apparently, in the initial version of this feature,
when an app requests a list of songs from the server, the server can
only generate that pop-up on the items in that initial request.  If the
app then requests more items (to do incremental loading for example),
the server will fail to generate the pop-up for the additional items and
just not respond. I remember I had confirmed this on the controller of
the Squeezebox Duet. If you browse a list of songs with more than 200
items, the pop-up will not work for the 201st item onward (the initial
request size of the Squeezebox UI is 200 items). 

Originally, Squeeze Ctrl will initially load 48 items and then
incrementally load the rest as you browse.  When this problem showed up
it either LMS 7.8 or 7.9, I changed the initial request size to 200 to
minimize the problem. Then when Android 7.0 (Nougat) came around Squeeze
Ctrl started crashing when you switched apps, because an app error that
older versions of Android used to ignore will now crash the app. 
Basically, Squeeze Ctrl was trying to save too much to memory when it
went into the background.  To fix the crashing, I tried different
methods, one of them being changing the initial load size to 20.
Ultimately, I don't think that made a difference to the crashing, but I
must have forgotten to change it back to 200.

It seems that they did eventually fix the problem in LMS, but Squeeze
Ctrl needs to be changed to use the fix. I'll do that in the next
update, but in the meantime, if you are using a software player or the
Squeezebox Touch, you can go into the LMS Settings > Player > Basic
Settings and change "Defeat destructive Touch-To-Play" to "do not
defeat". This will let Squeeze Ctrl show it's own pop-up.  That setting
doesn't show up for the Boom, Receiver, or the Transporter (not sure
about the Radio).



--------------
Squeezebox apps for webOS, Android and Windows Phone,
http://www.angrygoatapps.com
------------------------------------------------------------------------
wt0's Profile: http://forums.slimdevices.com/member.php?userid=18760
View this thread: http://forums.slimdevices.com/showthread.php?t=96757

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to