Move command moves pinned elements

[chubbard]

In Revit 2022 it appears that using move on pinned elements allows them to be unpinned and moved in a single command. I do not see where this bug(feature) was called out. Anybody else get this behavior? In the past versions it just says pinned elements cannot be moved. 

I jsut accidently moved a pinned linked Revit model not realizing it was selected with the element I wanted to move. 

Press and drag does not move, but Move-Select does move with no warning. Trying to delete still generates a warning and does not delete but move works 

See attached video of me moving a pinned gird 

[ToanDN]

Make sure Disjoin is NOT checked.

[barthbradley]

---

@chubbard wrote:

In Revit 2022 it appears that using move on pinned elements allows them to be unpinned and moved in a single command. I do not see where this bug(feature) was called out.

"Bug"? Huh?  I cannot be move a pinned element unless it is unpinned first.   

[barthbradley]

Holy cow!  Disjoin!  Yeah, that's not right in my book.  I'm with you on this one, @chubbard.  

[chubbard]

It seems this was added in 2021. If Disjoin is checked in the move command you can move any pinned element. Grids linked models CAD files etc. 

[ToanDN]

---

@chubbard wrote:

It seems this was added in 2021. If Disjoin is checked in the move command you can move any pinned element. Grids linked models CAD files etc. 

---

No.  The behavior has been the same on any versions. 

[chubbard]

Just tried it on 2020 and 2019. Cannot move pinned elements even if Disjoin is checked. Get a warning every time. 

[ToanDN]

Here is a screencast for 2019.

https://knowledge.autodesk.com/community/screencast/f919b0e5-6a19-4789-b9c3-8bacda4ebdb5

[David_W_Koch]

Wow.  Good to know.  Just played around with that, and not only does it move the element, it leaves it unpinned, as well.  This may explain how pinned items get moved by staff who claim that they never unpinned anything.  Or how things get unpinned that should not have been.

I suppose Autodesk considers this a feature of "disjoin".  Problem is, if you, for legitimate reason, check disjoin, that remains the default.  It is only too easy not to check that setting the next time you go to move something.  And then having it remain unpinned opens the door for it to be moved or worse in the future.

[chubbard]

Disjoin will stay active in 2022 even if you close the file and or Revit. I don't use it often but it was on making me think it might be defaut on? 

[barthbradley]

I'm pretty sure you can set that default through the Revit INI file. Check it out.  

Yep...

Change to 0.

[David_W_Koch]

---

@chubbard wrote:

Disjoin will stay active in 2022 even if you close the file and or Revit. I don't use it often but it was on making me think it might be defaut on? 

---

I checked that out in 2022 and it started out unchecked for me.  It seems to be saving the last setting, however, even when completely closing Revit and then restarting it.

That was not the case in very limited testing in Revit 2017.  It is too late here to test any other versions, or to thoroughly test all possible permutations.  Perhaps at some point, they started saving the value to the Revit.ini file?  A quick check showed a line for MoveCopy_Disjoin=0 in the Revit 2022 Revit.ini file in my user AppData\Roaming folders, but no such line in Revit 2017.  There was no such line in the 2018, 2019, 2020 or 2021 Revit.ini files, either.  So perhaps a new feature for 2022.