Irrigation mainline sizing
By Rob Streza on Wednesday, 01 May 2019
Posted in Irrigation
Replies 3
Likes 0
Views 3.7K
Votes 0

We have our irrigation mainline sizing callouts customized so that they have a mask behind the text and also have an Oval around it to differentiate it from other pipe sizes.  All of these were modified and placed onto the following directory: ...\blocks\graphics\irrigation\callouts.  Everything had been working fine until a recent LandFX update.  I now notice that the new mainline callouts are pulling in a different block name for the callouts and that these aren't located in the old directory.

For example, the block name for the old 1" mainline callout is "LAFX-MAIN-1.0".  The new block for the callout is "LAFX-MAIN-I1.0".  

I'm guessing that these blocks are being pulled from the cloud.  We need these to pull from our parent directory that has our modified standards.  Can this please be fixed?

Rob,

 

if there are any of the legacy fallouts defined in a drawing, the system will continue to use those. 

Otherwise, it creates the new blocks on the fly. They use a different font setting than lateral sizes, so they can be easily distinguished. And they also can have a mask applied. So the only difference should be the lack of an oval, should you ever wish to consider them in the future. 

But until then, you’ll just need to be sure to have one of the legacy blocks somewhere in each drawing. 

 

—J

Jeremiah Farmer
·
5 years ago
·
0 Likes
·
0 Votes
·
0 Comments
·

So, I'm guessing that the work around to continue getting the ovals is to insert the old blocks into the drawing prior to doing a "mainline size" for the system.  If those "legacy" block are there and named as the new blocks, then it should look just like it used to???

Rob Streza
·
5 years ago
·
0 Likes
·
0 Votes
·
0 Comments
·

Not named as the new blocks. Just manually insert any song one of the legacy blocks, and the system will use those instead of the new style. 

 

—J

Jeremiah Farmer
·
5 years ago
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post