descriptions and look for any conflicts. I checked logs and nothing
jumped out. There was a comment:
Code:
--------------------
[22-02-11 18:41:20.7302]
Slim::Plugin::DontStopTheMusic::Plugin::onPlaylistChange (183) Found Sugarcube
active - I'm not going to interfere with it.
--------------------
...
So again, I'm not sure if this is a DSTM request or should be a
SugarCube request, but these plugins do not play nicely with each other
and don't warn the user, either in the UI settings pages or the logs,
when the are conflicting.
Well... the above is exactly the hint you are asking for, isn't it?
I'd recommend that at the top of the screen of the DSTM plugin, if
SugarCube is detected (which it can see because it adds SugarCube as an
option in DSTM which is very surprising), a warning that SugarCube is
installed and must be disabled at the Player level for DSTM to work.
That's up to SugarCube to do: the plugin can tell DSTM that it should
not kick in while the plugin (SugarCube) was active. DSTM then asks the
plugin whether it was active or not. If it says it was active, DSTM
would not kick in, but log the above.
So if SugarCube wasn't really active (and you were expecting DSTM to
kick in), but DSTM believed it was, then it's due to SugarCube telling so.
And if the user does not properly disable, then in the logs, preferably
at the Error or Warn level, it says the specific player couldn't run
DSTM because SugarCube is enabled.
It is a warning.
BTW: are you sure you're running the latest of "everything" (LMS &
SugarCube)? There was a change to this check about 6 months ago. And
given the line number in your log I must assume LMS is from before that
change.
_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
