I have drag disabled by setting a high threshhold, since I literally have no use for drag.
Other people might have some cases where drag is useful, but usually want it disabled.
Therefore a toggle may be useful.
3 Likes
I think that it’s better to implement two separate toggles for dragging objects and control points. Fine tuning control points is essential and usually they are shown for the very reason to be moved in a different position. On the other hand, many users may want to prevent unwanted movement of existing objects while trying to select them, so a dedicated toggle (or a high threshhold setting) to turn off the object dragging makes sense.
Yes, I agree that for editing with control points, dragging is essential. And I also understand the need not to accidentally drag objects. There are already two settings for drag threshold (objects/control points), so that can be more or less implemented using the current ‘strategy’ of setting a very high threshold for objects and a low one for control points.
However, aside from full objects and control points, there is also the whole area of sub-objects. Right now they obey the ‘object’ setting. However, I can see the need to have easy dragging enabled for those while keeping hard dragging enabled for full objects.
IMO, this is almost getting to the point where it needs its own detailed settings panel with more granularity on what one would like to be able to drag easily or not.
As far as a toggle to completely disable dragging of one of the above categories, I think that also should be integrated into the settings. But this has been a subject of discussion as long as I can remember being on the newsgroup/forum, that is to say since like Rhino 1.1… There seems to be a massive wall of resistance to that which has not changed since.
3 Likes
Rhino.Options.Mouse.EnableUnselectedObjectDrag set to false works fine
Rhino 8 (WIP)
3 Likes
This is amazing, I wish I had known this ~5 years ago!
I sure am glad I snooped the forums for this basic thing, I find this Alt-button solution to be optimal for my needs.
Thank you, Pascal!
I completely agree with you. 
Is there a way to set this via the SDK in C#? I need to override standard settings for whoever is using my program. I’m still in Rhino 7, so if setting the drag threshold is what it has to be, so be it. I just want to know how to set the mouse options programmatically and cannot find any documentation with respect to this.
I answered my own question. You can run something like
RhinoApp.RunScript(“_-Options _Mouse _ClickAndDrag _ObjectThreshold {number} _Enter”, echo);
to toggle drag selected on and off, similar for other settings.
This being said, I can’t set a number higher than 100 here (error message is “Number must be smaller than or equal to 100”, but you can go higher in the settings dialog box. Why is this?
John -
Hi John !
Its BEEN awhile !
I really NEED to disable dragging during a move or copy command , as the highlighted wireframe object dragging along with the Move or Copy , dramatically INTERFERES with selecting destination object snap points . It becomes nearly IMPOSSIBLE to successfully complete move and copy commands for ANY but the simplest objects .
This is very serious , as it forces repeated UNSUCCESSFUL command attempts .
ANY suggestions you can offer would CLEARLY be appreciated , as clearly indicated by the longevity of this thread.
Thanks for ANY guidance you can offer , even a usable workaround would be appreciated .
THANKS ! -
Charles .
I think John retired.
Hi ! Sorry to intrude (not really ;=)) ! ) but my situation while similar is a bit different . Any suggestions I can gain will be a huge help .
I use drag with selected objects frequently .
What I really need is the ability to disable or at least toggle it in a conventional Move or Copy command , as the surface edges and ISO-Curves MASSIVELY confuse the process of selecting DESTINATION Object Snap points .
Is there ANYTHING you can offer on this ?
Thanks !
- C .
Hi ! Sorry to intrude (not really ;=)) ! ) but my situation while similar is a bit different . Any suggestions I can gain will be a huge help .
I use drag with selected objects frequently .
What I really need is the ability to disable or at least toggle it in a conventional Move or Copy command , as the surface edges and ISO-Curves MASSIVELY confuse the process of selecting DESTINATION Object Snap points .
Is there ANYTHING you can offer on this ?
Thanks !
- C .
Thanks - and ALL the best to him if so !
Is there ANYTHING anywhere on the setting that selects whether objects are shown moving into place as the move or copy command is operating or no- it just jumps into the next position ?
This would VASTLY improve the performance of these two commands , and I’m trying to remember that way back at either 3 or 4 (that’s how long I’ve been a RHINO user ( ;=) ! ) we were able to select NOT showing the ISO lines and contours of the object during a move or copy, at set-up ?
It seems as I recall , there was a setting , but now that my models have become as complex as they are , this has really become a “thing” to be dealt with .
Thanks for ANYTHING you can offer - even if its only a referral to something or someone else ?
Thanks -
C.
Dan-
Hi again.
Maybe you can refer me to someone who might help ?
I’m hoping to find a way that my object I’m moving or copying doesn’t slide with my search for the destination point , as the surface edges and ISO-Curves MASSIVELY confuse the process of selecting DESTINATION Object Snap points in a dense model , or even in one that is not so dense.
I seem to remember that there was once the ability to select NOT dragging the object with you to the 2nd or “Destination point” in the process of executing a move or copy command.
Thanks for ANY help you can offer - even if only to refer me or my question to someone more familiar ?
Sincerely-
THANKS !
Charles.
If you are looking to just copy or move objects without the preview, here are a couple of scripts that might help:
MoveNoPreview.py (509 Bytes)
CopyNoPreview.py (510 Bytes)
The only preview is a line that is drawn between the base point and the target point. Note that the copy script only makes one copy. If you need multiple copies at different locations in the same operation, let me know.
1 Like
Great scripts! Both work noticeably faster on dense mesh models. Thanks! 
P.S. Please, post your scripts in this thread, too.