Volian/SourceCode
8
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Backed out (for now) the fix to initialize MS Word sections if the document style didn’t specify a font.- because it caused problems with Westinghouse data

Browse Source
This commit is contained in:
John Jenko 2013-03-12 17:47:22 +00:00
parent 5379743193
commit f0bb7a73c2
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
PROMS/Volian.Controls.Library/DSOTabPanel.cs
View File

@ -220,8 +220,12 @@ namespace Volian.Controls.Library
if (MyDocumentInfo.Config == null || MyDocumentInfo.Config == "")
{
DocStyle ds = MyDocumentInfo.DocumentEntries[0].MyContent.ContentItems[0].MyDocStyle;
if (ds.Font.Family != null) doc.Application.Selection.Font.Name = ds.Font.Family;
if (ds.Font.Size != null) doc.Application.Selection.Font.Size = (float)ds.Font.Size;
// this will cause an error and goto the Catch if the family or size is null,
// Westinghouse needs it to to this - at least for now
//if (ds.Font.Family != null) doc.Application.Selection.Font.Name = ds.Font.Family;
//if (ds.Font.Size != null) doc.Application.Selection.Font.Size = (float)ds.Font.Size;
doc.Application.Selection.Font.Name = ds.Font.Family;
doc.Application.Selection.Font.Size = (float)ds.Font.Size;
doc.Application.Selection.ParagraphFormat.SpaceBefore = 0;
doc.Application.Selection.ParagraphFormat.SpaceAfter = 0;
doc.Application.Selection.ParagraphFormat.LineSpacingRule = LBWdLineSpacing.wdLineSpaceExactly;