Paste: CTRL+V vs ClickPasteText>PasteIntoBox>ClickConfirmPaste

[STR4NG3RdotSH]

I'm sure there's a valid reason for the convoluted paste feature, but I can't think of it. If its possible to paste into a text box and click a button and have it paste on the remote machine, how is it not possible to simply capture CTRL+V and have it skip the un-necessary steps of ClickPasteText>PasteIntoBox>ClickConfirmPaste?

Maybe its a limitation of the KVM it being a web doc (http://your.kvm.ip) and you can't give a webpage access to your clipboard like you can with mic/camera? Maybe because its http vs https? No idea, just spitballing.

[Nevexo]

It's certainly possible, it'd require:

• Capturing CTRL+V and not sending it to the remote side (what if you want it to do that? What if you want to copy within the remote host?)
• Request user permission to access the clipboard (sites usually don't have that)
• Type into the remote host.

The current way allows avoiding the first two, which could lead to more issues than they really solve. I suppose it could be a setting, though.

CTRL+V would have to be intercepted as if the sequence was forwarded to the remote site it could end up pasting whatever the host has in it's clipboard, and then start typing the client-side sequence too.

[STR4NG3RdotSH]

Ah I see. Maybe it could be something like:
if CTRLV
Clear host clipboard
Paste client clipboard
fi
That could avoid accidental pasting of multiple strings?

As for the user permission, I see that could be an issue, maybe even moreso with the jetkvm defaulting to unsecure (http).

Thanks for the additional detail

EDIT: Disregard the clear host clipboard, I just googled it and there's no hotkey or anything for clearing clipboard on most systems. Just manual processes or system settings.

[Nevexo]

I think it'd be best being a toggle, where you can decide if CTRL-V should be intercepted, or just forwarded.

I can't think of a good way to clear the remote clipboard, you'd need to have the machine copy an empty string, but you don't have any context of where the cursor currently is.

Making it a toggle would solve the permission issue anyway, as it'd only request the permission when attempting to turn on the feature, and we could display a message that explains why we need clipboard access (if it wasn't already super obvious!)

I guess it really depends on use-case. If you're full immersed in the remote machine (like using VDI) - you don't need to copy between the client and host, but if you're using it to manage a server for example, you would probably want this feature.

[STR4NG3RdotSH]

Ah yes.

My use case is using local and remote machines for common goals all day, so I do copy/paste between them a lot. I would definitely find use in a toggle of this option if the team got around to implementing it. At the same time I'm sure there's bigger fish to fry as well. I won't die, using the current method as I have been

[Nevexo]

There's a fair bit of work going on around the keyboard implementation at the moment, but once that's all sorted I'll see if we can get it going.