It would indeed seem that some of my images also no longer show up if they have BASE_LAYER set as the parent layer. They do show up the moment I change the parent layer though. Changing it to satellite_imagery seems to work fine. So that's at least a workaround for that issue. I suspect one of the layers got their name changed, causing the script to default to a layer behind the satellite imagery.
Belgium & Luxembourg Coordinator • Script Writing Community Coordinator
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
I didn't believe you at first, but that seems to be true
It seems to be caused by a difference in the order of layers. Normally, the base layer would always be the first layer, from which the script extracts the maximum amount of zoom levels. The layer that is now first only reports 16 zoom levels instead of 23, causing "number of zoom levels" - "current zoom level" to become a negative number at the level you usually adjust an image. Because that value is used in a multiplication, it flips what the actions do.
The solution will be to use W.map.getLayersBy("isBaseLayer", true) to retrieve the base layer instead. I'll try to free up some time later today to fix this.
It seems to be caused by a difference in the order of layers. Normally, the base layer would always be the first layer, from which the script extracts the maximum amount of zoom levels. The layer that is now first only reports 16 zoom levels instead of 23, causing "number of zoom levels" - "current zoom level" to become a negative number at the level you usually adjust an image. Because that value is used in a multiplication, it flips what the actions do.
The solution will be to use W.map.getLayersBy("isBaseLayer", true) to retrieve the base layer instead. I'll try to free up some time later today to fix this.
Belgium & Luxembourg Coordinator • Script Writing Community Coordinator
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
Version 1.4.10 is out now, with the aforementioned fix for resizing the images.
Belgium & Luxembourg Coordinator • Script Writing Community Coordinator
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
I'm personally not seeing any issues in either production or beta, at the moment. I presume the userscript still loads, but no longer shows any images?
Could you check the console log for any error messages concerning this script? If the IndexedDB instance of your browser has become corrupt (which would be most likely if the script still loads fine), I somewhat doubt it'll be possible to recover any images.
Could you check the console log for any error messages concerning this script? If the IndexedDB instance of your browser has become corrupt (which would be most likely if the script still loads fine), I somewhat doubt it'll be possible to recover any images.
Belgium & Luxembourg Coordinator • Script Writing Community Coordinator
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
Indeed, that is exactly why I wrote that export function. I have an open task to add a bulk import/export that uses zip files, but don't expect this any time soon.
Belgium & Luxembourg Coordinator • Script Writing Community Coordinator
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
Ah, indeed. I'll have to change the default layer there. As a temporary workaround, you can manually change the parent layer of the image overlay so it appears on top of that imagery by editing the image overlay.
Belgium & Luxembourg Coordinator • Script Writing Community Coordinator
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
Version 1.5.0 has been released, which places the image overlay just underneath the roads layer by default and adds an extra option to always place the layer there, instead of having to pick a specific layer to target.
Belgium & Luxembourg Coordinator • Script Writing Community Coordinator
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
The whitespace in the sidebar seems like an easy issue to fix: the WME's "hidden" CSS class no longer contains display:none, so that whitespace doesn't collapse any more. The version I've just deployed should fix that.
I'm not certain that this is also going to be the cause of the other issue, but I'm not having any more scrolling issues after changing that.
I'm not certain that this is also going to be the cause of the other issue, but I'm not having any more scrolling issues after changing that.
Belgium & Luxembourg Coordinator • Script Writing Community Coordinator
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
Weird, the WME update shouldn't have any effect on that. I don't think there is a lot I can do if the script seems to load fine apart from the missing images, I'm afraid...
Belgium & Luxembourg Coordinator • Script Writing Community Coordinator
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
I've just checked in both Firefox and Chrome and the recycling bin button to remove a mapped image is still present and functional. Could you provide a screenshot of the list of maps to show the issue you're experiencing?
Belgium & Luxembourg Coordinator • Script Writing Community Coordinator
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
https://www.tomputtemans.com/images/WazeBelgium.pnghttps://www.tomputtemans.com/images/WazeWMEbeta.png
Re: [Script] WME Image Overlays (1.4.9)