Bug check: Tab select of chained detail lines not working after inputting offset value in offset command

[lucdoucet_msdl]

To all,

When using the offset command on chained detail lines (such as a closed rectangle in the Screen cast attached), the tab select command will not recognize the entire chained group when the offset value is changed before.

Workaround: After entering the new offset value, the tab select of the entire chain is re-enabled by toggling the copy option on and off.

Does this happen to anyone else? If so, it would seem to be a bug, though a simply annoying one. ☹

-luc

Edit: Added Screencast

https://screencast.autodesk.com/Embed/Timeline/b517b230-1080-4ea5-b886-db0e9a196814

[barthbradley]

where's this Screencast you mentioned?  

...scratch that.  I can indeed replicate in 2022.  

...further findings: If the copy box is toggled on to off, or vice versa, the TAB-Select all lines works again. Weird.  

[lucdoucet_msdl]

@barthbradley 

Can't seem to add the screen cast to the original posting. 2nd try here = Nope, getting an invalid HTML error and the Forum editor erases the embedded screen cast. Have added a direct link in the original post.

Screencast with Revit 2020.2. Will try with Revit 2022.1

-luc

[barthbradley]

doesn't matter. I see what you are talking about now.  It's screwy.   

[RDAOU · Accepted solution]

@lucdoucet_msdl 

No issues here

However, I did notice something on your screencast...After you modify the offset distance and hover over the line.

• When you are hitting TAB you are re-highlighting the Offset Distance => the Chain is not working at your end
  
  1. After you input a value, click in a blank space on screen to exit/deactivate the offset dialog 
  2. Then tab over the lines

Your screencapture  - notice the blue outline of the Offset dialog and the highlighted Offset value while you are tabbing the line

   

S long as the border of the Offset dialog is blue => it is the active Active window => that is where the tab is applied

[lucdoucet_msdl]

@RDAOU 

You've caught the problem: clicking in an empty part of the view to make it active works. 

The fact that using the default offset value doesn't require the user to make the view active is counter intuitive though. I suppose it is a consequence of having a different action for the tab key when in the drawing environment (tab = cycle through elements) and in a text/numerical field ( tab = select all).

Going to have to retrain some of my muscle memory when using Revit!

Thanks,

-luc