Page 24 of 45

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Posted: Mon Nov 12, 2012 2:11 pm
by jasonh300
fotrik wrote:Jason, if something is wrong in one browser and working in another one, it doesn't automatically mean, that it's fault of the browser. If you don't have an evidence for your declaration, please never write such a dumb things.
The horizontal selection bug is well documented throughout the forums. It happens in Firefox. I've never seen any mention of the horizonal selection bug in Chrome. It's a Firefox issue.

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Posted: Mon Nov 12, 2012 2:39 pm
by jasonh300
fotrik wrote:OK, maybe I missed something but still don't see why it's a bug of the browser and not the editor.
It may be a bug in the editor, but since the editor is specifically written for Chrome, they probably aren't even looking at it. I encountered it when I first started editing and reluctantly switched to Chrome, and have never had a problem since. I use Chrome only for editing, so I don't have it loaded up with bookmarks or plugins that aren't related to editing or the forums.

The screen zoom level (Ctrl-0) is hugely important, regardless of what browser you're using because it screws up the zoom between what you see and where you click. That solves another 10% of the complaints. Now there's a potential issue with older routers choking on too many connections...caused by the editor, but it won't have any effect on people with newer or better equipment.

I can also see a huge difference in performance between my home computer, which is 8+ years old and only has 1 GB of RAM, and my work computer which is brand new and has 4 GB and a faster processor.

I run XP on both home and work machines...there's now 2 newer Microsoft OS's out there that may or may not be bug-ridden, plus a number of 3rd party Linux OSs and of course Macs.

There are so many variables, and certain combinations work perfectly and some may not work at all.

The one thing we know for certain is that the horizontal selection bug appears in Firefox.

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Posted: Tue Nov 13, 2012 2:23 pm
by jasonh300
xtago wrote:The waze editor doesn't work on firefox at all, for it to be able to used on firefox you need to install a chrome overlay that allows chrome addons to work in firefox.
No. That's Internet Explorer that requires the Chrome Frame, not Firefox. There is no such plugin for Firefox that I'm aware of. The only real issue I know of with Firefox is the horizontal selection bug, which was severe enough to make me quit using it.
xtago wrote:Allow for the A/B of a segment to be swapped around instead of spinning it manually or having to do the lot numbering backwards on a segment.
Swapping the segments around manually also reverses the speed data, which means total corruption for a one-way street. Someone did that to some segments around here and the one-way streets have speed data for both directions now, which is starting to cause problems.

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Posted: Tue Nov 13, 2012 6:43 pm
by jasonh300
Davipt, I've been seeing something similar to that for a while.

When you hover over segments they turn blue, but if you don't click on them, they normally turn white again as you move the mouse away. Sometimes, the blue will stick though, and other than the lack of the A/B, they appear to be selected. If you sweep the mouse pointer over a false-selected segment, it will usually turn back white.

When multiselecting, I always seem to end up with one or two segments that look like they're selected, but they're really not. In my case, it doesn't necessarily happen when zooming. This bug has been around for a long time and it happened in both Firefox and Chrome. It's a lot more obvious now that we have the A/B, and I'm so used to working around it, I never thought to report it.

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Posted: Tue Nov 13, 2012 8:51 pm
by jasonh300
It's also possible that this new behavior is unique Int'l editor then. We've had the new infrastructure in place for several months. iainhouse, are you also using Firefox, or something else?

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Posted: Thu Nov 15, 2012 12:15 am
by jasonh300
skbun wrote:Try this, because it doesn't seem to help whether landmarks in view have names or even addresses: just turn your landmark layer off and work like that.
Now that I've seen your example, I remember that this happened to me the day they enabled the new Landmark functionality. There was some discussion in the forum that day about it and that turning off landmarks layer prevents it from happening.

I haven't had my landmarks layer on since then, so I'd forgotten completely about this since it hasn't happened to me again.

I'm going to forward your error code that you posted to the appropriate department.

Thanks for the details!

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Posted: Thu Nov 15, 2012 12:21 am
by jasonh300
davipt wrote:In my case zooming out or in or taking layers out doesn't solve it. And it's no extra script either. There is a javascript error (I've posted both on Firefox and Safari) and from that point on the javascript login is broken and only a refresh will solve it. I'm sure with the javascript error lines they can easily solve this. And I'm pretty sure this is a bug introduced days after the launch of the new version.
While I was testing it just now, simply turning off the landmark layer didn't fix it for me. But once I turned off the Landmark layer and did a permalink, I couldn't get it to happen again.

Is that not the case for you?

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Posted: Tue Nov 20, 2012 12:38 am
by jasonh300
The thing with the geometry node sticking to the mouse pointer has been around for a while, but now, you can click multiple times and it still won't let go. It also seems to do it a lot more frequently under certain circumstances, and it does seem to have something to do with rapidly trying to select multiple segments. I found that hitting Escape will get rid of it sometimes, and sometimes it will do it on its own. This is an extremely frustrating bug.

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Posted: Thu Nov 22, 2012 10:48 pm
by jasonh300
Unknown cannot be selected on heavily traveled segments. This is global and it's been like this for a few months now.

Re: Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Posted: Thu Nov 22, 2012 10:56 pm
by jasonh300
mssusa wrote:
bz2012 wrote:I submitted a report to support along with a link to our conversation.
Had something like this for a while in the intl server in my last session (3 hours until a few minutes ago). No more unknown type available and the direction arrows in the drop down list were displayed as html escape codes for special characters.
The arrows are fixed now, but I haven't paid attention to the Unknown type.

Time to sleep :(
Yeah, I saw a screenshot of the weird coding in the support forum. That was a glitch, unrelated to the unavailability of unknown.