"kdf" <[EMAIL PROTECTED]> wrote: > many thanks :) > deffo readable now. I'm a bit surprised on this one. it really does look > like > the server is just jumping to a different player. Which skin is being > used > here? Its a bit of a leap guess, but if a skin were to be refreshing at > the > time of a song change, and passing the player object improperly at that > time, > it could theoretically send the command to the 'default' player instead of > the > intended one.
> for example, there was an issue (recently fixed) with the handheld skin > that > would restart songs on a manual refresh of the page. I'm thinking this > could be > caused by something similar. The skin is Fishbone, but I'm not convinced that a browser (or the Slim UI) has been up in all cases where the problem has happened. I run SS as a service on W2K3 and usually don't leave the UI up anywhere. It's possible, though. I just moved from one SB to two, and I'm seeing a behavior I didn't expect and want to make sure it's not related to this problem. SS has always maintained some persistent state info that makes menu selections sticky. If I go from the top-level menu through Browse Music > Browse Artists, I'm taken directly back to the Artist item that I most recently navigated through. Are these sticky selections supposed to be global, or are they per device? I'm seeing them as global such that if I pick an artist on one SB and then navigate through the same menus on the other device, the first devices previous menu selections are showing up on the second. Is this by design? _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
