I am going to contact Eduardocarvajal so he can take a look at it.
-
felohidalgo
- Coordinators
- Posts: 2416
- Has thanked: 194 times
- Been thanked: 496 times
Thanks Eduardo!!!EduardoCarvajal wrote:Hi All
Version 15.05.01 is here
This version includes:
- Fix compatibility problems with new Waze Editor
-
felohidalgo
- Coordinators
- Posts: 2416
- Has thanked: 194 times
- Been thanked: 496 times
Eduardo told us a couple days ago, than fixing the script this time has become more difficult, he has made some steps forward but it is not operational yet, he will let us know ASAP.
-
felohidalgo
- Coordinators
- Posts: 2416
- Has thanked: 194 times
- Been thanked: 496 times
You have Unlimited Size (Unsafe) option that allows unlimited nodes, sometimes works, sometimes not.
[img]https:///YFTVkM[/img][img]https:///aOdqQH[/img][img]https:///pWFhqA[/img][img]https:///yl9pMF[/img]
fgamio
iOS Beta Tester | WME Beta Tester
fgamio
iOS Beta Tester | WME Beta Tester
As a followup to my past (Oct 2013, prior to 13.10.16, sorry for not responding to your PM 
for that long) issues with expanding an existing river polygon (where the extension would occasionally break the clockwise / counterclockwise order of polygon's points), I've re-tested the script (and noticed that already the 13.10.18 solved the "Twisted" river problem - very good).
The only noticed issue: if I try to expand an existing polygon with a new segment and the segment contains any additional geometry node(s) (except the end node) inside the polygon, the script misleadingly states, that "Multiple street segments inside river. Cannot continue." instead of e.g. "Multiple segment nodes inside the river polygon. Cannot continue.". The initial post's "To expand an existing river:" paragraph could mention this as well.
Or, even better, omit all additional nodes of the segment inside the polygon area, except the one next to the polygon border.
for that long) issues with expanding an existing river polygon (where the extension would occasionally break the clockwise / counterclockwise order of polygon's points), I've re-tested the script (and noticed that already the 13.10.18 solved the "Twisted" river problem - very good).The only noticed issue: if I try to expand an existing polygon with a new segment and the segment contains any additional geometry node(s) (except the end node) inside the polygon, the script misleadingly states, that "Multiple street segments inside river. Cannot continue." instead of e.g. "Multiple segment nodes inside the river polygon. Cannot continue.". The initial post's "To expand an existing river:" paragraph could mention this as well.
Or, even better, omit all additional nodes of the segment inside the polygon area, except the one next to the polygon border.
I can not, but I'm willing to make the Slovak translation.EduardoCarvajal wrote:PS. I need help to translate Street to River+ to Hungarian (Magyar). Could you help me?
-
foxitrot
- Waze Global Champs
- Posts: 7263
- Has thanked: 1282 times
- Been thanked: 649 times
...with the good old crashing 
Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Symbian 2.1.99.114 (on N-E52), whiletrying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
I'll translate the strings. Just...
Sent from a touch display, which took care of perfectly scrambling my thoughts.
What about the multiple nodes? I realize just now that someone might indeed be trying to create or enlarge the river polygon with a multi-segment street (what you've been addressing), what I haven't tried yet. But multiple nodes inside the existing polygon do not work as well.foxitrot wrote:if I try to expand an existing polygon with a new segment and the segment contains any additional geometry node(s) (except the initial (A) node) inside the polygon, the script misleadingly states, that "Multiple street segments inside river. Cannot continue." instead of e.g. "Multiple segment nodes inside the river polygon. Cannot continue.". [...] Or, even better, omit all additional nodes of the segment inside the polygon area, except the one next to the polygon border.
Sent from a touch display, which took care of perfectly scrambling my thoughts.
-
foxitrot
- Waze Global Champs
- Posts: 7263
- Has thanked: 1282 times
- Been thanked: 649 times
...with the good old crashing Symbian 2.1.99.114 (on N-E52), while
trying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
Symbian 2.1.99.114 (on N-E52), whiletrying to get used to the good new asocial Android 4.xx.0.yyy (on OP-X March-me-Low).
thanks for the new version.EduardoCarvajal wrote:Hi All
Version 15.05.01 is here
This version includes:
- Fix compatibility problems with new Waze Editor
-
GFM_Danny
- Waze Local Champs
- Posts: 4539
- Has thanked: 1474 times
- Been thanked: 1382 times
As of Firefox version 44 (currently in beta) it is not allowed to assign a value to unsafeWindow (as it is an undefined constant for some reason). I'm currently checking some of the scripts in the forum to make sure they won't break once Firefox 44 goes live (January 26). I've checked your userscript and it doesn't actually use unsafeWindow anywhere, so the code below can safely be removed from the script.
Code: Select all
var bGreasemonkeyServiceDefined = false;
try
{
if ("object" === typeof Components.interfaces.gmIGreasemonkeyService)
{
bGreasemonkeyServiceDefined = true;
}
}
catch (err)
{
//Ignore.
}
if ( "undefined" === typeof unsafeWindow || ! bGreasemonkeyServiceDefined)
{
unsafeWindow = ( function ()
{
var dummyElem = document.createElement('p');
dummyElem.setAttribute ('onclick', 'return window;');
return dummyElem.onclick ();
} ) ();
}Belgium & Luxembourg Coordinator • Script Writing Community Coordinator
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
I thought for a moment you were talking to meseb-d59 wrote:Can you modify your bootstrap for compatibility with FF
It shouldn't have taken me two minutes to realise that's a message to the script author...
Belgium & Luxembourg Coordinator • Script Writing Community Coordinator
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
Hi, very good script. I love it, however since approx. 2 days ago, it started to throw an error upon clicking [Street to River] button. (While new unsaved street is created and awaiting the river to be created.)
Any idea, how to fix that?
btw: Is there a chance to allow SRP+ functionality also for saved streets? (Time to time I want to temporarily save the segment.)
Any idea, how to fix that?
btw: Is there a chance to allow SRP+ functionality also for saved streets? (Time to time I want to temporarily save the segment.)
-
Horizon911
- Posts: 513
- Has thanked: 279 times
- Been thanked: 26 times
Re: [Script] Street to River Plus