Steve and John,
Too bad about no one knowing how to call an element’s line weight. That would definitely help us push the graphics along for us all really quick.
Steve, how are you deciding how to apply the various shades of grey?
My current method divides the view depth into sections, filtering the list of elements into separate lists based on which section their location falls in, and applies an override accordingly. The stuff further back gets a light grey, the stuff in the middle a darker grey, and the stuff in the front no override.
This meets my needs for now, but I’m not satisfied with it yet. Specifically there are two big disadvantages I’m trying to address:
- When a line or sketch based element crosses from the foreground to the background it has a location that falls in the middle somewhere, so it is overridden to the setting given to the section it lands within. Adjusting my list management to take the lesser value based on the distance from the view plane will fix this, but that will take some time for me to rework things as i'm currently using the centroid or average point, not the nearest part of the element.
- Views which have a large distance between elements don't always tone the way I'd like. That is if we have a list of 0', 25', and 100' the first and second items fall in the first third and receive no override, but the last item goes full grey fade on me. I've modified the script to use a % and assigned a grey value accordingly, but as noted above the element.override nodes only allow for a single value.
Sadly, I'm guessing that I am less of a python wizard than John, and know that I'm years behind many other individuals who frequent this forum. In any case, I will be attempting to overcome my ignorance Sunday, and if by some miracle I manage to pull it off I'll be sure to post the python code here for everyone's benefit.