Posts: 3,909
Joined: Dec 2004
Reputation:
20
Nuka1195
Skilled Python Coder
Posts: 3,909
i added a xbmc.getinfotag(int) to xbmcmodule.cpp.
before i submit the patch, i wondered if i should add all the infotag constants also? like you have for player and playlist...
also in guiinfomanager.h, i noticed a double entry, should i update that file and include it in the patch?
#define system_free_space_c 115
#define system_free_space_c 115
thanks
Posts: 26,215
Joined: Oct 2003
Reputation:
187
cool.
i've added the fix for the #define in my local build as well.
Posts: 3,909
Joined: Dec 2004
Reputation:
20
Nuka1195
Skilled Python Coder
Posts: 3,909
i changed it to:
xbmc.getinfolabel(int) and xbmc.getinfoimage(int). since there are overlaps of info. weather.conditions...
edit: i misunderstood what the constants at the bottom did. should there be a list of the values in the python doc?
Posts: 3,909
Joined: Dec 2004
Reputation:
20
Nuka1195
Skilled Python Coder
Posts: 3,909
thanks for the fix,
i've noticed in the xbmc.html and xbmcgui.html that some descriptions are well written with an example. some are formatted better.
if i was to update these and maybe add an example if one would help. is this something that could go in before 2.0?
it only affects .cpp files in lib\libpython\xbmcmodule\.
if so i could run makedoc.py and submit the files to cvs.
Posts: 3,909
Joined: Dec 2004
Reputation:
20
Nuka1195
Skilled Python Coder
Posts: 3,909
thor, i added the links down with the functions, but i like your idea better. would you share your changes so i can add them in.
thanks
Posts: 26,215
Joined: Oct 2003
Reputation:
187
yes, that is the correct behaviour. stretch = 0 as default.