AlanOfTheBerg wrote:gerben wrote:His problem is the other way around
Time for me to take a nap.
Yeah, so I just tap escape. Not sure about the "quickly" part as it just stays there once I hit Esc. Or I just click Apply. But, Esc then tab 4 times gets you to Apply if we're staying close to the keys.
Another thing that would be AMAZING (and I'm secretly hoping I can already do this and just don't know it yet...) is select an entire street and be able to click w to enable all turns at the junctions. I am in the process of dang near re-doing an entire city due to the unknown/one way roads that are in reality two way roads enabling all junctions in-between. If there is a way to enable these junctions without having to click on each one individually and then hitting w, PLEASE let me know
AlanOfTheBerg wrote:Bug: Chrome/Mac: selection of any item in an autofill list cannot be done with the mouse. This can only be done with the keyboard.
davipt wrote:invented wrote: I have to scroll down now to hit the 'Select All Segments'
Ctrl-a or cmd-a is your friend.
For the scrolling and tab issues just use Firefox (or Safari) instead of chrome for a while
the app doesn't even update a tile until you route over it so it's pretty moot.AlanOfTheBerg wrote:mike-bronner wrote:If we're speaking of graphically drawing things out, the browser is already doing this. The server just sends the raw data about the objects (coordinates, basically), then the browser renders everything through SVG data. The selectable road object is actually separate from the road that you see. It is an invisible vector object that gets manipulated as you select it or hover over it.
Because all objects are essentially data, and not graphics, we can create nifty add-ons, like timbones' color hightlights script, that can manipulate segments.
The only graphics that the server servers up is the Bing imagery, which comes from Bing servers, so it doesn't present an additional load on the Waze servers.
We are saying the same thing I think. What we see visually for the road layer, is a png, aligned with the actual SVG layer. What I'd like to see is the SVG layer only to be loaded, and have the browser draw the actual visible layer too.
In terms of the browser save causing a tile refresh, that is a capability of the current infrastructure and was one of the major features of the upgrade the US got a few months ago, and the World got this past week.
However, we do not want it to happen this quickly, at least, not so the app can download it right away or by default. Can you imagine a tile being saved 20 times in 5 minutes and the app downloading the tile 20 times? That would crush both the infrastrucutre network bandwidth and kill our data plan limits. It may be able to do that, but before we do, we need better, more restrictive default app tile download behavior.
jasonh300 wrote:numbtrip wrote:So annoying it's soured the editing, and its also much too fiddly to try and select a road that is almost horizontal on the map, I have to keep adjusting my mouse precision just to try and select 1 segment.
This is a Firefox bug. Use Chrome.
If you're having loading issues on the NA server, try resetting your Cable/DSL modem. There hasn't been any type of editor outage this weekend. Not sure about the International server.