circularArrow has bad guide formulas in presetShapeDefinitions.xml

Discussion circularArrow has bad guide formulas in presetShapeDefinitions.xml

  • Thursday, May 13, 2010 8:20 PM
     
     
    I have noticed that the guide formulas defined in presetShapeDefinitions.xml which is a part of ISO/IEC 29500-1:2008 electronic inserts, in OfficeOpenXML-DrawingMLGeometries.zip, do not seem to be quite right.  The head of the arrow never seems to be drawn correctly when following these formulas.  Is there a newer version of this document available somewhere, or perhaps someone has a suggestion to fix the formulas?

All Replies

  • Friday, May 14, 2010 11:44 AM
    Moderator
     
     

    Hi drmoore718

    Thank you for your question.  A colleague will contact you soon to work on this issue.

    Regards,

    Mark Miller

    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

  • Friday, May 14, 2010 2:48 PM
    Moderator
     
     

    Hi drmoore718,

    I'll be working with you on this issue.  I'll take a look at the referenced formulas and get back to you shortly.  In the meantime, if you have a sample rendering image or code that you can share with me to exhibit the issue, please feel free to post it to dochelp@microsoft.com.   Just reference my name and the URL for this post in your email to make sure it gets to me.

    Best regards,
    Tom Jebo
    Senior Support Escalation Engineer
    Microsoft Open Specifications

     

  • Friday, May 14, 2010 3:58 PM
     
      Has Code

    Hi Tom,

     

    I actually believe I found the issue.  The guide formulas were defining a couple of names multiple times

     

    <gd name="dxI" fmla="+- x2I 0 x1I" />
    <gd name="dyI" fmla="+- y2I 0 y1I" />
    
    ...
    
    <gd name="dxI" fmla="cat2 rw3 htI wtI" />
    <gd name="dyI" fmla="sat2 rh3 htI wtI" />
     

    I was able to fix the issue by changing the names of the second "dxI" and "dyI" and any following formulas that referenced them.

     

    I am curious, though, if this is an error or if it is allowed by the specifications.  I wasn't able to tell for sure either way by reading through [5.1.11.11 gd (Shape Guide)] in "Office Open XML Part 4 - Markup Language Reference"

     

    Thanks

  • Friday, May 14, 2010 7:26 PM
    Moderator
     
     
    thanks, I'll check it out and let you know soon.
  • Friday, May 21, 2010 8:41 PM
    Moderator
     
     

    Hi drmoore718,

     

    We have determined that this is a bug in the presetShapeDefinitions.xml sample.  We will propose a defect report on this matter to Ecma TC45, for submission by TC45 to the maintenance group for IS 29500, and we anticipate that this correction will likely be approved and included in a future corrigendum for the standard.  Thank you for bringing this to our attention.

     

    Best regards,

    Tom Jebo

    Senior Support Escalation Engineer

    Microsoft Open Specifications

  • Friday, May 21, 2010 8:52 PM
     
     

    Hi Tom,

    So you know, I recently found multiply defined guides in the following autoshape definitions as well

    • gear6
    • gear9
    • leftCircularArrow
    • ellipseRibbon
    • ellipseRibbon2

     

    Thanks for the info.

  • Wednesday, May 26, 2010 4:54 AM
    Moderator
     
     

    Thanks drmoore718!  Just to verify, these are the value names that I've found to be redefined:

    •gear6 – a1

    •gear9 – a1 and a2

    •leftCircularArrow – dxI and dyI

    •circularArrow – dxI and dyI

    •ellipseRibbon – q1

    •ellipseRibbon2 – q1

    Did I miss any?

    Best regards,

    Tom Jebo

    Senior Support Escalation Engineer

    Microsoft Open Specifications

     

  • Friday, May 28, 2010 4:32 PM
     
     
    No, those are the names I found to be redefined as well.
  • Wednesday, July 06, 2011 10:47 AM
     
     
    Is correct version of circuitArrow xml exist? Thank you.
  • Thursday, July 07, 2011 8:38 PM
    Moderator
     
     

    Hi Victor, the corrected version of the presetShapeDefinitions.xml file will be included in a future release of the ISO/IEC 29500 standard. For now, you can use the method described above to fix the definition manually.

     


    Josh Curry (jcurry) | Escalation Engineer | US-CSS DSC Protocols Team