[senna99]

Actually think I've solved this.

Solution for future reference: Calling ReloadSkin() will force the skin settings to save to file.

I also use the ReloadSkin(), because it's now the only way to save data.
But still remains a problem with new engine, for example I have a lot trouble with Skin.SetString and AlarmClock(name,command,time[,silent,loop])
Frankly I do not know why

[Mike_Doc]

From what I know Alarmclock doesn't work in Jarvis. My skin was experiencing lots of crashes by users with Jarvis betas and with the help of BobCratchet it was found that after commenting out the various Alarmclocks that the crashing / freezing stopped. But it could also still be a skin issue and the use of Alamclock as well?

[senna99]

From what I know Alarmclock doesn't work in Jarvis. My skin was experiencing lots of crashes by users with Jarvis betas and with the help of BobCratchet it was found that after commenting out the various Alarmclocks that the crashing / freezing stopped. But it could also still be a skin issue and the use of Alamclock as well?

Thanks, Mike_Doc for the information.
Now I can put my project xone in trash or to start all from the beginning.

[sualfred]

I use Alarmclocks on Jarvis and they work?

[ronie]

debug logs?
crash logs?
skin code?
steps to reproduce?

[senna99]

debug logs?
crash logs?
skin code?
steps to reproduce?

HI, ronie

I did not think anything bad about, new kodi engine.
I will not bother with my project, anyway I need to upgrade skin codes.
Codes are two years old for sure and skin require a change.

Best regards

[BobCratchett]

http://trac.kodi.tv/ticket/16415 <- Ticket created when the MadNox hangs were first traced back to the AlarmClocks

[User 224999]

From what I know Alarmclock doesn't work in Jarvis. My skin was experiencing lots of crashes by users with Jarvis betas and with the help of BobCratchet it was found that after commenting out the various Alarmclocks that the crashing / freezing stopped. But it could also still be a skin issue and the use of Alamclock as well?

You need to put your alarmclocks as onfocus actions on a button.
The crashing will occur if you put them directly in the onload tags.

Found this out too myself the hard way...

So, something like this:

<window>
<defaultcontrol always="true">1000</defaultcontrol>
<controls>
<control type="button" id="1000">
<description>hidden button for onload actions as placing them in onload causes strange behaviour</description>
<onfocus>AlarmClock(SpotlightWidgetRotate,Control.Move(1508,1),00:20,silent,loop)</onfocus>
<onfocus>SetFocus(300)</onfocus>
<texturenofocus>-</texturenofocus>
<texturefocus>-</texturefocus>
<visible allowhiddenfocus="true">false</visible>
</control>