2006-06-17, 02:44
nuka and i discussed this a little bit over on the x-s forum. basically, now that i am screwing around with user configurable buttons, i found a bit of "missing" functionality.
we were talking about using a built in function similair to the skin.setimage() which could be used to select a python script of xbe file.
for skin.setscript(), the behavior would be nearly identical to skin.setimage, except the file display filter would only show files name *.py.
say the filepath returned by the user's input is x:\fu\bar.py.
the builtin function would return & set to the specified skin string variable "xbmc.runscript(x:\fu\bar.py)" (obviously quotes not included).
for setxbe, i figure same thing only the display filter would only show *.xbe and *.cut files, and the returned string would be xbmc.runxbe(x:\fu\bar.xbe). whatcha think?
we were talking about using a built in function similair to the skin.setimage() which could be used to select a python script of xbe file.
for skin.setscript(), the behavior would be nearly identical to skin.setimage, except the file display filter would only show files name *.py.
say the filepath returned by the user's input is x:\fu\bar.py.
the builtin function would return & set to the specified skin string variable "xbmc.runscript(x:\fu\bar.py)" (obviously quotes not included).
for setxbe, i figure same thing only the display filter would only show *.xbe and *.cut files, and the returned string would be xbmc.runxbe(x:\fu\bar.xbe). whatcha think?