mherger wrote: > Not easily. But if you enable debug logging for control.command, then > you'd see what is being used internally. A Spotty search would result in > this: > > > Code: -------------------- > > [18-07-03 06:59:00.1751] Slim::Control::Request::dump (2339) Request: Query [99:99:99:99:99->spotty items] from /abcd/slim/request|17||abcd (Dispatchable) > [18-07-03 06:59:00.1753] Slim::Control::Request::dump (2341) Param: [search] = [here comes your search term] > [18-07-03 06:59:00.1755] Slim::Control::Request::dump (2341) Param: [useContextMenu] = [1] > [18-07-03 06:59:00.1756] Slim::Control::Request::dump (2341) Param: [_index] = [0] > [18-07-03 06:59:00.1757] Slim::Control::Request::dump (2341) Param: [menu] = [spotty] > [18-07-03 06:59:00.1758] Slim::Control::Request::dump (2341) Param: [item_id] = [0.0] > [18-07-03 06:59:00.1761] Slim::Control::Request::dump (2341) Param: [_quantity] = [200] > -------------------- > > > > Those items are "indexed" by the navigation tree. 0.0 would be the > first menu item's sub-menu - which is search. But that would return > you a menu again.... > > If you were implementing LMS side code, then you could probably call > Spotty code directly - ugly, but possible.
Thanks for this. I will review and see if I can make something like this work. Otherwise I may setup a direct query to spotify and queue the resulting urls directly. Ynot ------------------------------------------------------------------------ ynot1234567890's Profile: http://forums.slimdevices.com/member.php?userid=66569 View this thread: http://forums.slimdevices.com/showthread.php?t=108898 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
