Good to hear You're using Safari 6, right?
Path 0.0.41 is available with a new feature: segment details now display shield information if available. This may help in debugging incorrect or missing shield information that could cause issues incorrect display in the client. Unfortunately there is not yet a method to make changes to this, but we are investigating the possibilities.
- Attachments
Patch 0.0.42 fixes a small bug that throws an error when anything other than a segment is selected.
Update patch 0.0.43 is available. This is actually quite a large update:
Thanks!
As always, let me know if you encounter oddities.
~Mike
- New functionality: alert user that an error was thrown.
- Functionality update: show shields for all streets of a segment, where applicable.
- Script update: updated WMECH to latest version 1.4.6 (this is still beta, please provide timbones with feedback if you experience any issues -- I decided to move ahead with his beta script, as the old 1.4.2 was throwing errors in certain circumstances, and this one is a lot more stable).
- New script: included Junction Node Fixer script by bgodette (still experimental -- only enable this if you are familiar with it).
- Script update: updated URO to latest version (1.9).
- Bug fix: corrected version checking functionality for Safari 5.x. (This used to fail previously due to Safari Extension limitations in Safari 5.x, but a work-a-round has been found.)
Thanks!
As always, let me know if you encounter oddities.
~Mike
Had to release an emergency patch fix 0.0.44:
- Bug fix: 0.0.44 fixed an issue that would cause JNF to not behave as intended. There were no adverse effects, but it wouldn't fix certain node issues. This has been corrected.
Patch 0.0.46 is out now. This patch fixes some errors that users were experiencing relating to WMECH 1.4.6, as well as adds the current permalink to error reports to help with troubleshooting.
We are getting some error reports from various WazeBar users. In most cases it is related to errors from Waze itself, but there are some cases that are still popping up for Windows Safari 5.1.7 users. This is being investigated, and I will update the error logging to be more specific.
If you do receive an error, you should see a red skull and cross-bones. This indicates that you should save your edits and refresh the browser, which is currently the best work-around.
Also, be sure to update to the latest version. I have been getting error reports from users with older versions of WazeBar, and for the most part those errors have been addressed in newer versions.
Thanks!
~Mike
If you do receive an error, you should see a red skull and cross-bones. This indicates that you should save your edits and refresh the browser, which is currently the best work-around.
Also, be sure to update to the latest version. I have been getting error reports from users with older versions of WazeBar, and for the most part those errors have been addressed in newer versions.
Thanks!
~Mike
Just released patch 0.0.47 to address some errors that were being thrown occasionally, as mentioned in the previous post:
- Functionality update: improved error logging details.
- Bug fix: made code a bit more robust in certain places to avoid occasional errors been thrown.
- Bug fix: increased local storage limit to 1MB to alleviate certain errors in Safari 5.x.
Posted patch 0.0.48:
- Functionality update: changed error handling to not log errors for outdated versions of WazeBar, but instead throw an alert to the user prompting them to upgrade.
Re: WazeBar v0.0.40 - Safari Extension for Waze Map Editor