milkboy wrote:

brandonrossl wrote:I'd like to add a request that a best continuation/no instruction color be used as well for those times where it's super confusing.

This is looking to be one of the most useful plug-ins! Great job!

Yeah. It's work in progress Probably won't have much time to do anything until next week though

I'm making a lot of progress on the modified best continuation algorithm, but it means the script will have to parts all the segment names and alt names which it never did before. So give him some time.

Milkboy, thanks now I can use the master branch. Is there a way to install from gut hub, or I have to copy code into a custom script?

If you want to work with the new algorithm I can send it you. Right now it's just hand drawn, but I can write it on a spreadsheet for you.

Re: roundabouts, there's another script called [Script] WME Roundabout Angles v1.04 which does this rather well, perhaps you could incorporate some of that code. It was written by wlodek76 and recently taken over. See the end of thread on script forum.

Sent using Tapatalk for Android 4.4.2

brandonrossl wrote:I'd like to add a request that a best continuation/no instruction color be used as well for those times where it's super confusing.

This is looking to be one of the most useful plug-ins! Great job!

milkboy wrote:

brandonrossl wrote:I'd like to add a request that a best continuation/no instruction color be used as well for those times where it's super confusing.

This is looking to be one of the most useful plug-ins! Great job!

Yeah. It's work in progress Probably won't have much time to do anything until next week though

I've sent milkboy a PM with the new algorithm for best continuation. It's rather complex and might take some time to implement.

Sent using Tapatalk for Android 4.4.2

milkboy wrote:Mmmmm.. Got something to think about with the best continuation.. As there might be one-way or otherwise restricted turns in one direction, but not the other, how should that be handled? Would there have to be two separate markers, or just use the order in which the segments were selected to choose driving direction? The latter one is "easy" while the former may be a bit complicated.. Will probably go with the latter one at least for now, but it could probably use some indication of driving direction.. Mostly just thinking out loud here =)

Very interesting, I hadn't considered that. You can even have no instruction only one option in one direction with a split going the other way (at a fork in the road). All the other routing scripts (route checker, route speeds, etc.) Utilize the order in which segments were selected to choose directionality to display. This method is intuitive, and already something people are accustomed to.

An indication of directionality would be nice, and an option to reverse directionality, perhaps by clicking on the indicator which could be another bubble nearby or floating in a corner, would be even nicer.

Sent using Tapatalk for Android 4.4.2

milkboy wrote:

PesachZ wrote:Milkboy, thanks now I can use the master branch. Is there a way to install from gut hub, or I have to copy code into a custom script?

Not actually sure.. Currently pretty much using copy-paste with Tampermonkey while developing =/ Probably not the best solution. Anyway, auto-updating from the GitHub repo is probably a bad idea also, as committed version might actually be very much untested

Oh well, I'm using the 1.6 master from github, but I'll wait for an official release to report any bugs then.

I will say though the 'regular turn' color is activated at 44° instead of the gray area color.
Sent using Tapatalk for Android 4.4.2

milkboy wrote:

PesachZ wrote: Oh well, I'm using the 1.6 master from github, but I'll wait for an official release to report any bugs then.

I will say though the 'regular turn' color is activated at 44° instead of the gray area color.

Fixed that today, but then again there are also other issues with the latest commits. Hope to have something semi stable in a few hours. Working on the best continuation logic

We can't wait[emoji2] , but alas we have to.
Thank you very much for pursuing this.
Since we can only thank once per post, here's a couple extra [emoji106] [emoji106] [emoji106] [emoji106] [emoji106]

Sent using Tapatalk for Android 4.4.2

milkboy wrote:

brandonrossl wrote:Likewise on the thanks! I'm a Chrome user so let us know when to start clicking the update extensions button!

Well.. Need to gather a little more feedback and do quite some testing before updating the addon. I don't want to break the existing functionality either..

Thank you, the arrows are a nice touch. Found some Wayfinders highlighted white on both sides of the split. They should be getting instructions on both sides (green), is this part still being worked on? Wasn't in the known issues. Only three segments meet at a junction. All same type the s-out and an have no name

Sent using Tapatalk for Android 4.4.2

milkboy wrote:

PesachZ wrote:Found some Wayfinders highlighted white on both sides of the split. They should be getting instructions on both sides (green), is this part still being worked on? Wasn't in the known issues. Only three segments meet at a junction. All same type the s-out and an have no name

There may be a ton of (unlisted) bugs, only tested a fraction of all possible combinations Could you post a link with the segments selected?

https://www.waze.com/editor/?env=usa&lo ... s=82065920

I have a whole test community set up with tons of variations, and all combinations used to figure out these algorithms. When I have some time on the computer, I'll try then all and see what's broken. ( or you could)

Sent using Tapatalk for Android 4.4.2

voludu2 wrote:Sorry. I edited my post while you were typing.

If I start WME with a segment PL, the JAI tab shows up but doesn't do anything.

When you say does nothing, do you mean if you deselect the segment and then select it again angles are not displayed, or deselect the segment and try to click the JAI tab and it doesn't open?

Sent using Tapatalk for Android 4.4.2

milkboy wrote:

SuperDave1426 wrote: (Side question: How automatic does using github make the update process when using it as your source for Greasemonkey/Tempermonkey? When you update the script there, will Greasemonkey/Tampermonkey know to update the script automatically?)

The @updateURL points to the current master branch, so it should "just work". The possible downside is that it's always going to update to the latest (committed) development version, which usually should work though.

SuperDave1426 wrote: Something you might want to consider is to put it on greasyfork.org. A lot of script authors who used to use userscripts.org are using that now, and a lot of people who are just going straight to a source to look for user scripts who used to use userscripts.org are now searching greasyfork.org for those scripts. There are quite a few WME scripts already there.

Just a thought, anyway.

Maintaining the code in several places is a pain-in-the-***, but I'll check it out =)

Greasyfork.org can pull committed changes automatically from github, and the like. So you only have to maintain a single copy of the code and everything else is automated. Just push an update to the existing live version soit looks at greasyfork for future updates. Then once setup you'd only ever need to update and commit source code, and the rest is automatic.[emoji1]

Sent using Tapatalk for Android 4.4.2

milkboy wrote:Added script on greasyfork also for completeness. The support for web hooks to update was a pleasant surprise =)

[emoji1] With the web hooks you can even really run a separate beta testing branch of the script. I know some authors are doing that.

Sent using Tapatalk for Android 4.4.2