Input field blank when copy-pasting from excel cell

[Former user]

v0.12 on Windows.

Open LibreOffice Calc (probably also same result in MS Excel), type a number in a cell. Copy-paste the cell (not from the formula, but from the cell) and paste it into SpeedCrunch.

Speedcruch input field will stay blank. However, it will percieve the value, e.g. showing a tooltip of the result. Typing more number will sometimes keep the input field blank, but the tooltip of the result is correct.

[Helder Correia]

Can you please attach a screenshot? I wonder if the issue is that you are copying text color too.

[Bruno]

It is the same result with or without colors (text/background). Here are some screenshots:

[Tey']

If you use the ⍇ key of your keyboard after pasting the cell content, you should find the number. Basically, there's a newline character at the end of whatever LibreOffice copies to the clipboard, and since our editor only shows 1 single line, you cannot see the number unless you put the cursor to the previous line.

We should replace newline characters (\r and \n) in text pasted into the editor. I wouldn't be surprised if there's an option to filter them in the widget (but cannot check for now).

[Bruno]

Backspace to delete the newline character doesn't always seem to work. It seems copy-paste from a Libreoffice Calc cell adds two character in front of the number. Even if I spam the backspace several times after the input field is gone, the input field shows no characters when typing. I have to ENTER to make it work again.

I've tried the same in 0.11 no problems there, one backspace and the newline is gone and I can see the characters in the input field.

[Tey']

Fixed #877 (issue when pasting empty lines)

→ <<cset 372305b12a60>>

[Tey']

Issue fixed in code.

It will be part of the next release (1.0, no ETA), but you can download the latest nightly build here if you need the fix now (just wait tomorrow before downloading it, as the changes will be built tonight).

[Tey']

Issue #1014 was marked as a duplicate of this issue.

[Tey']

Issue #1000 was marked as a duplicate of this issue.