==== Original Post ==============================================
Ok, as promised we’re nearly ready to release Toolbox 1.4.6.0 – a bug fix release, under the new development team.
We’re still working out the distribution path, but that will hopefully be resolved in short order. The functionality is the same as 1.4.5.1 (the last release from OyyoDams), with the exception of the Map Links – we retained the Livemap and WME Beta links – and that it works under the current WME.
At this time, we may not be packaging for Safari – if this is truly a problem, let us know and we’ll see what we can make happen.
Thanks to BellHouse and giovanni-cortinovis for their work on this. We have a few other developers who are getting up to speed now, too, so we should be able to better tolerate updates to WME.
Amazing!! I was surprised to see Toolbox load in the editor – but not that surprised, since I’d seen these topic notifications on my phone anyway. Still, I was surprised to see it so quickly!
Anyway, I’m not seeing the beta or live map links. IIRC, Oyyo simply disabled the entire external-links portion of Toolbox, so even if you removed all the other ones besides livemap and beta, the external-links portion will have to be reenabled. That’s just my guess.
The Chrome version is not updated yet. We need to transfer it from Oyyodam’s Webstore account to a new one, this might take a bit of time. Please try to be patient. So the Firefox users are first this time.
I’ld like to use the opportunity to say a very big thank you to OyyoDams for his tremendous work on bringing WME Toolbox to what it is now. I think this extension has become a bread-and-butter-tool for many users, that’s due to his excellent work. Life would be different without it.
Will it be possible to put back in the button to bring up where you are in Google Map Maker?
For me, at least, the whole GMM experience is a huge PITA (interface not as easy to use as WME, constantly having to argue with some idiot reviewer who doesn’t know the area and just denies a change with a form-letter “current information is more accurate,” etc., just isn’t my idea of a good time), and the loss of a button that takes me right to the same area I’m looking at in WME was just “adding insult to injury.” I’ve stopped bothering even trying to fix a badly-located map pin on Google’s side that caused someone to be routed incorrectly in Waze since that button was removed from Toolbox.
So I’m wondering if it can be added back in…? If not, then fine - I’ll continue to not bother with GMM when the routing problem in Waze was caused by a badly-located map pin in GM.
At the moment, no, we won’t be able to put GMM back in. The concern is the use of outside mapping tools, and until Waze gives us a list of approved external tools, we can’t include anything.
I know GMM is a huge pain. At the moment, the best suggestion I can offer is to fix the problem in Waze – if it’s a street address, put the house number in the right spot. If it’s a business search, add a point-place. Eventually our good data will crowd out Google’s bad data.
They are already preferring their own data. The trouble comes when it’s not an exact match – they don’t seem to have fuzzy matching figured out (like 2708 should be close to 2710)
If that’s the case, then how come I still get URs from people who got routed to the back side of Reno-Tahoe International Airport instead of the terminal, when the stopping-point marker for the area place is at the terminal and the point place that I also added to try to help with this is also at the terminal? :?:
Because they’re selecting the wrong landmark entry from the search results.
As I said – fuzzy matching isn’t working.
If your landmark is “Reno-Tahoe International Airport” and the user searches for “Reno Airport”, it will probably pull Google’s result closer to the top.
Also, there was a tool a few months back when I was last Wazing that seems to be missing. I could press a button and all ‘useless’ junctions on the screen would get deleted. That was SO USEFUL. Any way we could have that back? I think it required level 3, but I am level 3, so…
