Ok, thanks. Glad to know it's being worked on.OyyoDams wrote:Yes redo roundabout has to be rebuilt from scratch. I'm working on it but it may take some time.SuperDave1426 wrote:Just wanted to drop a note here that "redo roundabout" is still adding +1 to elevation when it's run. Is that something which can be fixed?
https://j.mp/2X5xt19https://bit.ly/379DGR1https://j.mp/1A1VFerhttps://j.mp/1KDY3hbhttps://j.mp/3aYJWY5https://bit.ly/3jrDpM6
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
I've noticed in the highlighting section of the tool is an entry for "dead-end roundabout." Forgive the semi-stupid question, but what is a dead-end roundabout? Aren't roundabouts, by definition, NOT a dead end?
https://j.mp/2X5xt19https://bit.ly/379DGR1https://j.mp/1A1VFerhttps://j.mp/1KDY3hbhttps://j.mp/3aYJWY5https://bit.ly/3jrDpM6
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
OyyoDams wrote:No, a roundabout is NOT a dead-end. A roundabout is used to connect several roads in a circular way.
When there is a dead-end (cul-de-sac), you must not draw a roundabout at the end of the segment.
Ah, ok, so that's what it means. I was kind-of confused about the term. Thanks for explaining it!tonestertm wrote:SuperDave, the tool highlights when an overzealous or point-farming editor has erroneously placed a roundabout in the round end of a cul-de-sac. We have a Level 4 editor out here who loves to do this.
So, if I understand correctly, this will basically highlight a roundabout that only has one road sticking out of it?
Side note: You'd think that a Rank 4 would know better than that by the time he/she makes it that far....
https://j.mp/2X5xt19https://bit.ly/379DGR1https://j.mp/1A1VFerhttps://j.mp/1KDY3hbhttps://j.mp/3aYJWY5https://bit.ly/3jrDpM6
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Is the Junction Node Fixer that this toolbox relies on also going to be moved to the Chrome store before Google locks down being able to install plugins locally?
https://j.mp/2X5xt19https://bit.ly/379DGR1https://j.mp/1A1VFerhttps://j.mp/1KDY3hbhttps://j.mp/3aYJWY5https://bit.ly/3jrDpM6
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
The Toolbox isn't loading for me this morning. Doesn't even seem to be trying - I don't see the usual Chrome status message at the bottom that it's waiting on wazeteam.com, etc. I just checked and the loader extension is still there and enabled.....
Anyone else having this problem?
Anyone else having this problem?
https://j.mp/2X5xt19https://bit.ly/379DGR1https://j.mp/1A1VFerhttps://j.mp/1KDY3hbhttps://j.mp/3aYJWY5https://bit.ly/3jrDpM6
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Thanks.
Once again, this illustrates, really well, why the plugin itself should be permanently cached until there's a new version to be downloaded via the loader, or just drop the "loader" concept and put the plugin itself into the Chrome Store (which also lets it be auto-updated, albeit not as quickly).
Just sayin'.....
Once again, this illustrates, really well, why the plugin itself should be permanently cached until there's a new version to be downloaded via the loader, or just drop the "loader" concept and put the plugin itself into the Chrome Store (which also lets it be auto-updated, albeit not as quickly).
Just sayin'.....
https://j.mp/2X5xt19https://bit.ly/379DGR1https://j.mp/1A1VFerhttps://j.mp/1KDY3hbhttps://j.mp/3aYJWY5https://bit.ly/3jrDpM6
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Ok, fine, I can understand that. Then it needs to keep a local copy of what the loader downloads cached, and then if the loader can't contact the server for some reason, you've still got a working toolbox. Doing this would create even less of a load on that server, since the loader app would only have to actually download a new copy if there's an updated version or a change to your editor rank level.doctorkb wrote:SuperDave,
I initially pushed for this as well, but Oyyo has incorporated certain features that aren't available to all editor ranks. If he put it out there in the webstore or other "public" area, it could be reverse-engineered to circumvent these restrictions.
There's a lot of people using this Toolbox app. Having them all rely on a server to get the app each time they want to use it (AKA, a single point of failure) creates a lot of headaches for those who use it. It's extremely aggravating to be trying to do map edits and have a tool that you rely on just suddenly disappear or stop working.
As illustrated every time the server goes down or other reasons for things like this happening.
Seriously. It needs to be made "server fault tolerant." Keeping the last downloaded version cached and only downloading when a new version is available (or the cache gets wiped for some reason) would go a long way towards accomplishing that.
https://j.mp/2X5xt19https://bit.ly/379DGR1https://j.mp/1A1VFerhttps://j.mp/1KDY3hbhttps://j.mp/3aYJWY5https://bit.ly/3jrDpM6
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Now, if only we could get OyyoDams to agree with it....
https://j.mp/2X5xt19https://bit.ly/379DGR1https://j.mp/1A1VFerhttps://j.mp/1KDY3hbhttps://j.mp/3aYJWY5https://bit.ly/3jrDpM6
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Except when it doesn't work at all.OyyoDams wrote:It's not just a question of "yes or no". Some of magic features of Toolbox need this external hotsing. Besides, I've already tried to cache the code and the result was a nightmare. So for now it works better like that.SuperDave1426 wrote:Now, if only we could get OyyoDams to agree with it....
But I see your point. It's a shame that it's designed in a way which requires something like a server which can go down or otherwise become unreasonable. Admittedly, it's been a LONG time since I slung any code, but designing something in a way where such a small thing can bring the entire thing down for everyone was always something that was to be avoided whenever possible. So I naturally have a dislike for this particular system that you've come up with. No criticism intended, I'm just thinking out loud. But given what you're doing with it, I see the reasoning.
I still don't have to like it, though.
Well, here's to hoping that server meltdowns are few and far between! Thanks for the explanation!
https://j.mp/2X5xt19https://bit.ly/379DGR1https://j.mp/1A1VFerhttps://j.mp/1KDY3hbhttps://j.mp/3aYJWY5https://bit.ly/3jrDpM6
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
+1fred-porto wrote:A new bug is found with the new editor's CHAT function.. at least with Chrome!
Toolbox cant handle the change of zoom level if the CHAT panel is open... roads becomes static while imagens are zoomed in or out.
If toolbox is disabled, zoom is ok.
Fred
https://j.mp/2X5xt19https://bit.ly/379DGR1https://j.mp/1A1VFerhttps://j.mp/1KDY3hbhttps://j.mp/3aYJWY5https://bit.ly/3jrDpM6
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Nevada Wiki Places Guidelines Parking Lot Guidelines
Re: [script] WME Toolbox