2015-09-13, 17:13
(2015-09-12, 06:03)tomer953 Wrote: 1) Oh, Contextmenu button... - that was hidden... I think its better to move it to somewhere else from contextmenu in the "choose theme" dialog - its not the obvious place to export theme to zip...
so about that: no way to let user load from ".theme" file directly? ill just tell them pass the ".theme" files between them, or - make the "createcolortheme" let you choose if you want to export to zip
2) I made a changes in the skinshortcuts, refreshed, created backup, restore shortcuts to default, tried to restore my backup - and nothing.
right now I tried to do it again but in the restore I get error during some unicoded path file, I'm providing log in the next line....
3) mm this is the log http://pastebin.com/fq1U5UTc but I think this one will be more useful: http://pastebin.com/CWhykTQ4 - those are the reason that script failes, actually I don't use them anymore, In the past I set them from skinshosrtcuts dialog background picker to test and fix some unicode errors overthere, so they are causing the problem. If it hard to you to fix, I'll fix it in the next few days.
and just checking - are you pushing updates of the helper to the official repo? you changed the version to 0.0.4 and I auto-get it somehow, I wondered If you did it...
1) I tried to use as less additional dialogs as possible. So the dialog used for the skinthemes is just the default DialogSelect.xml in your skin.
The export button is a bit more advanced so I decoded to "hide" it under the contextmenu. What I can do is specify an additional button that you can include in your skin if you want.
2) This should be fixed whenever problem 3 is fixed.
3) OK, I think/hope I've finally nalied the unicode issues but I can't test (as I don't have any unicode paths/settings) so please test again with latest Git version.
If it still fails I will extend my testsetup with some fake paths with some unicode characters in it.
4) I am updating the script on my beta repo. The script isn't yet released to official repo yet. As soon as the current features are stable and the unicode issues are fixed I will submit it to the repo.
