2013-10-25, 17:45
Hi,
This seems like an obvious question but searching didn't provide any useful results.
When picking new ids for controls I have to be careful not to overlap. I might get lucky and pick one that appears to work, but maybe that's because a conditional include* didn't get called. I could grep for an id number, but that might be overkill because ids can coexist if they will never appear on the same window.
So is there a way to detect clashing ids? Perhaps this is a features request for something to be written in the log when a duplicate id is detected.
*ETA:
Can includes be made conditionally? As far as I can tell XBMC skins only have conditional visibility. So includes are called regardless. Right? Does a visible control (and its id number) take priority over an invisible one?
This seems like an obvious question but searching didn't provide any useful results.
When picking new ids for controls I have to be careful not to overlap. I might get lucky and pick one that appears to work, but maybe that's because a conditional include* didn't get called. I could grep for an id number, but that might be overkill because ids can coexist if they will never appear on the same window.
So is there a way to detect clashing ids? Perhaps this is a features request for something to be written in the log when a duplicate id is detected.
*ETA:
Can includes be made conditionally? As far as I can tell XBMC skins only have conditional visibility. So includes are called regardless. Right? Does a visible control (and its id number) take priority over an invisible one?