![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: WEXP - Heading styles in tables Topic Summary: How to modify (remove) the heading style from tables Created On: 20-Apr-2007 05:20 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|||||||||||||||||||||||||
We have extracted views from multiple modules (29) into Word tables using WEXP. 1.1 Investigation Management (new)ffice
All we want to do is set the style of Object Headings (within tables only) to something like Normal Arial 20pt Bold. We created a separate module for the WEXP export, defined the WEXP View Name and WEXP Module View and tried setting the Paragraph Style on each of these objects to <Object Heading:20 pt Bold>. This did not work. (The manual refers to a DXL script for assigning styles to attributes, but we don't have a copy of this) Is there a simple way to set these styles? Don |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
You have to set the Paragraph Style to a format style existing in the Word Template. As an example, <InvalidTag Heading:Normal> always works, as the "Normal" format style per default exists in any Word Template/File. In your case, you could create a new style in the Word Template (Format -> Styles and Formatting; New Style), give it a proper name, e.g. TableHeadings and use this name in the Paragraph Style attribute.
The DXL script for assigning values to the Paragraph Style attribute can be found under "Tools -> Support Tools -> Edit Paragraph Style Attribute". Regards, Peter P.S.: Bizarre, I am writing "<" followed by "Object Heading", and the result displayed is "<" followed by "InvalidTag Heading"... Edited: 20-Apr-2007 at 08:59 by Peter Albert |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
Don,
You may not wish to change the Paragraph Style if the object is used elsewhere. What I tend to do if I wish to use a different style of text within a table is use the WEXP feature by specifying the style in the column heading of the extracted view. eg Investigation Management System Requirements:Normal Remember to save the view with this change. The colon and style are stipped off by WEXP. As Peter mentioned the style must exist within the template. - Martin ------------------------- - Martin |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
We really don't want to set the Paragraph Style in each of the 29 modules, as these objects are used for other things.
|
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
Have tried specifying the style in the extract module column heading (using :normal, so I'm sure it will exist in the .dot), but this does not seem to work. But this does not give me the result I'm looking for. Edited: 26-Apr-2007 at 07:03 by Don Inglis |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
It might just be a typo in your post, but the format style is case sensitive, i.e. :normal will not work while :Normal does. But you should have get an error message complaining that the style "normal" did not exist in the template.
Peter |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
Peter, Strangely enough I am getting 'Column Title' and 'Column Cell' |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
Don,
as for "Column Title", "Column Cell" and "Normal": My experience is that, if WEXP complains the styles do not exist, then they do not exist in fact. Again, it is important that you check the case sensitivity. That's why you don't have a problem with "Normal" (capital N), while in your original post you wrote "normal" (lower case n), which I expectes to raise a problem. I guess the same is true for "Column Title", it might be that you use "column title" in the Word template. But on the other hand, even if you get the styles' names correct, it still doesn't solve your problem ... You are right that the format style given in the View's column title is ignored for Object Heading. So here is another solution: You can export in the "book" mode of WEXP and create a WEXP template / bookmark consisting of one table row. In the columns you put the <<InvalidTag Heading>> <<InvalidTag Text>> <<ID>> after your liking and assign any formatting you like to them. If you assign the bookmark's name to the "WEXP Template" attribute, each object is exported into one table row and Word puts the rows together to build one table. It works, but has two disadvantages: 1) The settings are not View-specific, i.e. the settings of "WEXP Template" stay with the Objects. Therefore, if you export the module in a different view to a different Word file, you must have a matching WEXP template in the appropriate Word template file. 2) The export takes far longer, as for each Object the WEXP template has to be copied and pasted into the Word file. (For my little test module, exporting time was doubled compared to plain "table" export. But the result is just what you want) So yet another (ugly) solution would be to modify the "Heading n" format styles in the Word template, especially their numbering scheme. But then you have to define new format styles for the headings you actually want. Regards, Peter Edited: 27-Apr-2007 at 09:09 by Peter Albert |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
I've been following this thread from a distance -- I don't use WEXP -- but nevertheless I'd like to throw in an idea. I assume that the 'main' column is being exported. Would it make any sense to create a view with 'Object Heading' and 'Object Text' as two separate columns? Then maybe the style could be set separately on each column, which might go towards solving the problem.
OK. I'm now sitting well back from my computer, waiting for the flames to start... ![]() Paul. ------------------------- Paul dot Tiplady at TRW dot com TRW Automotive |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
Works like a breeze! I would just add one other suggestion: In the original post, Object Heading and Object Text are in the same table column, so I created a view with a Layout DXL column containing the following code
string d = obj."Object Heading" if (!null d) d = "{\\b " d "\n}" displayRich d obj."Object Text" "" This view combined with the format style in the view's column heading worked just fine. Sorry, no flame :-) Peter |
|||||||||||||||||||||||||
![]() |
Telelogic DOORS
» General Discussion
»
WEXP - Heading styles in tables
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.