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
Cameron,
You might be better off taking a look at the actual Customizing Valve Callouts Documentation on how to best make your Callouts function within the system.
Customize Valve Callouts
The Webinar you watched should align with the link above a little closer, but please keep in mind, it is a few years old, and might have a few out dated processes, so the current written documentation should better serve you. The Cloud-Based blocks documentation is more of an overall explanation of the shift we made to cloud, and how this affects your customized blocks and all existing downloaded blocks that reside in your Land F/X folder. The note about putting "NEW" at the end of the file name is one simple example of what you can put, so other suffixes would be fine.
As long as you follow the guidelines in the link above, your callouts should respect all of Land F/X functionality. If you have any further questions feel free to reach out to us in a support ticket and we can help you from there.
How to submit a tech support ticket
You might be better off taking a look at the actual Customizing Valve Callouts Documentation on how to best make your Callouts function within the system.
Customize Valve Callouts
The Webinar you watched should align with the link above a little closer, but please keep in mind, it is a few years old, and might have a few out dated processes, so the current written documentation should better serve you. The Cloud-Based blocks documentation is more of an overall explanation of the shift we made to cloud, and how this affects your customized blocks and all existing downloaded blocks that reside in your Land F/X folder. The note about putting "NEW" at the end of the file name is one simple example of what you can put, so other suffixes would be fine.
As long as you follow the guidelines in the link above, your callouts should respect all of Land F/X functionality. If you have any further questions feel free to reach out to us in a support ticket and we can help you from there.
How to submit a tech support ticket
- Page :
- 1
There are no replies made for this post yet.
Contact
- Land F/X
Our software tailors AutoCAD® to the needs of landscape architects, irrigation designers, and other professionals. We automate your most tedious tasks and ensure accuracy, giving you more time to design.