Parts List Update 2011 vs 2010

[nmunro]

Add-in using 2010 Interop, designed to work in 2010 and 2011.

User updates property information in part, applies changes:

2010 - Calling Update2() on the drawing document updates the parts list(s).

2011 - Calling the same does not update the parts list.

In 2011, the user must move the parts list or perform some other action to get the PL to update.

Is this a result of the new Sheet.Update() method in 2011? Any work arounds?

Thanks for any pointers.

[sanjay.ramaswamy]

Neil,

There were no intentional changes in this area. The parts list should have updated as in the past. Do you have a sample (code and file) that reproduces the problem?

[nmunro]

Hi Sanjay,

Its a big add-in so getting a sample out of it would take some work. The updates are accomplished through a change processor:

Property changes are written back to the appropriate document.

That document and the active document (drawing) are updated.

Not much else happening.

Here are two screencasts of the same dll on two different machines. Others are reporting the same behavioour with 2011.

Inventor 2010 Vista x64
http://screencast.com/t/ZjUwYjQ0ZTQt

Inventor 2011 Win 7 x64
http://screencast.com/t/ZTc0MzYyYW

[sanjay.ramaswamy]

Neil,

We looked into it, but we are not able to reproduce the problem. Changing property values from within a ChangeProcessor does seem to update the parts list. So we'll need more information to track down the issue.

[nmunro]

Maybe the place to start is with what Interop assembly gets used. The add-in does not copy the IV2010 Interop locally, so if a machine only has 2011 installed, it will use the 2011 Interop from the GAC?

[sanjay.ramaswamy]

Was the add-in built with Inventor 2010? If so, it should pick up the 2010 interop from GAC. We deliver the current interop + previous 2 releases.

[nmunro]

Fixed it. Had to force a second update of the drawing document after the change processor OnExecuter() method returned.

Had tried with a timer delay inside the chagne processor before updating the dwg, no luck there. Still no idea why it would work in one IV version and not another.

[ACEDeSmedt]

Sometimes, I have the feeling that, if you alter something with VBA, the drawing doesn't follow as it should be.

I'm still looking for examples but if I find one, i'll post it here

regards,

Klaas De Smedt