2008-08-19, 16:17
This is more of a heads up than anything else:
Since the recent mention of 'fixing' the python dialogProgress in the xbmc changelog, I've had lots seemingly random script 'hangs'.
Long story short...
old xbmc builds would happy display a dialogProgress.create() / . update() when in xbmcgui.lock() state but the newer builds would freeze, without an except.
I can't pin it 100% on the 'fix' but it its behaviour changed around when that was mentioned
Personally I'd prefer a dialogProgress be allowed to be displayed when in this lock() state, as it gives you the ability to inform user of an error straight away. But now I've found it, I can code to avoid hangs.
You can press the back button now ...
cheers
BBB
Since the recent mention of 'fixing' the python dialogProgress in the xbmc changelog, I've had lots seemingly random script 'hangs'.
Long story short...
old xbmc builds would happy display a dialogProgress.create() / . update() when in xbmcgui.lock() state but the newer builds would freeze, without an except.
I can't pin it 100% on the 'fix' but it its behaviour changed around when that was mentioned
Personally I'd prefer a dialogProgress be allowed to be displayed when in this lock() state, as it gives you the ability to inform user of an error straight away. But now I've found it, I can code to avoid hangs.
You can press the back button now ...
cheers
BBB