Hi there,
Just my comment. It seems a similar question has been asked as to the 'order of operation' and priority of command execution. This one example of many examples shows how the same setting can be defined in several different places within the same tool and in several different places using different tools. I am getting suspect that ACE has never published (to my knowledge) something like a drawing tree showing the hierachy of priority because there might not be a hard fast rule. I am thinking of building a block with multiple attributes. When the finished block is inserted into a drawing the order the attributes are listed from top down are in the order the attributes were selected when building the block. The list can be ordered anyway you want, it entirely depends on the order in which they were selected. This leads me to wonder if the setting defined in different places have their priority set by some order of operation that is driven by which tool setting ACE looks at first/last/in-between. That would explain why there is no tree, this would be more like a flow chart that can change in sequence depending on who is selected when. The winning could be driven by the .env file or the Project Setting, it would just depend on the order in which they were select by the ACE wheel of fortune? Just a random thoughts and way ward wondering for a Tuesday morning.
We know some of the order of operations. Such as we start with the ACE application setting for all drawings. We can override those by embedding settings into a template. We can adjust specific settings in the Project Properties and those settings can be overridden with the Drawing Properties. Other settings and who 'wins' so far are a complete enigma to me.
Have a great day
Please mark as a solution if this works for you, kudos are always welcome
