Rhino WIP Feature: Clipboard Enhancements

The Rhino WIP has several new clipboard enhancements that you will want to try.

Interview with Developer Steve Baer

Rhino WIP Clipboard improvements

The clipboard is a temporary, hidden storage area in your computer’s memory (RAM) that holds data (text, images, files) you’ve copied or cut, allowing you to paste it elsewhere.
This allows data to move between Rhino files, Rhino and other application like AutoCAD or Adobe products, and can just be used to duplicate data with the same Rhino file.

Paste into any version of Rhino Paste from clipboard

Traditionally you could only paste into the current version and previous version of Rhino when placing data in the clipboard. Rhino WIP now copies data that can be pasted into any previous version of Rhino. Copy from the WIP and paste into 5.

CopyToClipboardAt Command (CTRL+SHIFT+C) Copy with base point

This is a new command that lets you specify a base point when copying data to the clipboard. When this is done you will be able to paste with this base point taken into consideration. In other words you can specify a new location to paste data to. This should feel similar to the standard Copy command in Rhino, but with clipboard data instead.

PasteAt Command (CTRL+SHIFT+V) Paste at

In cases where you aren’t able to use the CopyToClipboardAt command (copying from previous Rhinos or other applications to the clipboard), there is a PasteAt command that lets you set the location of your pasted geometry.

PasteAsBlock Command Paste as block

Paste the data in the clipboard as a block in Rhino.

Copy now twice as fast

Copying data into the clipboard involves saving data as a temporary 3dm file. Previous versions of Rhino saved a 3dm for both its current version and for the previous version of Rhino. In the Rhino WIP, only a single save is required which cuts the time to copy data to the clipboard in half.

New ClipBoard Command Assignments on Windows and Mac

Windows


Mac

Why the improvements to the Rhino WIP Clipboard?

The improvements are designed make your work with the clipboard in Rhino more efficient.

  • Prior to the Rhino WIP, you could not paste into older versions of Rhino. You could paste current and one version back. For example, Rhino 8 could only paste to Rhino 8 and Rhino 7, but not Rhino 6.
  • This multiple version copy also caused delays since Rhino needed to save multiple file versions to the clipboard and was not efficient.
  • There was no basepoint used for copying and there was no basepoint used to locate the pasted geometry. The copied objects by default were pasted right on top of the original objects. Often this required an additional move to locate the pasted geometry where it need to be.
  • Also when you pasted the geometry and you really wanted a block, you were then need to create the block with the Block command. This took two commands, but now you can now paste directly to a block instance.

Please try it out and let us know what needs to be done to improve this feature. Copy and paste away!
Clipbaord_improvement_Micro3 Try it

13 Likes

Hello.That’s a really great feature!!

Since Rhino can only copy one item at a time, I think it would be even more convenient if I could copy multiple times in advance using [CopyToClipboardAt].

It would probably consume more memory, though.

1 Like

That’s a really great feature, nice work

I’m not sure I understand this request. Could you elaborate a bit?

1 Like

When there are three sections I want to place, even if I use the CopyToClipboardAt command, only the last copied data can be pasted.

I think it would be convenient to have a command like “paste the data copied second to last.”

1 Like

Since there is a dedicated topic, I would like to bring this Youtrack here again.

Interoperability between Rhino and Designer/Publisher still doesn’t work. I’m very disappointed.

CopyPaste problem, from Rhino to AffinityDesigner or Inkscape - Rhino - McNeel Forum

Hi Jacek -

I see this was commented in RH-38059 Copy/Paste between Rhino and Illustrator/Affinity Designer
I’ve added this thread.

That issue is on the “Future” list at this point.
-wim