Win xbmc.sleep() acts weird
#1
I have noticed a strange behavior.

On Windows, xbmc.sleep() has a minimum of 1000ms, and will go up to 2 seconds if I provide a number under 1000ms.
What gives?
This does not happen on other systems (linux, mac)

Can I use time.sleep() instead?
Reply
#2
I've always used time.sleep() in my scripts. I didn't even know xvmc has a separate sleep function.
Reply
#3
(2013-11-13, 03:21)pkscuot Wrote: I've always used time.sleep() in my scripts. I didn't even know xvmc has a separate sleep function.

Ah! Good to know then Big Grin
Reply
#4
I believe xbmc.sleep() allows WindowXMLDialog and WindowXML events to still be processed whereas time.sleep() doesn't (I'm sure there are probably other subtle differences too)
Reply
#5
Yeah I thought so too..

Well that means I now need to go dig in the XBMC source code then Sad
Reply
#6
xbmc.sleep() also listens to internal overruling events and time.sleep() doesn't
Read/follow the forum rules.
For troubleshooting and bug reporting, read this first
Interested in seeing some YouTube videos about Kodi? Go here and subscribe
Reply

Logout Mark Read Team Forum Stats Members Help
xbmc.sleep() acts weird0