I'm finding that I'm making more use of the "notes" for an element in my diagrams. Either directly in the body of the element or as a linked Text Annotation/Note.+10
It would be useful to be able to add a "text break" in to my notes where everything before the break is shown in the diagram, and everything after is hidden.
At the moment I adjust the character length for notes showing in the body of the element (Feature and Compartment Visibility -> Element Notes -> maximum chars)
But don't have a work around for linked Annotation/Note.
Can I suggest using the notes for your summary and linked documents for complete documentation?Splitting causes maintenance problems. Also, at enterprise scale, there is significant blowout. We could do similar with tagged values, but found it didn't suit the needs.
This will automatically do what you are requesting, and have the further advantage of allowing tables, nested lists, etc.
With version 13 this becomes even better, as there is a docked window for the linked document.
Can I suggest using the notes for your summary and linked documents for complete documentation?
This will automatically do what you are requesting, and have the further advantage of allowing tables, nested lists, etc.
With version 13 this becomes even better, as there is a docked window for the linked document.
| The Date the Stack Test was conducted S5.5(a)(ii): [CR] Confirmation that the regulations were satisfied S5.5(a)(iii): [FU] Fuel Used for the Test S5.5(a)(iv): [MU] Method used to measure NOx Concentration S5.5(a)(iv): [RA] Identifier of Alternate Rule if used. The Replaced Rule(s) were identified as part of the application for the Alternative Rule, and therefore do not need to be provided again. S5.5(a)(v): [EI] NOx Emission-Intensity Schedule 5: Classification Report — Information Required S5.5 The following information respecting a test on the boiler or heater referred to in paragraph 34(1)(a) of these Regulations conducted to determine its classification NOx emission intensity: S5.5(a) for a stack test, S5.5(a)(i) the date on which the stack test was conducted, S5.5(a)(ii) confirmation that each test run of the stack test was conducted while the boiler or heater met the conditions set out in paragraphs 27(2)(a) to (e) of these Regulations, S5.5(a)(iii) an indication as to whether the type of gaseous fossil fuel that was combusted during that stack test was natural gas or alternative gas, S5.5(a)(iv) the method set out in subsection 28(1) of these Regulations that was used for the stack test to measure the concentration of NOx and, if an alternative rule as approved under subsection 113(1) of these Regulations to replace a rule set out in that method was used, an indication of that rule, as approved, and of rule it replaced, and S5.5(a)(v) the classification NOx emission intensity of the boiler or heater, as determined by means of the stack test; and |
Splitting causes maintenance problems. Also, at enterprise scale, there is significant blowout. We could do similar with tagged values, but found it didn't suit the needs.I expected you of all people to be all about splitting those fields. What you are asking for is in effect a way to split the single notes field into two fields with different behavior. Or put another way, to cram two different logical fields into one physical field. I don't think the training associated with doing that would be any more than the training to put in a magic marker to separate two fields.
Again, it's bout reducing friction for the (especially casual) users. We want to show them enough on the diagram to entice them to select the item and see the full detail. The functionality is almost already available, in the tool tips... All we are saying here is to use a predetermined marker to delimit the amount shown on the diagram. As Steve says, we can do it programatically but it's a hassle.
Paolo
Of course, it was just a suggestion.
In theory, theory and practice are identical, in practice.... :)Splitting causes maintenance problems. Also, at enterprise scale, there is significant blowout. We could do similar with tagged values, but found it didn't suit the needs.I expected you of all people to be all about splitting those fields. What you are asking for is in effect a way to split the single notes field into two fields with different behavior. Or put another way, to cram two different logical fields into one physical field. I don't think the training associated with doing that would be any more than the training to put in a magic marker to separate two fields.
Again, it's bout reducing friction for the (especially casual) users. We want to show them enough on the diagram to entice them to select the item and see the full detail. The functionality is almost already available, in the tool tips... All we are saying here is to use a predetermined marker to delimit the amount shown on the diagram. As Steve says, we can do it programatically but it's a hassle.
Paolo
Of course, it was just a suggestion.