Autodesk.Revit.UI.Selection.PickObject issue

[Anonymous]

Hi,

I think there is an issue with the "PickObject" process.

Steps to reproduce :

1. Select any view with "pickable" objects.
2. Open the "Visibility/Graphic window" and keep it opened as a floating window.
3. Launch a command (for example within an addin) that calls "PickObject" to select a "pickable" object.
4. The picking process starts ...

At that point, you cannot select any object in the view (despite passing the picking filtering test).

You cannot press ESC to abort the picking process.

You cannot close Revit.

You cannot close the Visibility/Graphic window by its buttons.

Only thing you can do is close "Visibility/Graphic window" by ALT+F4, but then, the picking process is aborted without firing any exception.

[jeremytammik]

Dear Olivier,

Thank you for raising the issue here in public after our private email conversation.

Sorry to hear about this.

I logged the issue REVIT-136897 [PickObject fails when Revit UI displays floating window] 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 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.

Best regards,

Jeremy

[jeremytammik]

The development team analysed this issue and say:

There is no macro included so this will take a long time to reproduce to even see this. any chance one exists? We could get an answer faster if we had an example. 

Is this for this window only or all windows?

What is a floating window? Modeless? Visibility Graphics is not Modeless. 

In Revit you cannot select anything with this dialog open in the UI.

Is there some expectation that the API can launch commands while the dialog is open?

When we have V/G dialog open the add-in ribbon is grayed out. so how is this state even achieved?

Marking this case as 'Needs more information'.

Please provide a complete minimal reproducible case for the development team to analyse and understand:

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

Thank you!

Best regards,

Jeremy

[Anonymous]

I'll try to make a test case.

Is this for this window only or all windows?

Don't known, issue arises "at least" with this window opened.

What is a floating window? Modeless? Visibility Graphics is not Modeless. 

Yes indeed, VG is modal ...

In Revit you cannot select anything with this dialog open in the UI.

Correct.

Is there some expectation that the API can launch commands while the dialog is open?

Yes indeed.

My addin is a modeless form.

With VG being visible (so Revit is locked), and my addin's modeless form visible too, the user can click on a button that calls "Autodesk.Revit.UI.Selection.PickObject".

Revit then switches to the picking mode, which is bad because VG is visible and all is locked.

When we have V/G dialog open the add-in ribbon is grayed out. so how is this state even achieved?

My addin's modeless window is opened before opening VG.

[jeremytammik · Accepted solution]

Thank you for the clarification.

I am pretty sure that I can guarantee that you will not be able to interact with the Revit API in any way whatsoever as long as the Revit VG form is being displayed.

Therefore, we can cancel this whole issue and there is no need for you to submit a sample.

Cheers,

Jeremy

[Anonymous]

Got it Jeremy ...

My call to "PickObject" was made outside a valid Revit context.

It worked flawlessly when Revit was not locked, so I didn't see that it was a wrong usage.

By encapsulating the call inside a valid Revit context by using Idling event, the problem is solved, because OnIdling is only triggered when Revit gets unlocked.

The "issue" was in fact a bad usage from my side.

My bad, sorry for that.

Nevertheless, thank you Jeremy & Autodesk team for rapid and pertinent support.

[jeremytammik]

Brilliant!

Thank YOU for your rapid understanding and confirmation!

Cheers,

Jeremy