Layers Bob, put the big items on a different layer, can just use a temporary one, lock it and you can move the smaller items around easily, you can also hide the temporary layer if that makes it easier.
For a new route, or a single route, I would not mind doing that, but I have
no intention of going back to and having to re-do all
14 of my routes just to accommodate the fact that N3V
broke the ability of the mouse to be able to
precisely discern objects and are only letting us know they did it because I brought it to light and documented it here in the forums and forced the issue.
I am not sure that some of you understand the full impact of this. Much more then the industries are involved here. To accommodate this issue I will have to:
1. Move every industry that is near any large object to another layer.
2. Move any other object that I might wish to move, identify or configure that is near another larger object to another layer.
3. Replace existing industries that have large foot prints, with different ones, or carve up existing ones to make more modular smaller foot print ones because smaller objects cannot be over laid on them.
4. Move any small object that is overlaid on a larger object to another layer. If you overlay a smaller scenery object on a larger scenery object you will find you no longer have the ability to identify, move or adjust that item since the mouse pointer will only be able to detect the larger object. I have had to grapple with this many times already in my attempts to upgrade my T:ANE routes to TRS19 standards. The only stated solution for that is to move the smaller objects to another layer.
Have I got this list wrong here?
Also this issue effects almost every older route brought into TRS19 by users, including many routes created by authors long gone, or those not willing to upgrade them. This will put the burden on the users to have to fix those routes in many cases.
From N3Vs perspective and statement, it is not a bug, but a feature, but it impacts all of us freeware content and route developers by forcing us to have to re-do what they break. Of course that is entirely their prerogative for their product, but it is my prerogative to go the direction I indicated earlier, which I am going to do.
Bob