You can click the "disable" checkbox on the route tab when you don't need it...
I've written to our Community Manager to find out if there is any Waze-oriented reason for this disappearance.
As for the license -- I wouldn't worry about it. Without anything in the code or documentation, I would say it's fair to assume it was public domain (or at least inasmuch as you don't profit directly from it). The worst case scenario is that he comes back and asks for you to cease and desist -- which you then do.
I've been trying to update it to get it to work, but haven't gotten as far as I'd like.
As for the license -- I wouldn't worry about it. Without anything in the code or documentation, I would say it's fair to assume it was public domain (or at least inasmuch as you don't profit directly from it). The worst case scenario is that he comes back and asks for you to cease and desist -- which you then do.
I've been trying to update it to get it to work, but haven't gotten as far as I'd like.
Not sure it's the same person. This has been added:
I've tested it and it appears to work. You may need to click the "disable" checkbox, then unclick it (I did).
Code: Select all
/* Fix for new WME by tkr85 */
Let me know if you need any original posts updated.
No, but I can edit any post.PesachZ wrote:All the original post seem to have been deleted, are you able to add new ones?doctorkb wrote:Let me know if you need any original posts updated.
Sent using Tapatalk for Android 4.4.2
We can modify the first post of any thread, I'll just include a "MODERATORS COMMENTS" header for whatever we add to it.
Hey MapOMatic - just got your forked version and it fixes what was broken.
Noticed when trying to link to it, though, that you haven't updated the links within the Route Speed tab to point at your fork. When clicking "WME Route Speeds" it points to the old version's GreasyFork page.
Just thought you might want to fix that.
Noticed when trying to link to it, though, that you haven't updated the links within the Route Speed tab to point at your fork. When clicking "WME Route Speeds" it points to the old version's GreasyFork page.
Just thought you might want to fix that.
I am unable to reproduce the issue.
Thanks,
dspille
Country Manager, Multi-State Manager - South Central Region
SCR Wiki
images/ranks/CountryManager_Badge.pnghttps://storage.googleapis.com/wazeoped ... _Texas.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/s0175.pnghttps://s.waze.tools/c5s.png
dspille
Country Manager, Multi-State Manager - South Central Region
SCR Wiki
images/ranks/CountryManager_Badge.pnghttps://storage.googleapis.com/wazeoped ... _Texas.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/s0175.pnghttps://s.waze.tools/c5s.png
It's working for me with the WME Fix Map Object script.
Thanks,
dspille
Country Manager, Multi-State Manager - South Central Region
SCR Wiki
images/ranks/CountryManager_Badge.pnghttps://storage.googleapis.com/wazeoped ... _Texas.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/s0175.pnghttps://s.waze.tools/c5s.png
dspille
Country Manager, Multi-State Manager - South Central Region
SCR Wiki
images/ranks/CountryManager_Badge.pnghttps://storage.googleapis.com/wazeoped ... _Texas.pnghttps://s.waze.tools/beta.pnghttps://s.waze.tools/s0175.pnghttps://s.waze.tools/c5s.png
He's back with a new username (on greasyfork):
https://greasyfork.org/users/5745-fz69617
https://greasyfork.org/users/5745-fz69617
Dummyd2 AKA D2.
Retired - retraité de Waze
Retired - retraité de Waze
I fight a long time with cross origin VS injected code.
Here is the full explanation:
http://stackoverflow.com/a/11379215
I found it after I worked some hours and wrote the solution number 3 in the link above in my scripts.
If you (any scripter for WME) want, you can copy paste it from chat addon. It is at the very beginning of the script. Think about changing the name of the downloadHelper object to avoid conflicts
Here is the full explanation:
- The monkey has a function: gm_xmlhttperquest that allows cross origin requests, but to use it, you must set a @grant in the header.
- Doing this, your script is run in a sandbox. You can access to the window object with the unsafewindow object but if you bind a handler defined in your sandboxed code on and event triggered in the original page, it fails on firefox.
- So, you need to inject your code.
- But your injected code doesn't know the gm_xmlhttprequest object. => goto 1)
http://stackoverflow.com/a/11379215
I found it after I worked some hours and wrote the solution number 3 in the link above in my scripts.
If you (any scripter for WME) want, you can copy paste it from chat addon. It is at the very beginning of the script. Think about changing the name of the downloadHelper object to avoid conflicts
Dummyd2 AKA D2.
Retired - retraité de Waze
Retired - retraité de Waze
Re: [Script] WME Route Speeds (Traffic)