If there's an issue in URO+, I think it's better that Twister-UK fixes this instead of us making local changes. But I think URO+ is still working fine as before? As for URC: it's best to let the script author fix that issue, so I'm not going to give more details for now.
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
An issue was reported in my Tab Manager script as it somehow seems to trigger a negative spiral in the height of the options container. While it is completely unclear how Tab Manager could have that effect, I suspect it can be solved easily by not relying on JavaScript to calculate the height there, but just use CSS (flex works wonders for such layout issues).
More details can be found at viewtopic.php?f=819&t=168863&p=1754722#p1754722
More details can be found at viewtopic.php?f=819&t=168863&p=1754722#p1754722
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 suspected the script to base itself on another element with the class name "tab-content", but I couldn't find anything like that. Normally speaking the Tab Manager script should at no point be removing an element, it will only juggle the tab handles around a bit to make sure they stay in the same order. But that reuses the old element, so that shouldn't have an effect on other scripts.
Either way: I'd really advice to use CSS flexbox to style those elements. Then you don't even have to worry about how it looks when the window resizes. But it's your choice, of course
Either way: I'd really advice to use CSS flexbox to style those elements. Then you don't even have to worry about how it looks when the window resizes. But it's your choice, of course
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
Talking about changes...
Heads-up: this script will be affected by an upcoming change within the WME objects: W.location will no longer exist in the next (or one of the next) versions of the WME. This script seems to use W.location.code various times, see this sticky for more information.
Heads-up: this script will be affected by an upcoming change within the WME objects: W.location will no longer exist in the next (or one of the next) versions of the WME. This script seems to use W.location.code various times, see this sticky for more information.
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
One of my scripts seems to break URO+, but there's nothing I can do about it. This may be something that causes other scripts to break URO+ as well.
The script in question adds one or more map layers and may add or remove map layers while the user is editing. This causes the IDs of the map layers to jump up or down. URO+ relies on these IDs being static though, as the script stores these IDs as "global" variables (uroMCLayerIdx, uroTurnsLayerIdx) and doesn't always update them in time. The same can be said about the map controls (dteControlsIdx, uroURControlsIdx, uroProblemControlsIdx).
Instead it would be better to keep a direct reference to these objects, just like it is being done for the root container (uroRootContainer). This way any added, removed or reordered layers/controls will not negatively affect this script.
Should you wish to keep the indices in place for some reason though, you can also call the uroWazeBits function whenever any of these events are triggered by the W.map object: addlayer, removelayer and changelayer (the latter only if the value "property" of the event equals to "order").
The script in question adds one or more map layers and may add or remove map layers while the user is editing. This causes the IDs of the map layers to jump up or down. URO+ relies on these IDs being static though, as the script stores these IDs as "global" variables (uroMCLayerIdx, uroTurnsLayerIdx) and doesn't always update them in time. The same can be said about the map controls (dteControlsIdx, uroURControlsIdx, uroProblemControlsIdx).
Instead it would be better to keep a direct reference to these objects, just like it is being done for the root container (uroRootContainer). This way any added, removed or reordered layers/controls will not negatively affect this script.
Should you wish to keep the indices in place for some reason though, you can also call the uroWazeBits function whenever any of these events are triggered by the W.map object: addlayer, removelayer and changelayer (the latter only if the value "property" of the event equals to "order").
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
Just noticed a strange problem with selecting roundabout segments, it will only select 2 consecutive segments of the roundabout and it is random as to which two it chooses.
This is with the latest version of WME 1.4-206, UROverview Plus v3.4 and installed on Firefox beta v27.4 and OSX 10.91
This is with the latest version of WME 1.4-206, UROverview Plus v3.4 and installed on Firefox beta v27.4 and OSX 10.91
https://s.waze.tools/gc.pnghttps://wiki.waze.com/wiki/images/e/ed/AuSig.png
Austraila Wiki | CA: Australia
Austraila Wiki | CA: Australia
If you select CWL and scroll down to the bottom of the list you should see a "Remove Deleted" button. That will delete the deleted camaras from the list.gamasi wrote:Hi guys
Two cameras were deleted from CWL.
The URO+ does not show who deleted them and now I can not remove them from the list. The problem is that every time I enter the WME I get a notification.
Does anyone have a solution for this?
Thanks
https://s.waze.tools/gc.pnghttps://wiki.waze.com/wiki/images/e/ed/AuSig.png
Austraila Wiki | CA: Australia
Austraila Wiki | CA: Australia
Version 3.11.1 works for me
Mac OSX 10.9.3, Firefox v31(beta)
Mac OSX 10.9.3, Firefox v31(beta)
https://s.waze.tools/gc.pnghttps://wiki.waze.com/wiki/images/e/ed/AuSig.png
Austraila Wiki | CA: Australia
Austraila Wiki | CA: Australia
We all know how useful this script is in helping manage our editing areas and big thanks once again.
With the automated map problem process being run again we have the usual number of things the system has found.
A possible enhancement:
Is there any chance of being able to add the functionality to filter closed map problems by a specific editor?
If it is possible, could it also be able to filter the ones you have closed so you can then only see the map problems that others have closed.
This will help to find an editor/s who close the problems without actually solving the issue the system has detected. Then we are able to mentor them in what they could/should have done before closing the map problem.
With the automated map problem process being run again we have the usual number of things the system has found.
A possible enhancement:
Is there any chance of being able to add the functionality to filter closed map problems by a specific editor?
If it is possible, could it also be able to filter the ones you have closed so you can then only see the map problems that others have closed.
This will help to find an editor/s who close the problems without actually solving the issue the system has detected. Then we are able to mentor them in what they could/should have done before closing the map problem.
https://s.waze.tools/gc.pnghttps://wiki.waze.com/wiki/images/e/ed/AuSig.png
Austraila Wiki | CA: Australia
Austraila Wiki | CA: Australia
Thank you for adding this functionality so quickly3.36 tweaks the popup positioning, and adds an option to filter MPs if they were or weren't closed by a specific user.
https://s.waze.tools/gc.pnghttps://wiki.waze.com/wiki/images/e/ed/AuSig.png
Austraila Wiki | CA: Australia
Austraila Wiki | CA: Australia
Re: [Script] UROverview Plus v3.86 (20160729)