Re: WazeBar v0.0.48 - Safari Extension for Waze Map Editor
Posted: Sun Nov 18, 2012 5:49 pm
Thanks for all your hard work!mike-bronner wrote:Thanks for the update. I will see what I can do about that ASAP.
~Mike
Waze: outsmarting traffic together
https://www.waze.com/forum/
Thanks for all your hard work!mike-bronner wrote:Thanks for the update. I will see what I can do about that ASAP.
~Mike
All is working well now!mike-bronner wrote:This should now be vixed in patch 0.0.49. Please let me know if you are having any difficulties what-so-ever using WazeBar. Thanks!ohiostmusicman wrote:I'm now getting an error saying "WME Junction Node Fixer has failed to load due to version mismatch."
~Mike
I noticed today that City Highlight seemed to work part of the time and I could only select the most prominent city in my view. When I was trying to hunt down cities with only one letter today, it wouldn't let me do it...AlanOfTheBerg wrote:Hmm... well, not all is working great.
City highlight isn't working the way the latest WMECH does in Chrome. (Tim's not bgodette's branch.) In that version, we get city/state info. And, in my testing, the city highlight in WazeBar doesn't work at all.
My work around has been if you permalink/refresh in the area you're working in you'll be able to select the city on screen. If you move cities then you'll need to permalink/refresh.AlanOfTheBerg wrote:Known issue brought up a few posts back.Webs101 wrote:I'm using v. 0.0.51 on Safari 6.0.2 in OS 10.8 and nothing I do can get the city field to update in the drop-down menu for highlighting. It's stuck on a single city, far from where I'd like to use it.
Yes...same issues...edsonajj wrote:Have you tried using command(control)-s?ohiostmusicman wrote:With the new WME, there seems to be a WazeBar issue with fixing a UR and saving. When I select one and click either of the three options, the save button doesn't reflect the change and it won't let me save. When I permalink/refresh it asks if I want to navigate away from the page but I still can't save. When I disable WazeBar and go back to the basic editor there's no saving problem.
I managed to unpack the .gzip safari extension.mike-bronner wrote:I was thinking about this, but will need to do some more research. In theory, all the meat and potatoes is there, it would just need to be wrapped as a userscript.Timbones wrote:How hard will it be to port this to Chrome/Firefox?
That probably won't work, but you never know. I think the Framework that Safari Extensions are built upon is very different from other toolbars or userscripts like Greasemonkey.robin1979 wrote:Rename the .safariextz to .gz and see for yourself . Might just work as is (but I'm not that experienced extension coder, but you seem to be ).