Formats

Forum Post: Re: Adding Multiple Images At Set Location

Dane Balia — Thu, 23 May 2013 12:09:00 GMT

Thanks found the answer on the site.

openxmldeveloper.org/.../inserting-an-image-into-a-bookmark-in-an-openxml-wordprocessingml-document.aspx

Forum Post: Re: Open Xml

julix12 — Tue, 21 May 2013 14:56:00 GMT

Cool. thanks :) http://linkapp.me/yTD5K

Forum Post: Require Help

pankajbaviskar — Sat, 18 May 2013 07:14:00 GMT

Hi,

I am new to OpenXml , my requirement is i want to develop a word document which having text, tables and chart in that. i had written code for that , when i open word it gives unspecified Error.

Forum Post: Re: How do I know the size of a specific piece of text in a work document?

jcordeiro — Fri, 17 May 2013 23:00:00 GMT

Dear Jim,

Let me add some additional information.

Regarding point 1: you're completely right about the text from the standard: it clear states that the default praragraph style should be applied if there is no paragraph style applied. On the other hand the information regarding the pstyle element states:

"If this element is omitted, or it references a style which does not exist, then no paragraph style shall be applied

to the current paragraph. As well, this property is ignored if the paragraph properties are part of a paragraph

style." (ISO/IEC 29500-1:2012(E - 17.3.1.27)

This is against the first statement!!!

For the character style (also point 2) the behaviour of word is like this:

I change the default character style within Visual Studio (VS), (in my tests I added run properties with just the bold property inside) and when I open word, it completes ignore my changes. Then I change something inside the run with that style and after saving the document, word replaces the default character style with the following style (the original character default style) removing all run properties from the style:

<w:style w:type="character" w:default="1" w:styleId="DefaultParagraphFont">

<w:name w:val="Default Paragraph Font"/>

<w:uiPriority w:val="1"/>

<w:semiHidden/>

<w:unhideWhenUsed/>

</w:style>

Also, as I said before, Word keeps all run properties information for a character style in that specific style. In this case is not necessary to roll up styles. A simple test I made is to define within VS the size of a font in the run properties of character style "styleA" and no size information for character style "styleBinheritingFromA". When I open word everything is correct within runs of both styles, but if I change something in the run with "styleBinheritingFromA" word changes this style with all information inherited from styleB that is missing. In this case my size property is added to style "styleBinheritingFromA".

José

Forum Post: Re: DocumentBuilder dont find file create in runtime

ClaudiaJS — Tue, 14 May 2013 20:16:00 GMT

Thanks for answer, I want to say. With three procedures, i do, three differents files, after, i combine these files just created with other files already existing in the server, but when I do this, the procedure "DocumentBuilder.BuildDocument", combine the files already existing in the server, but the three files, created before the execution of the procedure seems dont exist, and comes this error: "empty list error ". I see the files in the server, i can open the file and modify without problem.

I hope to be clear, I post the code for the generation of one file

Public Function GeneraFileArticoli(ByVal IdOffer As String, ByVal nomeCartella As String) As String

Dim IndFileArticoli As String = ""

Try

Dim nomeDir As String = ConfigurationManager.AppSettings("DirServer")

Dim TemplatePath As String = nomeDir + "\OpenXmlContent\ModelloGrid.docx"

Dim OutputPath As String = nomeDir + "\" + nomeCartella + "\" + IdOffer + "-Articoli.docx"

File.Copy(TemplatePath, OutputPath)

Dim db As New DBOfferteDataContext

Dim varOfferta = From prod In db.spDoc(IdOffer)

Using theDoc As WordprocessingDocument = WordprocessingDocument.Open(OutputPath, True)

Dim body As Body = theDoc.MainDocumentPart.Document.Body

'***************************************** TABELLA CON DATI **************************************

Dim mainPart As MainDocumentPart = theDoc.MainDocumentPart

Dim ccWithTable As SdtBlock = mainPart.Document.Body.Descendants(Of SdtBlock)().Where(Function(e) e.SdtProperties.GetFirstChild(Of Tag)().Val = "ElencoProdotti").[Single]()

Dim theTable = ccWithTable.Descendants(Of Table)().Single()

Dim theRow = theTable.Elements(Of TableRow)().Last()

For Each articolo In varOfferta

Dim rowCopy As TableRow = DirectCast(theRow.CloneNode(True), TableRow)

