Working on a project where there are multiple ALG files for various reasons - some which are "necessary" while others were already setup this way before I joined the team. There is one ALG of Point Control alignments, another of Side/Crossing Alignments (which also includes curb return alignments). The main corridors are based upon still another ALG file.
The Point Controls all work no matter which ALG is active, but actually editing the Point Controls is like trying to tie you shoes while looking in a mirror. I am constantly having to change active projects so the alignment that the point control targets is in the active project.
Additionally, due to a number of secondary alignments, occasionally the bend in the section causes the template to find an point control alignment in the wrong location, resulting in a sudden extension of certain components in the template.
One particularly troublesome alignment is the one defining the proposed back edge of sidewalk. There are only two alignments that run the entire length of the project. I'd like to change the sidewalk component so the back edge point uses a style constrain instead of a point control. since not only will it locate an alignment automatically, but I can specify a +/- range. My thought is that this might stop the accidental location of a downstream sidewalk alignment when a secondary alignment bends the section. Also on cross streets, sometimes the left side finds the right side edge and visa versa. When this happens, the typical sections go absolutely bonkers.
Has anyone had similar issues and found the style constraint does work as long as the ALG is loaded, even if it is not the active project?