I want to save my office standard Valve Callout as a block to use in all of our projects, but I am confused on the suggested methodology.
The "Customizing Irrigation F/X" webinar from 2014 recommends editing and saving over an existing source file, while the more current documentation titled "Cloud-Based Blocks and Hatches" suggests saving edited F/X blocks with -NEW at the end of the filename/s (.dwg, .sld, and .xml). Are one of these options preferable for valve callouts, or any other blocks that we want to maintain dynamic capabilities?
I've read that the Cloud Based Block library allows users to choose what files are downloaded with each update. If this is true I'm not concerned with our custom blocks being overwritten with an update. I am more concerned with whether or not our new valve callout will have the same dynamic capabilities as the standard F/X blocks...?
Thanks in advance,
-Cam
The "Customizing Irrigation F/X" webinar from 2014 recommends editing and saving over an existing source file, while the more current documentation titled "Cloud-Based Blocks and Hatches" suggests saving edited F/X blocks with -NEW at the end of the filename/s (.dwg, .sld, and .xml). Are one of these options preferable for valve callouts, or any other blocks that we want to maintain dynamic capabilities?
I've read that the Cloud Based Block library allows users to choose what files are downloaded with each update. If this is true I'm not concerned with our custom blocks being overwritten with an update. I am more concerned with whether or not our new valve callout will have the same dynamic capabilities as the standard F/X blocks...?
Thanks in advance,
-Cam