rowCopy.Descendants(Of TableCell)().ElementAt(0).Append(New Paragraph(New Run(New Text(articolo.Kit.ToString()))))

rowCopy.Descendants(Of TableCell)().ElementAt(1).Append(New Paragraph(New Run(New Text(articolo.Codice.ToString()))))

rowCopy.Descendants(Of TableCell)().ElementAt(2).Append(New Paragraph(New Run(New Text(articolo.Prodotto.ToString()))))

rowCopy.Descendants(Of TableCell)().ElementAt(3).Append(New Paragraph(New Run(New Text(articolo.Incluso.ToString()))))

rowCopy.Descendants(Of TableCell)().ElementAt(4).Append(New Paragraph(New Run(New Text(articolo.Prezzo.ToString()))))

theTable.AppendChild(rowCopy)

theTable.RemoveChild(theRow)

mainPart.Document.Save()

IndFileArticoli = docOutputPath

End Using

Catch ex As Exception

Dim Problema As String = ex.Message

End Try

Return IndFileArticoli

End Function

Thank's in advance

Claudia

Forum Post: Re: Can the Presentation Builder be used without the USING() { } Statement?

YasiduY3K — Tue, 14 May 2013 17:16:00 GMT

Hi,

I did a small modification to the presentation builder.

Instead of creating an output file from scratch (OpenXmlMemoryStreamDocument), i'm using PresentationDocument.Open() to create an existing file and clone files from another presentation to it.

The approach I took was, (PresentationBuilder modification),

(Base presentation denoted as B, to be cloned presentation is denoted as C)

Modify BuildPresentation() method to use B as the output file.

Use C as the SlideSource.

Comment out CopyPresentationParts() method as the output is not getting built from scratch.

The resultant output throws an error!

Base presentation:

ToBeCloned:

Error:

Output:

After some checking i found out that the two master slides has contains two separate layout slides with the same ID!

Issue:

After browsing through, for similar situations, I was able to apply the following as a fix.

In CopyMasterSlides(), at the end, use FixSlideLayoutIds() method to re arrange the layout slide id's.

A sample code with fix is attached as Post3.zip

Hope this will help any future enhancement of the PresentationBuilder code as well as anyone with a similar problem, while trying to experiment with its code.

Cheers,

YasiduY3K

Forum Post: Re: merging word-documents with DocumentFormat.OpenXml(c#)

Tennyson — Thu, 09 May 2013 09:18:00 GMT

Hi, i happened to used this word document merging sdk in c# to help my image programming work which includes the merge of two or more word documents, it works well, have a try. And, what's more, it also can merge pdf documents, which i thinks you maybe also need this source.

Forum Post: Using Custom UI Editor if statement when file name is .pptx

y0gster — Thu, 09 May 2013 08:47:00 GMT

i just found this Custom UI Editor while searching for a way to have an onload event on Powerpoint. Now I need is an if statement in the UI editor that would prevent it from running when the file extension is pptx. Here is the line of code im using in customui:

<customUI xmlns="http://schemas.microsoft.com/office/2006/01/customui"   onLoad="onLoadCode" >  </customUI>

I can write the code in vba but here in xml im totally lost. What I was thinking was something like this which I wrote in vba:

if right(filename,4) = "pptm" then  onLoad  ="onLoadCode"   end if

Forum Post: Re: Applying a Slide Master to a Presentation

YasiduY3K — Thu, 09 May 2013 04:35:00 GMT

Hi,

Aspose is faster. but they sucks!

I tried using Aspose for my projects, but they always throws out errors. I got errors with cloning, slidenumbering, powerpoint object formatting etc.

May be it's because of the earliest version of their PPTX version, but I was ultimately fed up providing them sample codes to clarify the issues and waiting for long ETA's till they come up with fixes.

But there powerpoint 03 version is really good.

My advice is stick with openxml, even u encounter an issue, you will have a code base to work it out.

Forum Post: Re: Removing images from a PPTX (and not breaking any relations)

Eric White — Wed, 08 May 2013 17:50:00 GMT

You will be amazed at how fast it is, though. Once you write the correct code, it still will operate nearly instantaneously.

Forum Post: Re: Copy SlideMasterlayout element into the Slide

Eric White — Wed, 08 May 2013 17:46:00 GMT

Hi,

I've put together a PresentationBuilder resource center (openxmldeveloper.org/.../presentationbuilder.aspx) that contains a link to download the code, as well as links to the various screen-casts that you will want to watch. You can learn a lot about PresentationML if you watch those screen-casts.

Best, Eric

Forum Post: Re: newMasterPart.SlideMaster.Preserve = false, is not working

Eric White — Wed, 08 May 2013 11:42:00 GMT

Hi, I'll take a look at this tomorrow.

-Eric

Forum Post: Re: The presentation builder corrupts a presentation

YasiduY3K — Wed, 08 May 2013 10:03:00 GMT

Thanks Eric

Cheers, Yasiduy3K

Forum Post: Re: Tricky: MS Word vs Google Docs: Numbering starts at 2 whilst w:start w:val="1"/

Eric White — Mon, 06 May 2013 16:31:00 GMT

Hi,

You are absolutely right, numbering is tricky. Some time ago, I wrote an article on MSDN that details exactly how numbering works:

msdn.microsoft.com/.../ee922775.aspx

Further, I wrote a module, ListItemRetriever.cs, which is part of PowerTools for Open XML, which retrieves the "List Item" for each and every paragraph, if the paragraph has a list item.

I was going to run ListItemRetriever on your document, but it looks like the document that you attached is empty. But I put together the same example, and ListItemRetriever returns the correct values. My document looks like this:

The code to exercise ListItemRetriever.cs looks like this:

using System;  using System.Collections.Generic;  using System.Linq;  using System.Text;  using System.Threading.Tasks;  using DocumentFormat.OpenXml.Packaging;  using OpenXmlPowerTools;    class Program  {      static void Main(string[] args)      {          using (WordprocessingDocument wDoc = WordprocessingDocument.Open("../../outlineNumbers_OpenXML.docx", false))          {              foreach (var para in wDoc.MainDocumentPart.GetXDocument().Descendants(W.p))              {                  string listItem = ListItemRetriever.RetrieveListItem(wDoc, para, "-");                  string text = para.Descendants(W.t).Select(t => (string)t).StringConcatenate();                  string line = string.Format("{0} {1}", listItem, text);                  Console.WriteLine(line);              }          }      }  }

When you run this example on the above document, it produces:

i)  i  ii)  ii  iii)  iii  2)  2. LOOK HERE  3)  3

