2013-01-01, 16:26
Hi,
I see the following behavior (with XBMC Frodo 12 rc2 on Win7):
When a (video) plugin exits its Python code with exit(0), it generates this xbmc.log entry:
15:12:02 T:3620 INFO: Scriptresult: Aborted
When it drops off its file end without a coded exit() function call, it generates:
15:06:37 T:4464 INFO: Scriptresult: Success
15:06:37 T:4464 INFO: Python script stopped
-> What is the proper way for a plugin to indicate back to XBMC that it encountered an error ?
-> Why does XBMC consider a plugin that exits with exit(0) an abort ?
(I searched for but did not find this on the xbmc wiki ...)
Thx
Andy
I see the following behavior (with XBMC Frodo 12 rc2 on Win7):
When a (video) plugin exits its Python code with exit(0), it generates this xbmc.log entry:
15:12:02 T:3620 INFO: Scriptresult: Aborted
When it drops off its file end without a coded exit() function call, it generates:
15:06:37 T:4464 INFO: Scriptresult: Success
15:06:37 T:4464 INFO: Python script stopped
-> What is the proper way for a plugin to indicate back to XBMC that it encountered an error ?
-> Why does XBMC consider a plugin that exits with exit(0) an abort ?
(I searched for but did not find this on the xbmc wiki ...)
Thx
Andy
