New WME release v1.16-82

The place to get information and ask questions about everything to do with properly and successfully editing the Waze Map.

Use this forum for all general editing questions, and the sub-forums for specific types of Waze Map Editor features.

Moderators: Unholy, bextein

Re: New WME release v1.16-82

Postby Glodenox » Sun Nov 20, 2016 1:23 pm

Another WME issue is the date format used almost everywhere within the WME that 'got changed':
[ img ]

While the time information can be very useful, the way the timezone is displayed is a bit too expressive. This doesn't seem like an intentional change to me as it is caused by referring to keys in the translation strings that don't exist (any more?).
More precisely, I'm talking about the strings 'date.formats.long', 'time.formats.long' and 'date.formats.default', which gets referred to in many templates. The only similar string I can find is 'date.long', but in that string hours and minutes aren't displayed, which really helps a lot in investigating an UR, for example.

I've been able to fix this display issue by adding these strings myself like this, confirming the cause of the issue:
Code: Select all
I18n.translations.en.time = {};
I18n.translations.en.time.formats = {};
I18n.translations.en.time.formats.long = "%a %b %d %Y, %H:%M";
I18n.translations.en.date.formats = {};
I18n.translations.en.date.formats.long = "%a %b %d %Y, %H:%M";
I18n.translations.en.date.formats.default = "%a %b %d, %Y";


Which gives me this:
[ img ]
EDIT: note that I've modified the format in the code block, so the actual result is different than shown in the image above

I'll try to whip up a quick userscript to fix this and provide a way to change this locally.
Last edited by Glodenox on Sun Nov 20, 2016 9:14 pm, edited 4 times in total.
Script Writing Community Coordinator
[ img ][ img ]
Glodenox
Waze Global Champs
Waze Global Champs
 
Posts: 1001
Joined: Tue Aug 11, 2015 9:04 pm
Location: Belgium
Has thanked: 473 times
Been thanked: 1158 times

Re: New WME release v1.16-82

Postby RodNav » Sun Nov 20, 2016 1:32 pm

The time zone info as displayed is really annoying now, as there is far too much info. Take a look at how 2 entries appear under Drives:

Sun Nov 20 2016 12:54:01 GMT+0200
(South Africa Standard Time), 12:54

Sat Nov 19 2016 19:24:00 GMT+0200 (South
Africa Standard Time), 19:24

(I formatted them exactly as they appear, with different line breaks!)

All I need/want to see is:
Sun Nov 20 2016 12:54:01
Country Manager for South Africa.
LG G2 (aka LG-D802), Android 4.4.2
[ img ]
RodNav
Waze Local Champs
Waze Local Champs
 
Posts: 293
Joined: Mon Jun 27, 2011 6:39 am
Location: Somerset West (40km from Cape Town), South Africa
Has thanked: 197 times
Been thanked: 58 times

Re: New WME release v1.16-82

Postby iainhouse » Sun Nov 20, 2016 2:08 pm

Glodenox wrote:I'll try to whip up a quick userscript to fix this and provide a way to change this locally.


I hope you don't mind: given that this is a UI fix and I have a script that does that, I've incorporated this small addition into the WME Fix UI script. The updates is already on Greasyfork and I'm just off to update the script thread. :mrgreen:
[ img ][ img ][ img ]
UK AdminsUK WikiWaze FAQWMEFU Script :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season
iainhouse
Country Manager
Country Manager
 
Posts: 9893
Joined: Mon Jul 23, 2012 5:16 pm
Location: on the road from London to insanity, with Waze HQ in the driving seat
Has thanked: 2542 times
Been thanked: 7890 times

Re: New WME release v1.16-82

Postby Glodenox » Sun Nov 20, 2016 4:18 pm

iainhouse wrote:I hope you don't mind: given that this is a UI fix and I have a script that does that, I've incorporated this small addition into the WME Fix UI script. The updates is already on Greasyfork and I'm just off to update the script thread. :mrgreen:

That is fine by me :)