If I recall correctly, I believe it works this way because there is an implied level 0 for those level 1 list items. But I can't recall exactly (It's been a number of years). If you go through that MSDN article in full detail, it will explain the issue, I believe.

When you build the example, you will need the following modules from PowerTools for Open XML:

ListItemRetriever.cs
PtOpenXmlDocument.cs
PtOpenXmlUtil.cs
PtUtil.cs

You can get those modules from the PowerTools core zip file at http://powertools.codeplex.com

Those modules are also, of course, in the larger package that you can use to build the cmdlets.

Best, Eric

Forum Post: Re: Is it possible to use Custom XML tags?

Eric White — Mon, 06 May 2013 16:13:00 GMT

Hi,

The best approach is to wrap your paragraphs with content controls. Take a look at this screen-cast:

openxmldeveloper.org/.../custom-xml-parts-and-content-controls.aspx

You also can look at this screen-cast with information about associating additional data with each content control:

http://blogs.technet.com/b/gray_knowlton/archive/2010/01/15/associating-data-with-content-controls.aspx

Also, if you haven't done so yet, I recommend watching the intro to Open XML screen-casts:

openxmldeveloper.org/.../introduction-to-open-xml.aspx

And also the WordprocessingML screen-casts:

openxmldeveloper.org/.../introduction-to-wordprocessingml.aspx

Cheers, Eric

Forum Post: Re: Embedded Excel spreadsheet in Word Document - cannot update data

Eric White — Mon, 06 May 2013 16:03:00 GMT

Hi,

Open XML does not have a class that can automatically update the image that is displayed for the embedded Excel workbook. You will need to generate this image yourself.

I have on my (long) list a project to generate a thumbnail for an Excel spreadsheet. There would be a number of options so that you could control this process. This is part of a larger project to do a bit of rendering of an Excel spreadsheet from the markup. Then, you could use this code to generate the thumbnail and update the image.

You may be interested in the following screen-cast, which discusses the plumbing of embedding an Excel workbook in a document, in detail:

openxmldeveloper.org/.../screen-cast-exploring-the-structure-of-embedded-spreadsheets-in-word-documents.aspx

I wish that I had a better answer for you, but I don't. You just need to create a new bitmap, write the graphics into the bitmap that you want, serialize that bitmap into the appropriate part in the word document, and then your embedded workbook with have the appearance that you want.

