Avatar

Level 4

^this, exactly!

From my standpoint of usage, there are only two big roadblocks remaining. These are the last obstacles that stop eVars from completely taking over the world:

1. Workspace pathing

     a. It still uses a querying shortcut, so it doesn't compute correctly when hit based segments are used in workspaces.

          (this should be known to the product team already, I walked through it with someone back in Q4.  But I'd gladly demo it again to help achieve an accurate pathing tool in future versions).

     b. It doesn't have a post-processing option to 'remove repeated values', (Yet ! )

2. List variables are a limited quantity. (hopefully on the roadmap to allow more at some point)

Aside from these two items, eVars have really become the universally applicable/flexible variable type.