I would like to 'hatch' my bar chart vs depth and graphic log columns to show sections of core loss where applicable. I am having some issues solving the rules code on this in the background fill section of bar chart vs depth properties. The fill type(!symbol) I would like to use is Tile!x04.
Image 1: Current Output
Image 2: Desired Output. Note how the bar chart stops plotting while the area is 'hatched' but continues afterward.
I attempted doing this using a HasData function in the Output Condition but to no avail. Any help with this would be greatly appreciated. Thank you.
Many different ways to do this. However, I am unclear on what you want to use to trigger this. Ie. it could be the word "core loss" in the description field or remarks field (not the best since you are counting on the description to be typed exactly), could be a specific strata graphic symbol, could be entries in a specific core loss table, could be lack of an entry in a description interval, or lack if data in the bar chart, etc. Please clarify.
I was able to create the graphic desired by overlaying a graphic vs depth entity over my bar chart vs depth column. The graphic entity reads from a table containing the core loss data. My only issue now is the curve from the bar chart vs plot column still appears.
Is there a way to have the graphic entity 'sent to the front' as to be placed on top of the curve? Or is the simplest way to just to add a blank row at this interval to my bar chart data table? Ideally, I would like to avoid the second option as this template will be used for other datasets with core loss in different areas. Any help is appreciated. Thank you.
This is one method to do it and I was going to work up an example, but now there is no need. To answer your question, all entities have a property called print order on the configuration tab. Higher numbers in this property plot on top (or in front) of entities with lower print order. All you should have to do is increase the print order your graphic vs depth entity to 1 (default is zero so the bar graph is likely at a print order of zero). Now add a background fill of solid white to your graphic vs depth entity in the background fill tab which will block out the bar graph. If you want your scale lines to appear on top of the core loss X then you can add them manually rather than use the bargraph's lines and set their print order to higher than the graphic X.
As to your indifference. It is usually not a good idea to have the exact same information stored in multiple locations in the database. In your case you appear to have the core loss data in the description field of a strata table as text, the remarks table as text, and a separate core loss table. Reason is that if you need to correct it you have to correct it in 3 places. I would recommend keying your graphic "X" off the graphic code field in the same table as your description. You can create a material called Core_Loss and select that when you enter "core loss" in the description field. Then remove the core loss descriptions you have entered in the remarks table and get rid of the core loss table. An output criteria expression to print your graphic X would be something like <<IIf(<<Strata.GraphicSymbol>> = "Core_Loss",True,False)>>. Keying off the graphic symbol code in the strata table is more exact than typing in the word "core loss" because the user usually selects this from a drop down list.
Hope this helps