As best I can tell from observations, if you ‘click’ within 1 snap radius of a node, the node will be selected. The same should happen if you are within 1 snap distance from a segment.
It seems to me that if you are within 1 snap distance of multiple objects, the priority seems to be
nearest node, nearest segment, in that order.
Does anyone have definitive information from digging into the program or having written it?
The “WME add on” appears to allows you to CHANGE the snap distance from the default so that you can ‘taylor’ the editors snap behavior to your taste. Again, if someone has different information, please chime in. I am just guessing.
Is there a Script tool (like the Suppress Extra Junctions) that accomplishes this, i.e. fixes the ends of segments viewd within the screen? At least the End Node Fix?
Request for a minor change to the “Open in” functionality.
Is it possible to have the links always use the same browser window/tab, rather than having a new one created each time? For example, if I use the “Live Map” link it will open in a new tab. If I then use the link later without having closed the first Live Map tab, I will get a second Live Map tab.
From a quick look at some Javascript documentation for window.open, the second parameter name specifies the window name. Perhaps you could use the name of the link in here to persuade tab re-use?
I assume you mean to re-use the same tab that was used for the previous “Open in…”, and not the same tab as WME!
Even so, I can think of many times when I have wanted to use the “Open in…” feature for more than one location at a time. This change would mean that I would first have to go to the first page and open the permalink in a new tab, if I didn’t want to lose it when opening the second. As it stands, if I don’t care about an earlier tab it’s easy enough to close it manually.
That is what I meant. If others would find the change inconvenient, I certainly wouldn’t mind being turned down.
Alternatively, “re-use tab” could be a customisable option, but I understand that that would not be as simple: storage for the option, UI to set/change it, code to accommodate all that. I’d still like that option, but I won’t shed any tears if gdu1971 has more important things to do!
Hello,
For now, I’m trying (when I have time) to fix several things reported to the bug tracker and to build a new stable minor release.
There is also some independent plugins to WME Add-Ons under construction (yes it is possible).
For example, a script for level 5 users which is able to create a node for each intersection of selected segments (thx enhket for the idea). Ideal for new cities, just draw lines and click “node maker” to create all nodes.
The tabs management improvment you are requesting will probably lead into specific coding for client (ff or chrome) and I want to avoid it if possible…
I’ll check and let you informed but sure not in the top priorities of the moment , sorry…
BTW, your contribution is welcome, if you can, don’t hesitate to submit some piece of code and why not, take the lead of this project…
regards,
Gilles
By fortunate coincidence, I passed the 200K mark yesterday. That’s means I’m eligible for level 5 and country-wide rights. From now on points don’t get me anything and I’m only working for my own satisfaction at helping out others - and what better way to do so than by contributing to a script?
I assume that, when you say “lead of this project”, you mean the bit about re-using tabs? Taking the lead for WME-Addons with my level of skill would be an insult to everyone else. :shock:
As it happens, I used to be a programmer, although the amount of Javascript I’ve done is minimal. I’ve probably done more FORTRAN on punched cards! So i’m giving it a go. In fact, I’ve been working on it for nearly 2 hours - and I was supposed to go home 2 hours ago. That sort of thing is partly why the wife divorced me.
I’ll let you know if I can get some working code together.
Would it be possible to create a ‘Landmark list’ like ‘segment list’, which lists all landmarks in view and city/state/country when applicable, with the ‘select’ button to fix them? This would be really handy to do basemap landmark cleanup in my area…
(In other words, basically: this is the same thing as ‘Segment list’, but for landmarks.)
Script doesn’t seem to be picking up the alternate names in the segment list. It just lists “Todo”. Does that mean you’re still working on it? i.e. To do list?