ChangesMonitor SDK Sample cannot capture Slab/Ceiling/Roof creation event

[dr.zhou.wei]

Hi guys,

I recently went through the RevitSDK2016 and found a problem in the ChangesMonitor SDK Sample. The problem is that the Sample using Application.DocumentChanged cannot capture the event of creating an instance of Slab/Roof/Ceiling from the Architacture Panel. It only captured the model lines' events when I draw the outlines of these instances without related object events in the final creation. I upload this screenshot here to show my confusion. Did anybody encounter the same problem before? I couldn't find related answers anywhere to explain what I met. I tested this in both Revit 2015 and 2016 Chinese version and result is the same. It seems the ChangesMonitor SDK Sample can record other instances' creation events for sure excepting the problem I met. I'm unsure if this problem is the same case in other language versions of Revit? Any clues? 

Cheers
Wei

[jeremytammik]

Dear Wei,

Thank you very much for reporting this.

Can yoou please provide the exact step by step instructions in order to reproduce this behaviour?

If we can reproduce it, I will pass it on to the development team for further analysis.

For that, we require a really simple, fool-proof, minimal reproducible case:

http://thebuildingcoder.typepad.com/blog/about-the-author.html#1b

Thank you!

Best regards,

Jeremy

[dr.zhou.wei]

Dear Jeremy,

Thank you for your feedback. In order to show a clear procedure in my test, I opened an empty project to do my testing operations decribed as follows. Every step is corresponded to a marked screenshot.

Step-01) I clicked the architecture slab icon; Step-02) I clicked the Rectangle icon to draw a slab; Step-03) When I drew the rectangle, the events were captured in the dialogbox as shown to be the model line only. So far the event was normal. Step-04) When I clicked the green tick icon to finish the editing to create the slab, the creation event was not captured as no such a event shown in the dialogbox, which still showed 4 model line events. This is the PROBLEM I identified as I have finished the slab creation but no related event captured using the documentchanged method. Step-05) However, if I changed the current slab type to be another one (as shown of Generic - 150 mm), the modification event will be shown. Step-06) As illustrated, the modification event was shown that the slab was changed into the new one.

The identified creation event missing problem is also found in the Ceiling and Roof creations without relevant events captured in the dialogbox following my step-by-step operations mentioned above.I'm wondering if this is the SDK or product problem.

Kind regards

Wei

[jeremytammik · Accepted solution]

Dear Wei,

Thank you for your update and clear description.

I logged the issue REVIT-90802 [API: no DocumentChanged event raised by slab creation] with our development team for this on your behalf, as it requires further exploration and possibly a modification to our software. Please make a note of this number for future reference.

You are welcome to request an update on the status of this issue or to provide additional information on it at any time quoting this change request number.

This issue is important to me. What can I do to help?

This issue needs to be assessed by our engineering team, and prioritised against all of the other outstanding change requests. Any information that you can provide to influence this assessment will help. Please provide the following where possible:

• Impact on your application and/or your development.
• The number of users affected.
• The potential revenue impact to you.
• The potential revenue impact to Autodesk.
• Realistic timescale over which a fix would help you.
• In the case of a request for a new feature or a feature enhancement, please also provide detailed Use cases for the workflows that this change would address.

This information is extremely important. Our engineering team have limited resources, and so must focus their efforts on the highest impact items. We do understand that this will cause you delays and affect your development planning, and we appreciate your cooperation and patience.

I hope this helps.

Best regards,

Jeremy

[dr.zhou.wei]

Dear Jeremy,

Thank you for your confirmation about this pitfall exposed in the SDK sample. I'll seek another soultion to utilise the DocumentChanged approach to our development. In terms of your questions for this issue, my answers are inline of them:

Impact on your application and/or your development.
>>It has an impact that I have to use some other ways indirect to reach my development goals.

The number of users affected.
>>I don't think this pitfall will affect a number of users( developers? ) since the DocumentChanged event has been introduced for 5 years already and not be identified until now.

The potential revenue impact to you.
>>Possiblly the impact on our business is in medium severity

The potential revenue impact to Autodesk.
>>The impact for Autodesk is in low severity

Realistic timescale over which a fix would help you.
>>Within half year would be great

I hope my answers will be useful for your development team to enhance this nice feature for better and robust solution.

Thank you again for your help.

Kind regards
Wei

[jeremytammik]

Dear Wei,

Thank you for your update, appreciation and business case.

I updated the database description to REVIT-90802 [API: no DocumentChanged event raised by slab creation -- 11757416] to include the ADN case number that I use to keep notes on this issue and added you business case to it as well to help the development team assess its importance.

I hope this helps.

Best regards,

Jeremy