Since approx 2 days ago I've started to experience the problem related to PIE (version 2020.08.17.02):
When "Enable geometry modification options" is enabled, I cannot successfully select area places. After clicking the area place, the geometrical nodes appear for a second and than disappear. The place remains selected, but I cannot modify its shape.

JustinS83 wrote:

Horizon911 wrote:Since approx 2 days ago I've started to experience the problem related to PIE (version 2020.08.17.02):
When "Enable geometry modification options" is enabled, I cannot successfully select area places. After clicking the area place, the geometrical nodes appear for a second and than disappear. The place remains selected, but I cannot modify its shape.

Do you have the resize option enabled? This is the only time this "issue" is seen and the tooltip tells you exactly what is going to happen.

Hmmmm, you are absolutely right! Thanks! I used that feature couple of days ago, however I did not realize (and than completely forgot), it would have such global consequences. So I ended up with troubleshooting overall WME behavior incl. all scripts.
Any chance that related info could be more prominent?
(Or at least by having some visual warning + explanation somewhere in global PIE settings. )

Arnoniem wrote:However, since I installed the script, I keep having issues with WME, making segment and place selection impossible. It's like there is an invisible layer blocking access to everything underneath. Others have reported this as well, in the Benelux.

Does this happen across the entire map area, or only on one small portion? There is a bug in WME (reported to staff) associated with the Google Street View control. This means there is a 100x100 pixel area on the screen at all times that prevents selection of anything underneath it. This area starts in the top left corner, but moves around as you pan the map, resetting it's position when you change zoom. After a number of saves without refreshing the browser window, this area can also obstruct WME controls like zoom, my location and - ironically - the GSV control.

WME FixUI includes a "Show map-blocking WME bugs" function to make this problematic area visible, so you know where it's interfering.

Fantastic enhancement, Justin!

It's frightening how many awful photos are approved on places; a quick scan of my local area resulted in about 40% of them being deleted. Without this tool, those approved photos would probably never be seen as you would have to take the time to select every place on-screen and manually review all the photos. I reckon we can clear a massive amount of wasted data from the Waze servers and improve the quality (and therefore the reputation) of the photos that show up in the app.

Can I suggest a change for the new photo viewer? Prevent re-flowing of the image panels when deleting images.

I've encountered the following scenario several times. You have a row of pictures with one free space at the end. The next row down starts with a place with 2 pictures - so it's container panel is 2 images wide. You intend to delete both of those pictures. You click the trashcan icon on the first picture and that panel shrinks to one picture wide. It immediately re-flows into the gap on the previous line and the next image panel in line jumps to the start of the line you're working on. If you're not careful, you can end up deleting that next image instead of the one that has now jumped up to the previous line.

I hope that makes sense: if not, I'll have to work out how to make a video of it.

I do realise it will leave gaps - and indeed, I'm guessing that the re-flowing is native behaviour and you'll have to put something in there to force the gaps to remain! However, the gaps will only start to appear when pictures have been deleted and they obviously won't re-appear if the picture browser is closed & re-opened. And they do only need to be at the end of lines, to prevent the something on the start of a line jumping onto the previous line.

I'm just thinking it would be worth the untidy appearance for the usability benefit. But if my guess above is correct, I also understand that it may not be simple to do.

And just as you post an update, I have an improvement suggestion.

On my first run through my local area, I deleted a lot of photos, but there are still hundreds left. If I come back to check again in a week or two, I'll be searching through a lot of good photos to find a few bad ones.

Is it possible to implement some sort of date filter? So that I could show, say, all photos since 1st December.

I'm also mulling the possibility that I might want to compare the new ones to the existing ones. So maybe the filter could put a different border colour around the "filtered" photos?

I suspect the problem is that the default font size for the main body of WME wa changed a couple of releases ago. Although most elements of WME define their font-size explicitly, there are a few things that depend on the body font-size. This is currently 14px and I suspect it must once have been smaller than that. Reducing that size seems to fix several problems I've seen, including the scroll bars on PIE.

I've already incorporated a specific font-size setting for the side-panel to override this change - it will be part of the next release of WME FixUI. But I haven't changed the font-size right up at the body level, because it could have multiple effects in other places.

Setting a font size of 13px on the photoViewerMainDiv div seems to fix the problem.

(Very minor) Bug Report.

The X icon to close the "edit geometry" window is AWOL. The parent div ID is pieViewEditGeom and the icon you're using is the Font Awesome fa-window-close. Replacing that with fa-close seems to work.

You could use class waze-icon-close, but you'll probably have to fiddle with the font size/weight.

JustinS83 wrote:

iainhouse wrote:(Very minor) Bug Report.

The X icon to close the "edit geometry" window is AWOL. The parent div ID is pieViewEditGeom and the icon you're using is the Font Awesome fa-window-close. Replacing that with fa-close seems to work.

You could use class waze-icon-close, but you'll probably have to fiddle with the font size/weight.

Works for me in production and beta

Strange, indeed! Still missing for me in Beta and Production - but not in anonymous mode (i.e. no scripts).

Digging even deeper, it looks like some other script I'm using may be loading a version of FontAwsome for itself. Apart from some FA CSS I can see in the native WME, my sources tab tells me I also have FA loaded from use.fontawesome.com. Within that source is some CSS that is killing the icon. If I disable that line, the icon appears.

So I guess it's not a problem with PIE. I guess some other script is loading a different version of FontAwesome. I've no idea how to find out which one, other than by spending time disabling scripts - but at least it's a minor problem!