Posts: 15,264
Joined: Jan 2009
Reputation:
728
ronie
Team-Kodi Member
Posts: 15,264
yup, no problem if you use WindowXML / WindowXMLDialog.
i have little to no experience with the Window / WindowDialog classes
... and frankly, i would like to keep it that way :-)
Posts: 180
Joined: Aug 2016
(2017-01-05, 16:41)ronie Wrote: yup, no problem if you use WindowXML / WindowXMLDialog.
i have little to no experience with the Window / WindowDialog classes
... and frankly, i would like to keep it that way :-)
Not a fan of custom ui, or not a fan of the xml based classes?
Posts: 180
Joined: Aug 2016
(2017-01-06, 02:57)ronie Wrote: (2017-01-06, 02:42)Protocol-X Wrote: (2017-01-05, 16:41)ronie Wrote: yup, no problem if you use WindowXML / WindowXMLDialog.
i have little to no experience with the Window / WindowDialog classes
... and frankly, i would like to keep it that way :-)
Not a fan of custom ui, or not a fan of the xml based classes?
eh, i am a big fan of the XML based classes.
it's the non XML based ones i dislike. :-)
might be because i started out as a skinner, so creating a gui in xml is pretty easy for me.
but other than that, the non XML based classes are very limited compared to the XML based ones.
oh, and did i already mention i find them buggy as well? ;-)
Ah sorry I misread.
I agree on the flexibility 100%, just wish there was a way to make them more dynamic even if it was something like controlx.addcontrol(controlFromXml('path/xxx/xxxx'), newcontrolid) not like an include, even know they don't seem to work on addons, but more for a way to dynamically controls when using APIs that always change so you do not need to make an update every time an API changes. This way you could simply build an army of control xml files and then plug them in whenever needed.