[KenV99]

Hi,

Has 'xbmc.Monitor.waitForAbort' been implemented as discussed here?: http://forum.kodi.tv/showthread.php?tid=196360&page=2

I'd just like to verify that the behavior is such that the method returns at the time abort is requested rather than waiting for the sleep cycle to expire (allowing the loop to have a very large time for sleep). The API changes haven't made it into PyDocs yet...

I'd also like to verify that the call is in seconds as opposed to ms as it was in abortRequested. If so, does it accept float as well as int?

Thanks.

[takoi]

Yes to both. It's the same as python's threading.Event.wait() method so you can see docs for that. There's also an example usage on the Service addons (wiki) wiki page explaining it.

[KenV99]

Thanks!

Would it be worthwhile creating a sticky thread here in the Python Add-on Development forum with a link to the API changes, similar to sticky thread that is there for Gotham? I would just do it but I don't seem to have permissions.

[takoi]

Me neither, I think. Ask a mod? Not sure it it's worth the trouble though. As you can see, maintain sticky threads quickly becomes a burden.
Should teach people to go to the wiki

[Martijn]

Like this?
http://kodi.wiki/view/Helix_API_changes

Forum threads are not that easy to maintain like Takoi said. Changes should be documented on the wiki.
Still need to move the Gotham changes to the wiki

[KenV99]

Like this?
http://kodi.wiki/view/Helix_API_changes

Forum threads are not that easy to maintain like Takoi said. Changes should be documented on the wiki.
Still need to move the Gotham changes to the wiki

Both you and Takoi have good points.

For me, because there was a sticky for Gotham, I was waiting for a sticky for Helix to appear here, so I wasn't looking in the Wiki.
So maybe remove the sticky for Gotham? Or create a sticky thread with just the link and close it for comment?

Just for consistency sake...

[Roman_V_M]

Like this?
http://kodi.wiki/view/Helix_API_changes

I don't want to sound too critical, but such listing without detailed info (e.g. method signatures and return types) is practically useless. As a maintainer of XBMCstubs, I'd want to add the info to the Kodi module stubs.

[takoi]

Like this?
http://kodi.wiki/view/Helix_API_changes

I don't want to sound too critical, but such listing without detailed info (e.g. method signatures and return types) is practically useless. As a maintainer of XBMCstubs, I'd want to add the info to the Kodi module stubs.

It's a wiki, and you know where to find the module source code for the full docs. I don't want to sound too critical either, but frankly, if you are not happy about the page you have only yourself to blame.

[Karnagious]

Cant see anything about it here: http://mirrors.xbmc.org/docs/python-docs/14.x-helix/

[Martijn]

Cant see anything about it here: http://mirrors.xbmc.org/docs/python-docs/14.x-helix/

still need to update those docs. will try tonight

[Karnagious]

Cant see anything about it here: http://mirrors.xbmc.org/docs/python-docs/14.x-helix/

still need to update those docs. will try tonight

Ta.

[Martijn]

updated

[takoi]

I guess it takes some time to propagate or something? I still see 'last updated 22.08.2014'..

[Martijn]

I guess it takes some time to propagate or something? I still see 'last updated 22.08.2014'..

that's a manual date which i forgot to change and don't have time to do anymore. docs are updated

[schapplm]

When calling monitor.waitForAbort(0.0), it seems to wait forever (which makes sense from looking at the implementation).
Is this behavior intended?
This was not so obvious (from the documentation) to me and I needed to do a workaround in my addon.