Ribbon Panel items are disabled when 3d view is activated.

[Anonymous]

Hi,

I am new to Revit. I have created a new ribbon panel and added some items.

When I switch to a 3D View the ribbon panel items are disabled.

Why items are disabled ?

How can I enable them in all type of views till there is a active ui document ?

[Anonymous]

Hey,

I'm pretty sure they should not be disabled just because you switched to 3D view.
Maybe you have some other command\transaction running or a messagebox\window open?
Press escape once or twice and check if there is no open windows in the background from revit or revit addins.

[Anonymous]

I have tried pressing escape twice but it did not have any effect.

I am using Revit 2017.

[RPTHOMAS108]

Hard for anyone to say if you share no code indicating what you have done to create the items on the ribbon.

e.g. have you implemented IExternalCommandAvailability at all if so how?

[Anonymous]

For login button there is no AvailabilityClassName.

But for other button there is. 

public bool IsCommandAvailable(UIApplication applicationData, CategorySet selectedCategories)
{
return UserData.Instance.LoggedIn && (applicationData.ActiveUIDocument != null);
}

Other buttons are available when user is logged in and there is some active document available.

[Anonymous]

Same plugin works in Revit 2018 with no code changes.

Ribbon panel items are not disabled when 3d view is activated.

[Revitalizer]

Hi,

in the Revit 2018 SDK, there is a "Revit Platform API Changes and Additions.docx".

On the very first page, it says:

"Most commands allowed in 3D orthographic views are now also allowed in perspective views."

I want to add that this API addition just reflects the changed UI behavior, from 2017 to 2018.

So it is not a problem but works as expected.

Revitalizer

[Anonymous]

So we cannot enable the ribbon panel in Revit 2017 when current view is 3D view ?

[Revitalizer · Accepted solution]

Hi,

basic knowledge of the product can answer many API questions.

In nearly all cases, the rule is:

If you cannot do it via UI, it cannot be done via API, too.

Revitalizer

[Anonymous]

We are currently experiencing the same issue. May I know what the alternative solution was? Did you end up having to not using IExternalCommandAvailability implementations on the ribbon items?