CR - Define Partial TextStyles & DimStyles in dgnlib

I am looking for discussion on what you would think about the ability to create Partial TextStyles and DimStyles. If this was mixed with Tasks and Element Templates a administrator could build cusom tasks with individual tools to apply the partial styles to the active settings. If these Tasks and Tools could remain persistent in a separate tool frame from tasks, this could be a user definable "Active Styles Settings" Dialog / Toolframe. The outline of the tasks could be something like:

  1. TextStyle Settings
    1. Text Size
      1. Template (dgnlib)
        1. Heading 1
        2. Heading 2
        3. Heading 3
        4. Paragraph 1
        5. Paragraph 2
        6. Paragraph 3
      2. Leroy (dgnlib)
        1. 60
        2. 80
        3. 100
        4. 120
        5. 175
        6. 240
      3. Point (dgnlib)
        1. 8
        2. 10
        3. 12
        4. 14
        5. 16
        6. 18
        7. 20
    2. Text Aspect (dgnlib)

      1. Narrow (w=0.8*h)
      2. Standard
      3. Wide (w=1.5*h)
    3. Font  (dgnlib)
      1. Architectural
      2. Engineering
      3. Arial
      4. Romans
    4. Text Mask / Outline (dgnlib)
      1. None
      2. Mask
      3. Outline
      4. Mask & Outline
  2. DimStyle Settings
    1. Terminator Type (dgnlib)
      1. None
      2. Arrow
      3. Circle
      4. Dot (filled circle)
      5. Slash
    2. Terminator Location (dgnlib)
      1. Auto
      2. Inside
      3. Outside
      4. Outside - connected
    3. Units Control
      1. Archetectural (dgnlib)
        1. 0'-0⅛"
        2. 0'-0¼"
        3. 0'-0½"
        4. 0'-0"
      2. Engineering (dgnlib)
        1. 0.0000'
        2. 0.000'
        3. 0.00'
        4. 0.0'
        5. 0'
        6. 10'
        7. 100'
      3. Inches - Decimal (dgnlib)
        1. 0.0000"
        2. 0.000"
        3. 0.00"
        4. 0.0"
        5. 0"
      4. Inches - Fractional (dgnlib)
        1. ⅛"
        2. ¼"
        3. ½"
        4. 0"
  3. LineStyle Settings
    1. ...
  4. Multi-LineStyles
    1. ...

I know a lot of this can already be accomplished using Tasks. I don't like the need to duplicate setting like text sizes and aspect ratios for each font. My current work flow is to create one TextStyle dgnlib as a template with all of the Text Sizes necessary for one Template / Font..Then I copy that dgnlib and change the aspect ratio. Then I copy both and chge the font:

Arial.dgnlib (Arial-L60, Arial-L80, Arial-L100, Arial-L120, Arial-L175, ...)
Arial-Narrow.dgnlib (Arial-Narrow-L60, Arial-Narrow-L80, Arial-Narrow-L100, Arial-Narrow-L120, Arial-Narrow-L175, ...)
Engineering.dgnlib (Engineering-L60, Engineering-L80, Engineering-L100, Engineering-L120, Engineering-L175, ...)
Engineering-Narrow.dgnlib (Engineering-Narrow-L60, Engineering-Narrow-L80, Engineering-Narrow-L100, ...)

What do you think?

- Roy

 

 

 

  • Some supporting posts from other threads:

    Roy Gallier:
    I think TextStyles could become more useful if they could hold as few as one or two attributes: say font or text height & width. Then we could apply more than one TextStyle. If there are overlapping attributes then the last one applied wins. 
    This concept is necessary

    Roy Gallier:
    I think I would like to have all the settings (for TextStyles & DimStyles) exposed during placement. What I envision would be a compact placement dialog (not the huge defination dialog) as now with tabs indicating the groups of settings. The tabs would activate daughter flyout pages for the individual settings. The Styles could then be relegated to managing the settings on each tab or section of settings on a tab. It seems to me that Element Templates would be better suited to group the individual settings or Styles together. If an individual setting is change for a tab then the Style for that tab is dropped altogether and the all individual settings are stored in the elemenent descriptor. The ET would allow for locating and selecting the placed elements and the granular Styles would allow for changing only the settings desired. 
    The GUI with tabs is not necessary if we use the Tasks GUI. Although it would be nice to have this as a separate, persistent & dockable task.

    Roy Gallier:
    I would like the Annotation Scale to be part of one of the many Styles which could be applied. The AnnoScaleStyle could also include an edit about point and some drawing scale ranges to: allow scaling, freeze scaling, max. scale, min. scale, & hide element.
    I think managing the edit-about-point (also scale-about-point) separate from the justification is very important. I think the text visability / scale control fits very well with the way MicroStation handles referance text with AnnotationScale; this would be a control like Scale Manager .

    Roy Gallier:
    MaryB:
    While we're at it, adding some sort of toggle for "Background" would be REALLY helpful, too.
    I second that and add Outline or better yet Text Frame like Place Note.
    I discuss this as well as other  enhancements in my Text Nodes / Notes  thread.

  • Roy,

    here's my setup I use since Annottaion Scale was presented in MS. I have only 2 dimension style set for Annotation Scale -- general and small one. I have 4 text styles set for Annotation Scale -- heading 1, heading 2, general text, small text - I'm using simple windows-delivered TTF fonts so they look same on every other computer

    I set up 2 Templates - one for dimensions and notes, another one for text. I haven't yet fully tested the detailing tools

    all geometry is in design model(s) and all the text, notes, dimensions ... are in sheets with Annotation Scale. I do not use any text in design model

    this works fine for all my work

    p.

    /pt

  • Peter,

    We use nearly all combinations outlined. This results in very unwieldy TextStyle & DimStyle selection boxes with all styles displayed. Choosing custom tasks defined for each makes this much more managable. It would be even more manageable if we could mix and match parts of the style definitions.

    - Roy