editUsesParsedPaste property
If true, the color code entry field uses parsed paste action for keyboard shortcuts CTRL-V and CMD-V,
A standard text field, will just paste whatever text is in the copy/paste
buffer into the field. This is the false default behavior here too,
with the exception that the field only accepts valid hex value input
chars (0-9, A-F), so it always filters and pastes only the acceptable
input chars from the paste buffer.
If this property is true, the edit field will use the same color
paste value parsing used by the other paste actions used when the input
field is not in focus.
This results in a paste action in the field that always fully replaces
the content with the parsed color value of the pasted data, not just
pasting in the string in the paste buffer over selected text.
Currently this setting only impacts CTRL-V and CMD-V keyboard shortcut pasting on desktops. The paste on Android and iOS are not intercepted when this setting is true.
Defaults to true.
ERRATA INFO:
This setting was in version 3.6.0 changed to be true by default. The feature had been broken and missing since version 3.4.0 and the default behavior from 3.4.0 and forward was the same as setting this to true, there was no false feature. Generally it is recommended to keep this setting true for a more consistent and better paste experience. Thus decided to make it true by default, which matches the behavior of the past versions 3.4.0 and 3.5.0. The true behavior is also what pretty much all uses cases should use. Was about to deprecate this setting and remove it in version 4.0.0, but decided to keep it undeprecated for now since it works as stated again.
The false setting is equivalent to past versions (1.x) default behavior when pasting strings into the code entry field.
Implementation
final bool editUsesParsedPaste;