Setting padding via API?

[stuckless]

Yeah, I'm ready to throw in the towel now Basically, there are some aspects of the sage api that cannot be serialized, and it's cases like this. Likely sagetv will not apply the padding without first requesting some confirmation from the user. In this case, sagetv is realizing that it cannot do this without affecting something else. i don't know what the specific message is, just that when you see that kind of reply, that is what is happening.

[syrel]

Is the fact that it needs user input why it is possible to set padding via the webserver?
thanks for your efforts

syrel

[stuckless]

Originally Posted by syrel

Is the fact that it needs user input why it is possible to set padding via the webserver?
thanks for your efforts

syrel

I'm only guessing that it is somehow trying to get the user's attention, based on the fact that it is returning an AsyncTask. Maybe if Jeff is reading this, he can explain what is happening, and potentially what I could be doing to handle it in the REST APIs.

[syrel]

I'm still not giving up on this, even though I have no idea what I'm doing

Could I potentially create a custom service for SetRecordingTimes in a js file, and then call the service?

syrel

[stuckless]

Originally Posted by syrel

I'm still not giving up on this, even though I have no idea what I'm doing

Could I potentially create a custom service for SetRecordingTimes in a js file, and then call the service?

syrel

Unfortunately, no, but I looking into how to handle AsyncTaskID responses in the REST API. This will likely require a new SageTV version, but, I should be able to handle it. I can't really say when it will be done either

[syrel]

Ah, ok. I wondered that because I'm trying to work out how the webui does it to see if I can mimic it. The post command sent by the webui is
10.0.0.21:8080/command=SetRecPad&AiringId=15096519&returnto=%2Fsage%2FDetailedInfo%3FAiringId%3D15096519&startpad=2&StartPadOffsetType=earlier&endpad=5&EndPadOffsetType=later

So I'm assuming somewhere or other it defines a command of SetRecPad that somehow avoids the problem being caused by the sagex api - but I haven't found where SetRecPad is defined yet...