Hi Everyone,

iainhouse wrote:There appears to be another change in this version that isn't documented in the release notes.

Segments with closures on them highlight in orange when hovered over or selected. Not a bad idea, except that the colour is very similar to the colour of a segment that has been edited but not yet saved.

So thank you Waze, once again, for introducing a useful feature that is devalued by a stupidly poor contrast level. Is there some internal requirement that all WME Devs should have 20/20 vision, with no form of colour blindness and are only allowed to work in perfect lighting conditions with minimum 28" FHD monitors?

Will forward this feedback to the team to find a more distinctive colour for this.

iainhouse wrote:

delilush wrote:* Internal changes

Translation: A kick in the teeth for most of the script editors, with many scripts broken. Therefore also a kick in the teeth for the thousands of experienced editors who rely on those scripts.

I will have more to say on this subject later, but first I have to fix my own script.

I've updated in Scripters Hall (closed forum) with more details about this. There were some script breakers in the lastest beta versions that were fixed before releasing to production. We're happy to work with the developers to continue finding solutions for this.

Best,
Daliah

iainhouse wrote:I was very unfair earlier. I've modified my original post and I apologise for it here. Between some frustrations with Waze and with Real Life, and some other stuff I'm dealing with, I definitely allowed my mouth to pull away without first engaging my brain.

Yes, this update has broken many of the scripts and I felt that Waze could have done more to alleviate the situation. But the fact is that the script writers were told of the major internal change. For myself, at least, I didn't notice at the time and I haven't had the time to check out the problems, so it's entirely down to my own laziness.

In fact, I think that we could probably have done more to communicate to Waze that this update was going to have a major effect on the scripts and maybe something could have been done about that.

As Daliah said above, she has posted more information in Scripters Hall - including information she gave me at the Global Meetup that I was hoping would be spread a bit wider. I think we will probably be having some discussions there about how we can better manage how WME updates interact with the scripts. Given that HQ is willing to work with us on scripts, I shouldn't be complaining unless I do my part to maintain the relationship.

Maybe I have a problem with this time of year: it's almost exactly 3 years since I had a little rant. I probably need to lower my blood pressure again.

Thank you Iain! I'm glad we're talking about this stuff. I think by letting each other know how things work and what hurts and where, there is often so many things we figure out we can be doing better together.

Thank you so much for fixing the non-existent streetid bug!

delilush wrote:* Internal changes

Translation: A kick in the teeth for most of the script editors, with many scripts broken. Therefore also a kick in the teeth for the thousands of experienced editors who rely on those scripts.

[EDIT] This was unfair and rude of me. I have posted an apology further down this topic.

I will have more to say on this subject later, but first I have to fix my own script.

There appears to be another change in this version that isn't documented in the release notes.

Segments with closures on them highlight in orange when hovered over or selected. Not a bad idea, except that the colour is very similar to the colour of a segment that has been edited but not yet saved.

So thank you Waze, once again, for introducing a useful feature that is devalued by a stupidly poor contrast level. Is there some internal requirement that all WME Devs should have 20/20 vision, with no form of colour blindness and are only allowed to work in perfect lighting conditions with minimum 28" FHD monitors?

russblau wrote:

iainhouse wrote:Is there some internal requirement that all WME Devs should have 20/20 vision, with no form of colour blindness and are only allowed to work in perfect lighting conditions with minimum 28" FHD monitors?

Didn't you have to pass the physical when you signed up, Iain?

Sure - but 7 years of using WME has not been kind to my eyesight, never mind the lack of physical exercise.

I was very unfair earlier. I've modified my original post and I apologise for it here. Between some frustrations with Waze and with Real Life, and some other stuff I'm dealing with, I definitely allowed my mouth to pull away without first engaging my brain.

Yes, this update has broken many of the scripts and I felt that Waze could have done more to alleviate the situation. But the fact is that the script writers were told of the major internal change. For myself, at least, I didn't notice at the time and I haven't had the time to check out the problems, so it's entirely down to my own laziness.

In fact, I think that we could probably have done more to communicate to Waze that this update was going to have a major effect on the scripts and maybe something could have been done about that.

As Daliah said above, she has posted more information in Scripters Hall - including information she gave me at the Global Meetup that I was hoping would be spread a bit wider. I think we will probably be having some discussions there about how we can better manage how WME updates interact with the scripts. Given that HQ is willing to work with us on scripts, I shouldn't be complaining unless I do my part to maintain the relationship.

Maybe I have a problem with this time of year: it's almost exactly 3 years since I had a little rant. I probably need to lower my blood pressure again.

voludu2 wrote:In that image above, In "Via Merulana St. 209"
What does "St." stand for?

The road name there is "Via Merulana"

I see the same thing on segment after segment - For example "E 141st St St. 321".

What is the extra "St." for?

It appears to be irrelevant information. It is just adding St. to the end of every segment name. It really should be removed.

That has been reported and IIRC, staff said it is WAD.

The workaround is to hit the esc button instead of tabbing off or hitting apply.


Edit:

Found the thread (Beta viewing only)