I read about quirky Reviteristic issue at RFO this afternoon. A weird graphics glitch occurs when we interact with the Help Icon families that use the URL parameter feature to reference an external document. This is an example of it in the sample architecture model that ships with Revit (rac_basic_sample_project.rvt - in imperial content).
When we select the icon and examine its properties we get this Learning Link parameter.
When we click in the field the small button appears with the ellipsis icon. Clicking on the that button will take us to the URL saved in family.
The trouble begins after we move our cursor away from the field and start to resume work. The URL is stuck on screen over another parameter like below, the Detail Number parameter for the view.
I noticed that I can work past the issue if I click in the Default Analysis Display Style field, which I presume works because it also has an navigation/ellipsis style button.
I also noticed that if I am careful to click on the field right above the Learning Link, called Location, before leaving the Properties Palette I can avoid the issue too.
The forum thread was talking about this in 2019 but these images are from 2020.2.
When we select the icon and examine its properties we get this Learning Link parameter.
When we click in the field the small button appears with the ellipsis icon. Clicking on the that button will take us to the URL saved in family.
The trouble begins after we move our cursor away from the field and start to resume work. The URL is stuck on screen over another parameter like below, the Detail Number parameter for the view.
I noticed that I can work past the issue if I click in the Default Analysis Display Style field, which I presume works because it also has an navigation/ellipsis style button.
I also noticed that if I am careful to click on the field right above the Learning Link, called Location, before leaving the Properties Palette I can avoid the issue too.
The forum thread was talking about this in 2019 but these images are from 2020.2.
No comments:
Post a Comment