Thanks guys for your responses so far. Every little bit more I can learn about this program is a help. Hugo - good point, a mapkey skipping a section would be easy enough to run several times in a row Kevin - #9 modeling, I think that's the only workaround I've found, but it doesn't always sove the issue (nor is it very clean!) #5 Detailing - I use the auxillary view to create removed section views, which can (per ASME Y14.3) have a scale. If you know of a better way to create this type of view let me know. David - #1- Well, at least PTC is aware of this, but them stating it is "intended" functionality is a bit of a cop-out (I'd call it "unfortunate but working as programmed"). There should be some workaround such as a function string(CG) (like excel's "address" function) which could be used in place of "CG", and therefore it would update with the coordinate system name change. But if this is easier in WF3 maybe it's a non-issue now. #2- Moving the red arrow can take an exorbitant amount of time in a lengthy model tree. I use a mapkey to activate the "insert mode" in both assemblies and parts (through edit>feature/component operations, the pre-WF functionality) so that I can put the insert arrow anywhere I want without dragging it, but once the insert mode is active, you can only cancel it, there is no choice to place the arrow somewhere else. So I am left with either cancelling and regenerating the part/asm, or dragging the arrow for 30 seconds or so through a long model tree to the next place I want to put it. Another analogy to excel - imagine if, to insert a new row, you had to drag a new one from above row #1? Not a big deal, until your spreadsheet has more than 10 or 20 rows. #7 - A UDF would probably work, but what if all the subsequent features are to be dependant on the first? #9, yes I wouldn't like to be the programmer trying to make this happen. But I still won't give PTC any slack here 
#10 - I'll have to play around with this, I though there was some reason I wasn't using datums on the fly here. #11 - Layers get me by for now, but they make detailing much more tedious in certain situations. I have some parts with multiple layers with one curve each, because I need to only show one curve in each view. If they were cosmetics, they could all be in one layer, and I could just erase the unneeded curves. Thanks for taking the time to help me out here.
#10 - I'll have to play around with this, I though there was some reason I wasn't using datums on the fly here. #11 - Layers get me by for now, but they make detailing much more tedious in certain situations. I have some parts with multiple layers with one curve each, because I need to only show one curve in each view. If they were cosmetics, they could all be in one layer, and I could just erase the unneeded curves. Thanks for taking the time to help me out here.
Rick You dont even have to run the mapkey multiple times, you can just create one that repeates the xhatch change. My mapkey runs the same function 20 times. (Covers most om my cross sections mapkey fh @MAPKEY_NAMEFix Hatch;@MAPKEY_LABELfh;\ mapkey(continued) ~ Select `main_dlg_cur` `MenuBar1`1 `Edit`;\ mapkey(continued) ~ Close `main_dlg_cur` `MenuBar1`;\ mapkey(continued) ~ Activate `main_dlg_cur` `Edit.psh_dwg_props`;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;#DONE;
mapkey fh @MAPKEY_NAMEFix Hatch;@MAPKEY_LABELfh;\ mapkey(continued) ~ Select `main_dlg_cur` `MenuBar1`1 `Edit`;\ mapkey(continued) ~ Close `main_dlg_cur` `MenuBar1`;\ mapkey(continued) ~ Activate `main_dlg_cur` `Edit.psh_dwg_props`;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;\ mapkey(continued) #NEXT XSEC;#ANGLE;#45;#SPACING;#VALUE;1;#DONE;
