# \[Bug\] Previously selected nodes jump to mouse position after creating a new node and moving it

**URL:** <https://forum.dynamobim.com/t/bug-previously-selected-nodes-jump-to-mouse-position-after-creating-a-new-node-and-moving-it/23688>\
**Category:** Uncategorized\
**Tags:** bugs, dynamo\
**Created:** [July 13, 2018, 9:50am UTC](https://forum.dynamobim.com/t/bug-previously-selected-nodes-jump-to-mouse-position-after-creating-a-new-node-and-moving-it/23688 "2018-07-13T09:50:57Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![sed07](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@sed07](https://forum.dynamobim.com/u/sed07)\
**Post date:** [July 13, 2018, 9:50am UTC](https://forum.dynamobim.com/t/bug-previously-selected-nodes-jump-to-mouse-position-after-creating-a-new-node-and-moving-it/23688/1 "2018-07-13T09:50:58Z")

</div>

Hi,

I don’t know if this is the place to post bugs, but I’ve been having this issue lately. I think it started after switching to Revit 2019, but I’m not sure. I wonder if anyone else experienced it and knows what’s causing it.

Basically what happens is whenever I create a new node or copy an existing one (but mostly when I copy an existing one), when I deselect the newly created node(s) then re-select it and move it, any previously selected node(s) will jump to the mouse position at that moment, and many times it ends up bringing the node all the way from the other side of the script and places it right on top/under the new node.

And what’s worse, it’s not undo-able. I’ve uploaded a recording below.

 ![moving%20nodes%20bug](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/0/7/0797d8d7dcacfb29cabee64621cdda36729e395a.gif)

---

<div class="post-metadata">

**Author:** ![Ewan\_Opie](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/ewan_opie/32/77070_2.png) [@Ewan\_Opie](https://forum.dynamobim.com/u/Ewan_Opie)\
**Post date:** [July 13, 2018, 10:11am UTC](https://forum.dynamobim.com/t/bug-previously-selected-nodes-jump-to-mouse-position-after-creating-a-new-node-and-moving-it/23688/2 "2018-07-13T10:11:46Z")

</div>

Had this randomly in 0.9 as well as 1.2 and 1.3  
Looks like the inclusion on CTRL drag copying was introduced in 0.9 possibly [http://dynamobim.org/forums/topic/copypaste-behavior-is-annoying/](http://dynamobim.org/forums/topic/copypaste-behavior-is-annoying/) @Ritesh_Chandawar ?

---

<div class="post-metadata">

**Author:** ![sed07](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@sed07](https://forum.dynamobim.com/u/sed07)\
**Post date:** [July 13, 2018, 12:14pm UTC](https://forum.dynamobim.com/t/bug-previously-selected-nodes-jump-to-mouse-position-after-creating-a-new-node-and-moving-it/23688/3 "2018-07-13T12:14:05Z")

</div>

I’m using Dynamo 1.3.3 and CTRL drag copying. You’re saying it might be related to something introduced in previous versions?

---

<div class="post-metadata">

**Author:** ![kevin\_h\_us](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@kevin\_h\_us](https://forum.dynamobim.com/u/kevin_h_us)\
**Post date:** [August 14, 2019, 12:56pm UTC](https://forum.dynamobim.com/t/bug-previously-selected-nodes-jump-to-mouse-position-after-creating-a-new-node-and-moving-it/23688/4 "2019-08-14T12:56:38Z")

</div>

Same problem is still occuring (using Revit 2017 with Dynamo 2.0.0.4654) but more immediately, where the ctrl+drag shortcut is used, and when the newly created component is selected, the original component jumps to the new location.

It is so annoying that I am abandoning use of that command.

---

<div class="post-metadata">

**Author:** ![jacob.small](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/jacob.small/32/161030_2.png) [@jacob.small](https://forum.dynamobim.com/u/jacob.small)\
**Post date:** [August 14, 2019, 1:00pm UTC](https://forum.dynamobim.com/t/bug-previously-selected-nodes-jump-to-mouse-position-after-creating-a-new-node-and-moving-it/23688/5 "2019-08-14T13:00:27Z")

</div>

Can you confirm you’re using the latest build of Revit 2017? Also update Dynamo from 2.0.0 to 2.0.2, a lot of issues will be fixed by updating those two items.

---

<div class="post-metadata">

**Author:** ![sed07](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@sed07](https://forum.dynamobim.com/u/sed07)\
**Post date:** [August 14, 2019, 2:47pm UTC](https://forum.dynamobim.com/t/bug-previously-selected-nodes-jump-to-mouse-position-after-creating-a-new-node-and-moving-it/23688/6 "2019-08-14T14:47:37Z")

</div>

I have since gotten used to using ctrl+c and ctrl+v instead of dragging, but I confirm that it doesn’t cause any problems with dragging now on Revit 2020.

---

<div class="post-metadata">

**Author:** ![kevin\_h\_us](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@kevin\_h\_us](https://forum.dynamobim.com/u/kevin_h_us)\
**Post date:** [August 15, 2019, 7:30am UTC](https://forum.dynamobim.com/t/bug-previously-selected-nodes-jump-to-mouse-position-after-creating-a-new-node-and-moving-it/23688/7 "2019-08-15T07:30:48Z")

</div>

I am using Revit 2017.2 and will update to Dynamo 2.0.3  
Thank you for the advise!

---

<div class="post-metadata">

**Author:** ![jacob.small](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/jacob.small/32/161030_2.png) [@jacob.small](https://forum.dynamobim.com/u/jacob.small)\
**Post date:** [August 15, 2019, 1:32pm UTC](https://forum.dynamobim.com/t/bug-previously-selected-nodes-jump-to-mouse-position-after-creating-a-new-node-and-moving-it/23688/8 "2019-08-15T13:32:24Z")

</div>

Revit 2017.2.5? If not put those last few patches in place. 🙂

---

<div class="post-metadata">

**Author:** ![Yao](https://avatars.discourse-cdn.com/v4/letter/y/2bfe46/32.png) [@Yao](https://forum.dynamobim.com/u/Yao)\
**Post date:** [November 24, 2020, 3:19pm UTC](https://forum.dynamobim.com/t/bug-previously-selected-nodes-jump-to-mouse-position-after-creating-a-new-node-and-moving-it/23688/9 "2020-11-24T15:19:05Z")

</div>

Now we are in November of 2020, I am using Alias 2021.2 with Dyanmo 2.7.0.9206 and I still have the same problem ! 😂 🤣
