rgdawson wrote: > Ha, well, I looked pretty hard, but figured I was too ignorant to figure > it out. I was hoping I could just execute a Javascript function from > within my app and return a variable, like toolbar.nowPlayingExpanded or > something, but I could not make such a thing work. I don't need it > persisted by Material if I can somehow figure it out. If I can do that, > then I can persist it myself and pass action=expandNowPlaying/true as > needed when I start up. And then if I can do that, I can remove a user > setting from my app, which would no longer be needed. > > Greg
If you are injecting JS into Material, you should be able to access its variables so the following -might- work: Code: -------------------- bus.$on('nowPlayingExpanded', function(expanded) { // Save value of expanded }); -------------------- *Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here. ------------------------------------------------------------------------ cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=109624 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins