Results 8,711 to 8,720 of 8999
Thread: Announce: Material Skin
-
2022-07-06, 05:25 #8711
- Join Date
- Jan 2010
- Location
- Hertfordshire
- Posts
- 9,285
-
2022-07-06, 05:43 #8712
- Join Date
- Mar 2017
- Posts
- 3,631
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.
-
2022-07-06, 08:17 #8713
- Join Date
- Feb 2010
- Posts
- 382
Thank you. Much appreciated!
I'm not sure I understand this because the web interface does what I am looking for (displaying the comment without needing to click anything) but Material Skin does not. Would it be possible for Material skin to behave like the web interface does in this respect?
Thanks for your consideration,
Mike
-
2022-07-06, 08:52 #8714
- Join Date
- Mar 2017
- Posts
- 3,631
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.
-
2022-07-06, 11:09 #8715
- Join Date
- Jan 2020
- Posts
- 80
I am not sure where the correct place to ask this question is, so please let me know if I should ask this elsewhere.
I would like to use the IR Blaster plugin with my SB Touch. After installing it , I was greeted with a blank plugin page. Only after I changed from Material Skin to Default Skin was the plugin page visible. Is this something on the Material skin side or on the plugin side, and can that be resolved ?
I am running:
LMS Version: 8.3.0 - 1655802730
Material Skin 2.9.8
IR-Blaster 6.2.2Last edited by justjason; 2022-07-06 at 11:14.
-
2022-07-06, 11:22 #8716
- Join Date
- Feb 2010
- Posts
- 382
-
2022-07-06, 11:26 #8717
- Join Date
- Mar 2017
- Posts
- 3,631
I've installed this plugin, but it does not show at all for me - not in Default or Material, no entries whatsoever. Perhaps its because I don't have the correct hardware.
Anyhow, looking at your screenshots this would appear to not be a Material issue. The page that you are showing from Material is actually from LMS's "Classic" (not "Default") skin. Material uses the "Classic" skin for server settings, extra platyer settings, and "Extras". Your "IRBlaster" is from a page within "Player Settings", so this is all from LMS. All Material does is add some CSS (and a little Javascript) to the "Classic" skin to make it appear slightly more Material-like. You should be able to see the same issue if you use the "Classic" skin - eg. "h t t p://SERVER:90090/Classic"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.
-
2022-07-06, 11:28 #8718
- Join Date
- Mar 2017
- Posts
- 3,631
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.
-
2022-07-06, 12:55 #8719
- Join Date
- Jan 2020
- Posts
- 80
Trying the .../classic url , I end up with an interesting Frankenstein, but changing over in Interface Settings to Classic I do see the same behavior - ie no plugin page. What would the Default page be building from ?
Yeah, It would only work for Touch, SB 2/3 and Transporter (I think)
Does this mean that the issue is on the plugin side ?
-
2022-07-06, 23:42 #8720
- Join Date
- Mar 2017
- Posts
- 3,631
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.