I've uploaded the userscript to fix this issue specifically over here: https://greasyfork.org/scripts/25011-wm ... format-fix
After some experimenting, I went for the following date format: "%a %b %d %Y, %H:%M"
This gives a date like this: "Fri Nov 18 2016, 08:27", which seems like a good fit.
Last edited by Glodenox on Sun Nov 20, 2016 4:30 pm, edited 1 time in total.
Script Writing Community Coordinator
[ img ][ img ]
Glodenox
Waze Global Champs
Waze Global Champs
 
Posts: 1001
Joined: Tue Aug 11, 2015 9:04 pm
Location: Belgium
Has thanked: 473 times
Been thanked: 1158 times

Re: New WME release v1.16-82

Postby AntonioGMuriana » Sun Nov 20, 2016 4:21 pm

Please, include the year, otherwise the date is useless!!
AntonioGMuriana
Map Raider
Map Raider
 
Posts: 230
Joined: Mon Jun 27, 2016 12:26 am
Location: Madrid, Spain
Has thanked: 51 times
Been thanked: 46 times

Re: New WME release v1.16-82

Postby Glodenox » Sun Nov 20, 2016 4:29 pm

Oh right, those get used in the 'segment last updated' and 'segment added' dates. I only thought about UR's where usually the year isn't as important.
The script has been updated to use the format ''%a %b %d %Y, %H:%M' which includes the year, but I've had to remove the timezone data, because it'd become too wide again otherwise.
Script Writing Community Coordinator
[ img ][ img ]
Glodenox
Waze Global Champs
Waze Global Champs
 
Posts: 1001
Joined: Tue Aug 11, 2015 9:04 pm
Location: Belgium
Has thanked: 473 times
Been thanked: 1158 times

Re: New WME release v1.16-82

Postby iainhouse » Sun Nov 20, 2016 4:46 pm

AntonioGMuriana wrote:Please, include the year, otherwise the date is useless!!

Thanks! I've also updated WME Fix UI accordingly. :mrgreen:
[ img ][ img ][ img ]
UK AdminsUK WikiWaze FAQWMEFU Script :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season
iainhouse
Country Manager
Country Manager
 
Posts: 9893
Joined: Mon Jul 23, 2012 5:16 pm
Location: on the road from London to insanity, with Waze HQ in the driving seat
Has thanked: 2542 times
Been thanked: 7890 times

Re: New WME release v1.16-82

Postby Glodenox » Sun Nov 20, 2016 9:17 pm

After rdnnk pointed out that the closures view was still showing very long dates, I looked around in the code and eventually discovered another missing string: 'date.formats.default'. I would've sworn I had searched for 'date.formats' in an attempt to find other missing strings, but whatever.

I've updated the userscript by setting this value to '%a %b %d, %Y'.
Script Writing Community Coordinator
[ img ][ img ]
Glodenox
Waze Global Champs
Waze Global Champs
 
Posts: 1001
Joined: Tue Aug 11, 2015 9:04 pm
Location: Belgium
Has thanked: 473 times
Been thanked: 1158 times

Re: New WME release v1.16-82

Postby GeekDriverPeaceful » Sun Nov 20, 2016 11:43 pm

Got notification of new WME update:
Previous: 1.2.295-d611754
New: 1.2.305-5cb35a0

I wonder what changes were made.
GeekDriverPeaceful
Beta tester
Beta tester
 
Posts: 700
Joined: Mon May 30, 2016 4:28 pm
Location: USA
Has thanked: 792 times
Been thanked: 237 times

Re: New WME release v1.16-82

Postby AlObaili » Sun Nov 20, 2016 11:46 pm

GeekDriverPeaceful wrote:Got notification of new WME update:
Previous: 1.2.295-d611754
New: 1.2.305-5cb35a0

I wonder what changes were made.


Sorry if this is an obvious question, but where can I get this WME version notification?
[ img ]
[ img ][ img ][ img ][ img ]
مـنـســـق مــجـتـمـع ويـز الـسـعــوديـة والــبحـريـن ومـنـســق الـتعــريـب لـمـنـتجـات ويــز
CM for Saudi Arabia & Bahrain & Transifex Coordinator for Arabic
AlObaili
PartnerCoordinator
PartnerCoordinator
 
Posts: 346
Joined: Sun Apr 20, 2014 4:04 pm
Location: Saudi Arabia
Has thanked: 233 times
Been thanked: 149 times

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: No registered users