Home › Forums › eaDocX queries › Table sizes (Column widths, full table width) › Table sizes (Column widths, full table width)
Home › Forums › eaDocX queries › Table sizes (Column widths, full table width) › Table sizes (Column widths, full table width)
Another thought for you / clue for eaDocX
(extra info added)
On my current task I observe the following:
1 Tables that are simply output as a table of relationship attributes are complying with their column width definitions and text alignment in cell.
2 Tables that are defined in the same way, but are navigated to via RelationshipElement (to stereotype defined as table) are automatically resizing columns and using centred cell alignment.
Example structure:
Package
– FeatureGrouping (Object Type = Class) IS PARENT OF SystemFunction (Object Type = Activity)
– FeatureGrouping (Object Type = Class) IS PARENT OF Capability (Object Type = Class)
– SystemFunction (Object Type = Activity)IS PARENT OF SysUseCase (ObjectType = UseCase)
My FeatureGrouping profile outputs:
1. A table of the Name and Description of its SystemFunction children (WELL BEHAVED TABLE)
2. A relationship element (SystemFunction), which is defined to output inline only a table of the SysUseCase objects that have a trace relationship (mostly those in the tree but also some others) (BADLY BEHAVED TABLE)
3. A relationship element (Capoability), which is defined to output as a table (i.e. not inline). (WELL BEHAVED TABLE)
I will no doubt get further clues over the next few days, but thought this worth mentioning,
Heather
- This reply was modified 11 years, 2 months ago by Heather Wallace. Reason: Added exta info and clarification
Download a free trial
Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.
Download