Actions
action #14100
closedImplement ClientCutText for VNC to speed up sending text
Start date:
2016-10-07
Due date:
% Done:
0%
Estimated time:
Description
Assuming the backend's VNC server supports *CutText actions we can send text more quickly using the ClientCutText message: https://tools.ietf.org/html/rfc6143#section-7.5.6
Control flow:
- Test case calls type_string or perhaps a new call like paste_string
- Check the guest is in a state which supports the clipboard
- Check the string for any none latin characters or control codes which may break the operation
- Send ClientCutText message in VNC.pm
- Send the appropriate key sequence to perform paste/yank
Similarly ServerCutText can be used to send text in the opposite direction, if the test writer can reliably copy text to the clipboard.
Potential problems:
- The backends may not support the *CutText operations
- It may require a daemon to be running on the guest OS
- Not all software supports the clipboard.
Advantages:
- Faster
- Won't drop keypresses
- May work in most situations
I will investigate further if other attempts to speed up text input are not adequate.
Updated by coolo about 8 years ago
This is the client_cut_text function in qemu in full length:
static void client_cut_text(VncState *vs, size_t len, uint8_t *text)
{
}
Updated by rpalethorpe about 8 years ago
- Status changed from New to Rejected
coolo wrote:
This is the client_cut_text function in qemu in full length:
static void client_cut_text(VncState *vs, size_t len, uint8_t *text) { }
OK, I will close this for now, it doesn't look well supported in the virtualization domain.
Actions