JustinS83 wrote:You could, you know, just turn off that plugin It's the "Show Save Errors" option at the bottom of the tab

Yes, I could (I hadn't checked for the option).

I'm just suggesting it could be moved below the Edit/Save buttons so it doesn't shuffle them down? I won't complain if you don't.

New version/server working fine thank you!

I've found a potential problem. these 3 segments are being incorrectly highlighted as having unverified speed.

FAIR WARNING: do not zoom out to view the entire junction. Once you have seen it you will never be able to un-see it again.

Also, I would appreciate it if you could contact me about setting up a country configuration for the UK.

BruceQC wrote:I'm having the same issue as DarknessLover. If I just click on this link, http://waze.xpto.org/magic//magic.bundle.user.js , the script dls, but won't install. I get this error.
http://prntscr.com/hx0oor
Thanks!

Your screenshot appears to be an error from the Windows Scripting Host - that suggests you're trying to use Magic with Internet Explorer or Edge?

https://waze.xpto.org/magic/ wrote:Magic depends on Tampermonkey and is only tested on Chrome. We don't support other browsers.

I'm not saying you won't get help with the problem, but I wouldn't expect it.

My apologies. If you're using Chrome, I'm not sure why Windows Scripting Host is poking it's nose in. Possibly there's a file association involved. I'm guessing that the install is failing in TamperMonkey; then the Javascript source code is downloaded as a file; then WSH is set as the default handler for .js files and is trying to run the code. It's heavily minified and it wouldn't surprise me at all if WSH chokes on it.

This has prompted me to try some experiments. Note that I installed the new version earlier today without problems. So I removed Magic, then re-installed it - and got an error myself! The error about "cannot install from this site". That was followed by the download bar appearing at the bottom of Chrome as the file simply downloaded as a normal download.

After a bit of experimentation, I think I found a factor that I haven't seen mentioned before by any of the other people who have experienced problems. The script would not install if I had a WME window open. I tried several times and it seems that, if you have a WME window open, it somehow interferes with the installation of the script. I've now been round several times and been able to consistently install/re-install without WME windows open.

So my suggestion is to try this:

1. Make sure Magic is uninstalled from Tampermonkey (and not installed in any other way)
2. Copy the installation link https://waze.xpto.org/magic/magic.bundle.user.js to your clipboard
3. Close Chrome completely
4. Reopen Chrome with a fresh tab. If you have tabs set to open with Chrome, close them. If one of those was WME, I'm not sure what will happen.
5. Paste the link into the address bar
6. Wait for the page to fully load and show the code. Because it's minified and all on one line, this will take TamperMonkey a while to handle - maybe 20-30 seconds
7. Click the Install button
8. Check the Tampermonkey dashboard to see if it's there

I hope that will work for you. Beyond that, we're definitely into territory where I can't really help much more without setting up a remote desktop sharing session.

Mvan231 wrote:What does "Visual Search" highlight actually do? I can't seem to find info on it

If you type text into the search box (no need to hit RETURN), Magic will highlight segments with matching names.

SeveriorumPatrem wrote:Last I heard, guidance was to NOT junction railroads with driveable roads any more (a decision I didn't agree with but way above my pay grade). Has that changed back?

I won't speak towards any local /national guidelines on mapping. But at several meetups over the last couple of years, Waze routing devs (particularly Yigal) have recommended junctioning railroad and driveable segments. The reasoning given was that it allows Waze to better estimate transition times across the junctions.

One reason for not doing it is historical: in the distant past there have been examples of actual routing onto RR segments. Yigal assured us that Waze will now never route onto a RR segment and I've certainly not seen/heard of that happening for years.

There's an additional advantage to having a junction: if the crossing is closed (for maintenance or an accident), then you can add two one-way RTCs, each pointing away from the junction. That will allow drivers to be routed to either side of the crossing, right up to the crossing itself, but won't allow through-routing.

With the new layers menu in the latest WME release, it looks like the Magic layers toggle has disappeared from the layers menu.

dbcm wrote:Will publish this after i receive some examples from you guys

Errr - have you published something without letting us know? For the last hour or two, I've been seeing some . . . amusing effects in WME?

When I turn off the Magic layer, these symbols go away and they've all been related to end-of-segment problems. I'm not sure about the poop icon, but the explosion is perfect!

Can I please point out that this script (like all the others) is voluntarily provided by a Waze community member(s), at no cost, for the benefit of the community.

It is up to the developer of any script what functions they want the script to provide and how they wish to implement them. There's nothing wrong with making requests - half the functions in my own script only exist because someone else asked me to add them. But it's up to me whether or not I accept such a request and it's my choice as to how it works and whether or not it's enabled by default.

I admit it's unusual for a new feature to appear in a script without warning. I frequently criticise HQ for introducing new WME features without warning. Publishing an update to my own script is non-trivial, as I try to coordinate updates to the original post, the changelog post, the release post and publishing on Greasyfork. But there are no rules about this.

I'm sure we'll hear something soon; but in the meantime, please keep the nature of your posts polite and respectful. Throwing your toys out of the pram and demanding removal of a new feature you don't like is unfair. You may prompt the developer(s) to dig their heels in and not make changes - or become dispirited and stop bothering to make updates.

shmupi wrote:No ban?

Sent from my SM-G970U using Tapatalk

No. I decided to give you one more chance, Shmupi.