Best, Eric

Forum Post: Re: Grouping Excel rows using open xml

Eric White — Mon, 06 May 2013 15:35:00 GMT

Hi Ravi,

You certainly can group rows. I haven't yet seen any good examples on doing this with Open XML, but it is certainly doable.

One approach to use is as follows:

Create your workbook without any grouping
Save away a copy of the workbook
Copy to a new name
Modify the new workbook, grouping the rows, and doing nothing else other than grouping the rows.
Use the Open XML SDK productivity tool to compare the two files. You can then see exactly the markup that you need to produce in order to group rows.

If you haven't done so yet, I recommend viewing the introductory screen-casts on Open XML:

http://openxmldeveloper.org/wiki/w/wiki/introduction-to-open-xml.aspx

Also:

http://openxmldeveloper.org/wiki/w/wiki/introduction-to-spreadsheetml.aspx

While the following is on PresentationML, it is relevant:

How to Research Open XML PresentationML

Also view this video:

How to Research Open XML Markup

-Eric

Forum Post: Re: Multiple OleObjects (Linked Objects) are not getting merged properly using DocumentBuilder

Eric White — Mon, 06 May 2013 15:24:00 GMT

Hi Fenil,

I am going to commence on PowerTools 3.0 in a couple of months (it's going to be cool!). I will definitely address this issue with that version.

Cheers, Eric

Forum Post: Re: How does powerpoint link txbody formatting from the slide to a slidelayout/master

miktro — Sun, 05 May 2013 10:10:00 GMT

I found a very helpful page today (published on Feb 11 2013) listing many corrections and explanations of OOXML behaviour in MS Office.

msdn.microsoft.com/.../ee908652(v=office.12).aspx.

This lists 1873 pages of corrections to the OOXML specification - many of which directly contradict the specification.

The main implication of these pages seems to be that the OOXML specification cannot be relied on to determine the behaviour of a document when used by MS Office.

If you find a discrepancy it may well be that Office is not obeying the specification - or is using it's own defaults.

And if you rely on the specification to write conforming documents to be read by MS Office you may get surprising behaviour.

After spending over a month trying to determine default formatting values using the specification I am on the point of giving up as it seems that whatever I deduce may fail in future when implmenting a specific case that I have not compared to MS Office behaviour.

It seems one of the main purposes of the standard = to enable documents to be read in 10+ years when all related software has perished = is now invalid.

We will have to revert to scribing documents on parchment to ensure anything is readable in 1000 years.

Forum Post: Re: How to group several Shapes into a GroupShape Object

denlar — Thu, 02 May 2013 13:57:00 GMT

Hello again,

I found an ugly way to perform the grouping action. Since it's really ugly, if anyone suggest better code I will read it with joy

//Create an empty GroupShape          public GroupShape GetGroupShape(UInt32Value ui32)          {              GroupShape grpShape = new GroupShape();              NonVisualGroupShapeProperties nonVisualGroupShapeProperties = new NonVisualGroupShapeProperties(                      new NonVisualDrawingProperties(){ Id = ui32, Name = "Group "+ui32 },                      new NonVisualGroupShapeDrawingProperties(),                      new ApplicationNonVisualDrawingProperties()                      );              // Initialize dimension to 0,0 and position to 0,0              GroupShapeProperties groupShapeProperties = new GroupShapeProperties();              A.TransformGroup tfg = new A.TransformGroup(                      new A.Offset() { X = 0L, Y = 0L },                      new A.Extents() { Cx = 0L, Cy = 0L },                      new A.ChildOffset() { X = 0L, Y = 0L },                      new A.ChildExtents() { Cx = 0L, Cy = 0L });              groupShapeProperties.Append(tfg);                grpShape.Append(nonVisualGroupShapeProperties);              grpShape.Append(groupShapeProperties);                return grpShape;          }            //Grouping method          public GroupShape GroupAllShapes(IList<Shape> allShapes, IList<GroupShape> allGrpShape, UInt32Value idGroupShape)          {              GroupShape gs = GetGroupShape(idGroupShape);              int shapeCount = 0;              foreach (Shape s in allShapes)              {                  AddOpenXMLElement(gs, s, shapeCount);                  shapeCount++;                  //gs.;              }                foreach (GroupShape grpShape in allGrpShape)              {                  AddOpenXMLElement(gs, grpShape, shapeCount);                  shapeCount++;                  //gs.;              }                shapeCount++;                return gs;          }

Ok now the AddOpenXMLElement method has to add the Shape or GroupShape but also to keep the GroupShape dimension and position up to date :

// Add a Shape or GroupShape to the given GroupeShape          // Actualize the dimension & Position of the final GroupeShape          public void AddOpenXMLElement(GroupShape gs, OpenXmlElement shape, int shapeCount)          {                            if (shape.GetType() == typeof(Shape))              {                  Shape s  = (Shape)shape;                  gs.Append(s);                                    if (shapeCount == 0) //1st shape added => Initialization of the GroupShape properties                  {                      gs.GroupShapeProperties.TransformGroup.Offset.X = s.ShapeProperties.Transform2D.Offset.X;                      gs.GroupShapeProperties.TransformGroup.Offset.Y = s.ShapeProperties.Transform2D.Offset.Y;                      gs.GroupShapeProperties.TransformGroup.ChildOffset.X = s.ShapeProperties.Transform2D.Offset.X;                      gs.GroupShapeProperties.TransformGroup.ChildOffset.Y = s.ShapeProperties.Transform2D.Offset.Y;                        gs.GroupShapeProperties.TransformGroup.Extents.Cx = s.ShapeProperties.Transform2D.Extents.Cx;                      gs.GroupShapeProperties.TransformGroup.Extents.Cy = s.ShapeProperties.Transform2D.Extents.Cy;                      gs.GroupShapeProperties.TransformGroup.ChildExtents.Cx = s.ShapeProperties.Transform2D.Extents.Cx;                      gs.GroupShapeProperties.TransformGroup.ChildExtents.Cy = s.ShapeProperties.Transform2D.Extents.Cy;                  } else                  {                      //OFFSET PART (position)                      if (s.ShapeProperties.Transform2D.Offset.X < gs.GroupShapeProperties.TransformGroup.Offset.X)                      {                          gs.GroupShapeProperties.TransformGroup.Offset.X = s.ShapeProperties.Transform2D.Offset.X;                          gs.GroupShapeProperties.TransformGroup.ChildOffset.X = s.ShapeProperties.Transform2D.Offset.X;                      }                      if (s.ShapeProperties.Transform2D.Offset.Y < gs.GroupShapeProperties.TransformGroup.Offset.Y)                      {                          gs.GroupShapeProperties.TransformGroup.Offset.Y = s.ShapeProperties.Transform2D.Offset.Y;                          gs.GroupShapeProperties.TransformGroup.ChildOffset.Y = s.ShapeProperties.Transform2D.Offset.Y;                      }                      //EXTENTS PART (dimension)                      if ((s.ShapeProperties.Transform2D.Offset.X.Value + s.ShapeProperties.Transform2D.Extents.Cx.Value) > (gs.GroupShapeProperties.TransformGroup.Offset.X.Value + gs.GroupShapeProperties.TransformGroup.Extents.Cx.Value))                      {                          gs.GroupShapeProperties.TransformGroup.Extents.Cx = s.ShapeProperties.Transform2D.Offset.X - gs.GroupShapeProperties.TransformGroup.Offset.X + s.ShapeProperties.Transform2D.Extents.Cx;                          gs.GroupShapeProperties.TransformGroup.ChildExtents.Cx = s.ShapeProperties.Transform2D.Offset.X - gs.GroupShapeProperties.TransformGroup.Offset.X + s.ShapeProperties.Transform2D.Extents.Cx;                      }                      if ((s.ShapeProperties.Transform2D.Offset.Y.Value + s.ShapeProperties.Transform2D.Extents.Cy.Value) > (gs.GroupShapeProperties.TransformGroup.Offset.Y.Value + gs.GroupShapeProperties.TransformGroup.Extents.Cy.Value))                      {                          gs.GroupShapeProperties.TransformGroup.Extents.Cy = s.ShapeProperties.Transform2D.Offset.Y - gs.GroupShapeProperties.TransformGroup.Offset.Y + s.ShapeProperties.Transform2D.Extents.Cy;                          gs.GroupShapeProperties.TransformGroup.ChildExtents.Cy = s.ShapeProperties.Transform2D.Offset.Y - gs.GroupShapeProperties.TransformGroup.Offset.Y + s.ShapeProperties.Transform2D.Extents.Cy;                      }                  }              }                if (shape.GetType() == typeof(GroupShape))              {                  GroupShape grpShape = (GroupShape)shape;                  gs.Append(grpShape);                  if (shapeCount == 0) //1st shape added => Initialization of the GroupShape properties                  {                      gs.GroupShapeProperties.TransformGroup.Offset.X = grpShape.GroupShapeProperties.TransformGroup.Offset.X;                      gs.GroupShapeProperties.TransformGroup.Offset.Y = grpShape.GroupShapeProperties.TransformGroup.Offset.Y;                      gs.GroupShapeProperties.TransformGroup.ChildOffset.X = grpShape.GroupShapeProperties.TransformGroup.Offset.X;                      gs.GroupShapeProperties.TransformGroup.ChildOffset.Y = grpShape.GroupShapeProperties.TransformGroup.Offset.Y;                        gs.GroupShapeProperties.TransformGroup.Extents.Cx = grpShape.GroupShapeProperties.TransformGroup.Extents.Cx;                      gs.GroupShapeProperties.TransformGroup.Extents.Cy = grpShape.GroupShapeProperties.TransformGroup.Extents.Cy;                      gs.GroupShapeProperties.TransformGroup.ChildExtents.Cx = grpShape.GroupShapeProperties.TransformGroup.Extents.Cx;                      gs.GroupShapeProperties.TransformGroup.ChildExtents.Cy = grpShape.GroupShapeProperties.TransformGroup.Extents.Cy;                    } else                  {                      //OFFSET PART (position)                      if (grpShape.GroupShapeProperties.TransformGroup.Offset.X < gs.GroupShapeProperties.TransformGroup.Offset.X)                      {                          gs.GroupShapeProperties.TransformGroup.Offset.X = grpShape.GroupShapeProperties.TransformGroup.Offset.X;                          gs.GroupShapeProperties.TransformGroup.ChildOffset.X = grpShape.GroupShapeProperties.TransformGroup.Offset.X;                      }                      if (grpShape.GroupShapeProperties.TransformGroup.Offset.Y < gs.GroupShapeProperties.TransformGroup.Offset.Y)                      {                          gs.GroupShapeProperties.TransformGroup.Offset.Y = grpShape.GroupShapeProperties.TransformGroup.Offset.Y;                          gs.GroupShapeProperties.TransformGroup.ChildOffset.Y = grpShape.GroupShapeProperties.TransformGroup.Offset.Y;                      }                      //EXTENTS PART (dimension)                      if ((grpShape.GroupShapeProperties.TransformGroup.Offset.X.Value + grpShape.GroupShapeProperties.TransformGroup.Extents.Cx.Value) > (gs.GroupShapeProperties.TransformGroup.Offset.X.Value + gs.GroupShapeProperties.TransformGroup.Extents.Cx.Value))                      {                          gs.GroupShapeProperties.TransformGroup.Extents.Cx = grpShape.GroupShapeProperties.TransformGroup.Offset.X - gs.GroupShapeProperties.TransformGroup.Offset.X + grpShape.GroupShapeProperties.TransformGroup.Extents.Cx;                          gs.GroupShapeProperties.TransformGroup.ChildExtents.Cx = grpShape.GroupShapeProperties.TransformGroup.Offset.X - gs.GroupShapeProperties.TransformGroup.Offset.X + grpShape.GroupShapeProperties.TransformGroup.Extents.Cx;                      }                      if ((grpShape.GroupShapeProperties.TransformGroup.Offset.Y.Value + grpShape.GroupShapeProperties.TransformGroup.Extents.Cy.Value) > (gs.GroupShapeProperties.TransformGroup.Offset.Y.Value + gs.GroupShapeProperties.TransformGroup.Extents.Cy.Value))                      {                          gs.GroupShapeProperties.TransformGroup.Extents.Cy = grpShape.GroupShapeProperties.TransformGroup.Offset.Y - gs.GroupShapeProperties.TransformGroup.Offset.Y + grpShape.GroupShapeProperties.TransformGroup.Extents.Cy;                          gs.GroupShapeProperties.TransformGroup.ChildExtents.Cy = grpShape.GroupShapeProperties.TransformGroup.Offset.Y - gs.GroupShapeProperties.TransformGroup.Offset.Y + grpShape.GroupShapeProperties.TransformGroup.Extents.Cy;                      }                  }              }            }

So yea it's ugly, but it seems to work. Please give me a better way to perfom this, I will be glad.

Regards.