Posts: 995
Joined: Apr 2009
Reputation:
60
nessus
Skilled Skinner
Posts: 995
After reading my EDIT i see now that is the same thing with my last question (same menus across skins). Sorry... my English sucks !!!
Let me try again. If i am changing skins and i don't want to use the same structure and items i can have the current skin's menus by resetting the shortcuts.
So... can this be avoided and/or can i do it by one reset click for all menus (main menu and submenus) because for the submenus you need to reset one by one if you want to reset all of them.
So to make sure i express this correctly:
A. Change skins and keep the same main menu, submenus, widgets etc even if the user resets shortcuts
B. Change skins and reset from one click/button/option the main menu, submenus, widgets etc to current skin's defaults.
Cheers
Nessus
removed151214
Unregistered
removed151214
Unregistered
Posts: N/A
I appear to have removed the obvious references to it when cleaning up the documentation (there's such a thing as too clean!) - I'll restore them at the weekend.
You can give the user the choice to reset all the menus to the skins defaults by including a button with:
<onclick>RunScript(script.skinshortcuts?type=resetall)</onclick>
(Just to be clear, not that it should affect anything, this deletes (if the user agrees to it) everything in the scripts addon data directory, even if the DATA.xml/.shortcuts file isn't part of the current menu)
removed151214
Unregistered
removed151214
Unregistered
Posts: N/A
From a quick look that looks correct - the automatically generated labelID should be 31002, and the submenuVisibility is that, only specified as a number.
Is it actually causing a problem, such as the submenu not showing?
removed151214
Unregistered
removed151214
Unregistered
Posts: N/A
OK, please send me all your .DATA.xml files and your script-skinshortcuts-includes.xml file. I'll try to take a look this evening though, if its a complex issue, I'll finish looking tomorrow
Edit: Thanks for the files. I've tested your script-skinshortcuts-includes.xml (with a search-and-replace on the profile name for the first user - nessus) and all the items are showing for me with their relevant submenu, so I'm going to need some more time with this. I'll let you know when I've got something
Edit 2: I've been unable to recreate this problem, but I'll push an update to how the submenuVisibility is generated this weekend (or sooner, if I get time) which should clear up whatever's the underlying issue.
removed151214
Unregistered
removed151214
Unregistered
Posts: N/A
(2014-08-20, 20:21)TechnoTuup Wrote: I keep getting the error stating: Skin Shortcuts - Unable to build menu
I already reinstalled xbmc 13.2 final but that does not change anything. What must I do to fix this issue?
It looks like you've found a bug, so there's not much you can do directly - but you can help track it down by posting a full
debug log (wiki) somewhere like xbmclogs.com and pasting a link to it here (please don't paste the full log here
)
It's even easier than said in the link above if you have the XBMC Log Uploader script installed - when the menu fails to build the script will take care of enabling debug logging and calling the log uploader script - just note down the URL it gives you and paste it here.
You've caught me on a busy week, so once the log is uploaded I'll look into this over the weekend.
Posts: 10
Joined: Aug 2014
Reputation:
0
Can you tell me where I can find that url? XBMC Log Uploader only states that the log is uploaded to xbmclogs.com. In the log file in APPDATA I do not see any url as well.
removed151214
Unregistered
removed151214
Unregistered
Posts: N/A
The log uploader will display onscreen the URL it has uploaded to, or you can put an email address in the log uploaders settings and it will email you the link. Or manually upload via the instructions on the
debug log (wiki) wiki page.
removed151214
Unregistered
removed151214
Unregistered
Posts: N/A
It looks like it, which is why I'll change the submenu visibility property to not use the labelID this weekend (or sooner if time allows) - hopefully it'll all work as intended afterwards *crosses fingers*
removed151214
Unregistered
removed151214
Unregistered
Posts: N/A
@
nessus, could you try the
latest git version, and let me know if it works? Cheers.