doctorkb wrote:Does TB's calling of uroWazeBits() make sense? Should we remove that from TB to avoid future issues?
I recall there was some problem a while ago where having URO+ and TB installed would cause WME to misbehave and that TB was tweaked to fix this, so I'd hazard a guess that the uroWazeBits() call is related to this fix, however as I was unaware until these past few days that TB has been making this call, I don't know for certain why it's doing it, when it started doing it, or whether removing it would cause a problem.
Based on the comment added to the console log when TB calls the function, it's something to do with layers, and since the only thing uroWazeBits() does in relation to layers is to get the layer indices for all the layers URO+ later uses, I'd suspect that having TB installed as well has (or had) the potential to alter the layer indices, such that when URO+ then came to try accessing a layer using the previously stored index, that index was now pointing to a different layer.
However, looking at the layer indices listed in the console by URO, I can't see any changes between those listed during the initial function call and those listed following the TB-initiated call, so it may be that further changes in TB and/or WME have rendered this fix redundant.
In short: I don't know for certain why TB is making that call or whether it's still required, but since it now seems that having it make that call is no longer an issue, I'd suggest leaving it alone for now.