If I click the locate crosshair in an RPP PUR window, it seems to either do nothing or it centers somewhere randomly away from the PUR location. The crosshair in a UR window or a regular place PUR works fine, it's just RPP PUR. I disabled everything but URO+ to make sure and I have all the Place and UR options unticked.
Assistant Regional Coordinator - NOR
Global Champ - US
WME Beta Community Coordinator
Yes it is native. With all scripts off or if I turn off only URO, it works fine. With URO on as the only script, it doesn't. I don't see that URO has any pan/zoom options, but I don't know how else to explain it.
Assistant Regional Coordinator - NOR
Global Champ - US
WME Beta Community Coordinator
I wonder if that is the console diagnostics output that Twister enabled a couple of versions back working on the Clear Feed problem. I see that spamming as well.
Assistant Regional Coordinator - NOR
Global Champ - US
WME Beta Community Coordinator
Did some script testing and for me it's Toolbox that causes the WazeBits 0120 repeating line. If I do nothing more than disable TB extension, the WazeBits part stops completely. And this is TB 1.8.10.
Assistant Regional Coordinator - NOR
Global Champ - US
WME Beta Community Coordinator
In app closures are editable, but lately we've been having more problems with them not appearing in the app (even if edited by an editor) to the point where it's just better to delete and recreate. Something may have changed on the back end, but that's what we've been seeing.
Assistant Regional Coordinator - NOR
Global Champ - US
WME Beta Community Coordinator
CCP closure feeds are treated as app closures, is that an issue? This doesn't seem to be related to the segment-ID issue, it is showing a segment ID for the one I saw.Twister-UK wrote:3.160 is here...
- WazeFeed RTCs are no longer incorrectly treated as in-app closures
- WazeFeed RTCs now have their own filter options
Assistant Regional Coordinator - NOR
Global Champ - US
WME Beta Community Coordinator
https://www.waze.com/en-US/editor/?env= ... =506745108Twister-UK wrote:Do you have a PL to an example of such a closure? I had a quick scan around the PA area just now but couldn't see any mis-flagged RTCs.
PA_Turnpike is the CCP. He disabled URO to edit the closure.
Your explanation of the ID issue makes sense. No way to know for sure after the fact unless you see something in the closure info.
Assistant Regional Coordinator - NOR
Global Champ - US
WME Beta Community Coordinator
OK, thanks for checking Chris.Twister-UK wrote: Empty location field, null provider property, and a userID > 0... all unfortunately consistent with the signature of an in-app closure, so no way to differentiate without having URO learn all the possible userIDs for accounts that only generate closures from within WME. Easier to just wait for the segmentID fix to make its way into production.
Assistant Regional Coordinator - NOR
Global Champ - US
WME Beta Community Coordinator
It's because of the "no details" WME bug.laurenthembprd wrote:In a strange way, an active closure that I put with WME appears 'In-app'.
Assistant Regional Coordinator - NOR
Global Champ - US
WME Beta Community Coordinator
Re: [Script] UROverview Plus v3.146.1 (20181102)