I really missed the Delete All button. Thanks!
I believe URO+ sets the closure event in the closure tab to None automatically. If so, the latest WME update disabled that capability.
Thanks.
Again, meh… Thanks for the heads-up, added to the to-do list…
sorry, wrong post. should be on FUME
Hi,
Any news yet about a new version on the horizon? The MTE selection is manageable, but still quite a tricky issue.
Cheers,
Eddy
New WME v.2.318 broke URO+ =(
Other than the obvious problem of not being able to display comment counts for URs, and the closure event auto-selection mentioned previously, is there anything else I ought to be looking out for here?
The URs option “Last comment less than…” stopped working.
That’s related to the display of comment counts - any functionality related to knowledge of the comments on a UR (such as how many, when made, who made them etc.) is currently broken.
4.17 fixes the MTE selection problem, dips its toe into the SDK waters to fix the problem with UR comment counts etc., and adds a bunch of new UR filter options relating to vehicle type, OS and suchlike…
Hi,
It seems that MTE selection is broken again after the WME prod update 
Eddy
Ugh, that didn’t last long.
The hover over segment feature is also broken.
Filtering URs is broken too.
4.18 fixes all known WME update-related issues…
Thank you so much!
WIth only URO+ enabled, the mouse cursor immediately moves off of the road closure line. At first, I didn’t notice it as I typed. Then I realized a letter I typed selected a MTE from the dropdown.
Yeah, that’s a side effect of the latest change required to get the “None” MTE override working again… I’ll see if I can refine it so that focus is returned to the description field once the MTE has been set.
Today’s WME prod release breaks the UR pill counter feature. The release introduced the new UR icons.
Yeah, this is an unfortunate side-effect of migrating to the SDK - it currently doesn’t provide a means of doing a bulk-retrieval of UR session data (as required in order to do anything comment-related beyond merely knowing that a UR has any comments in the first place) unlike the old direct access method URO used to use, and the “one result per request” method the SDK does provide then imposes a rather undesirable level of rate-limiting on how many requests can be stacked up without the server throwing a strop, so to respect staff’s desire for us all to get our scripts migrated ASAP, whilst also maintaining script functionality, I’ve had to massively slow down the rate at which URO pulls in all of this extra data, hence the correspondingly obvious delay in showing/updating the comment details and applying any related filtering settings…
To provide some level of indication when this is occurring, URO changes the mouse pointer to the one including the hourglass whilst it’s waiting for all the requests to be fulfilled.