Minor typo bug in ApplicationOptions.XML and difference when using it in iLogic

[ReneRepina]

Greetings,

I hope it is the right category to post this, I was searching for other bug reporting system but I did not find it.

I came across a minor typo bug in ApplicationOptions.XML file, (EnableCrossPartSketchGeomtryProjection="1" setting to be exact) that seems to be working if you import and export data, but if you use that sentence exacly like in iLogic it doesn't work beucase it is a typo.

Sentence is EnableCrossPartSketchGeomtryProjection="1", as you can probably figure it out, it is missing and E in "GeomEtry".

If I use code sentence (as written in XML file) in iLogic (ThisApplication.AssemblyOptions.EnableCrossPartSketchGeomtryProjection = True) it won't work, because it is missing and E (it says: Public member 'EnableCrossPartSketchGeomtryProjection' on type 'AssemblyOptions' not found.).

But if I tweak it a little and fix the typo (add E to geomEtry) --> (ThisApplication.AssemblyOptions.EnableCrossPartSketchGeometryProjection = True) it works like it should.

It is a minor bug, that actually works even with a typo in it, if you import and export file, but it doesn't work in iLogic if you use sentence exact like in XML.

Hope I explain it clearly to understand.

Best regards,

ReneR

kelly.young has embedded your image for clarity.

[Xun.Zhang]

Hi ReneR,

I agree with you that it is a bug and report to project team from now on.

Thanks!

[Scott.Hawkins]

Hi Rene,

That is unfortunate, misleading and annoying for users!

It is unfortunate because it is not really a bug, because the XML is not really a user interface (it is part of the XML schema) and that is not actually an English word.  If it were, then it would have been caught by a spell checker.  Of course the COM (iLogic) name is arguably more of an actual user interface and so more humans have looked at it and would have noticed this.

Both spellings were introduced when this feature was added to Inventor 2013 and have not changed since then.  If we were to change it now, then we would impact backwards compatibility.  We could add synonyms going forward to recognize both spellings in both the COM and the XML, but we would have to choose which spelling to use in the XML for export.  To preserve compatibility we would need to choose the "misspelling" 

Do you think that we should add compatibility with the two spellings to both the COM and API?  If so, then we would look at doing that for Inventor 2020 (next year's release).  The alternate spellings could not be used by previous releases.  I would need to submit a change request to do so and have it approved.

Thank you,

Scott

[ReneRepina]

Hi Scott,

I understand. In my situation I was searching this command for iRule, I did not know how the command is called, so I used my logic and tools  to get the right command and I came across this command name in XML file, but I figure it out that with that string it does not work, so I tried with adding E and it was working. Since those two words did not came up the same, I reported it here in case this could be a problem.

Since reading XML files and using (programming) iRule is kinda deep use, it can stay like it is now, because people who know how to use XML and iRule commands will probably figure it out how to make it work, but it could be misleading though (if you try to find commands like that).

Best regards,

ReneR