You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of my users has been using pyRevit to Make Patterns for quite a while, but today wasn't able to complete the command, and we couldn't close Revit.
Turns out she was trying to Make a Pattern from a Detail View instead of a Drafting View.
Clearly user error, but the reason I'm posting a bug report is that this hung up Revit and we had to use Task Manager to kill Revit completely.
We had the pattern lines drawn in a Detail View (created from a Callout on a Section if that matters)
Selected the lines, started the Make Pattern tool, gave it a name, and when wed click on the Creat Pattern button, the normal orange pop up window never displayed.
At that point, we couldn't close pyRevit and couldn't get back into the Revit UI
This first happened with PyRevit 4.4. I then upgraded to the current version 4.6 and the same thing happens.
Again, this is clearly user error, but it is a nasty error which caused lost work
The text was updated successfully, but these errors were encountered:
One of my users has been using pyRevit to Make Patterns for quite a while, but today wasn't able to complete the command, and we couldn't close Revit.
Turns out she was trying to Make a Pattern from a Detail View instead of a Drafting View.
Clearly user error, but the reason I'm posting a bug report is that this hung up Revit and we had to use Task Manager to kill Revit completely.
We had the pattern lines drawn in a Detail View (created from a Callout on a Section if that matters)
Selected the lines, started the Make Pattern tool, gave it a name, and when wed click on the Creat Pattern button, the normal orange pop up window never displayed.
At that point, we couldn't close pyRevit and couldn't get back into the Revit UI
This first happened with PyRevit 4.4. I then upgraded to the current version 4.6 and the same thing happens.
Again, this is clearly user error, but it is a nasty error which caused lost work
The text was updated successfully, but these errors were encountered: