I've searched, but did not find this reported....
In order to paste a blueprint (or blueprint book) string, the GUI requires that you open and dismiss the import dialog once before allowing you to paste.
If you open the dialog the first time and type command-v to paste, the box receives a "v" character.
After escaping and re-opening the import dialog, the dialog will accept the string from the clipboard properly.
I tried using ctrl-v to paste - same result.
Tested on 0.15 stable and 0.16 latest.
Mac OS X 10.11.6
EDIT: Pasting into a text editor as an intermediate step makes no difference.
[Antron] [0.16.x] Mac OS X Import blueprint string bug
- ThrashNeon
- Burner Inserter
- Posts: 14
- Joined: Sun Mar 11, 2018 4:05 pm
- Contact:
Re: [HanziQ] [0.15.x][0.16.x] Mac OS X Import blueprint string bug
I cannot reproduce that, is there anything specific about your system - rebound keys, either in the system, or with some other software?
Also please post the log file.
Also please post the log file.
- ThrashNeon
- Burner Inserter
- Posts: 14
- Joined: Sun Mar 11, 2018 4:05 pm
- Contact:
Re: [HanziQ] [0.15.x][0.16.x] Mac OS X Import blueprint string bug
No rebound keys, no input keymapping or clipboard software installed, all keyboard shortcuts are set to factory defaults in System Preferences.
Copy/Paste works normally for everything except Factorio (I use it constantly).
Also, the same behavior in the map exchange string field.
On first open, click in it to expand, command-v to paste, and a "v" character is input.
Close and immediately reopen map dialog, and paste is received correctly.
Log attached
Copy/Paste works normally for everything except Factorio (I use it constantly).
Also, the same behavior in the map exchange string field.
On first open, click in it to expand, command-v to paste, and a "v" character is input.
Close and immediately reopen map dialog, and paste is received correctly.
Log attached
- Attachments
-
- factorio-current.log
- (17.65 KiB) Downloaded 158 times
Re: [HanziQ] [0.16.x] Mac OS X Import blueprint string bug
Apart from trying a different keyboard (which should not have an effect on this fault behaviour, but you never know), I don't know what else to try. For 0.17, we're rewriting all of the input-handling related code in Factorio, so my only hope is, that it will be fixed by that.
-
- Manual Inserter
- Posts: 1
- Joined: Thu Oct 18, 2018 12:17 am
- Contact:
Re: [HanziQ][for 0.17][0.16.x] Mac OS X Import blueprint string bug
I just wanted to say that I am experiencing the same issue on OSX. Pressing Ctrl+V just results in the character `v` being placed in the Import text field.
The 'workaround' of opening and closing the input blueprint string form did not work for me.
The 'workaround' of opening and closing the input blueprint string form did not work for me.
Re: [HanziQ][for 0.17][0.16.x] Mac OS X Import blueprint string bug
Command+V is used in macOS to paste, not Control+V.robertmassaioli wrote: ↑Thu Oct 18, 2018 12:25 amI just wanted to say that I am experiencing the same issue on OSX. Pressing Ctrl+V just results in the character `v` being placed in the Import text field.
The 'workaround' of opening and closing the input blueprint string form did not work for me.
Re: [HanziQ][for 0.17][0.16.x] Mac OS X Import blueprint string bug
I have always experienced this.
When attempting to paste using CMD+V, the first time only the "V" goes through, but after deleting it (I don't close/reopen, I just delete the "V"), it'll paste fine (by CMD+V'ing again).
Steps to reproduce:
https://www.dropbox.com/s/f4n9g6d2ydi98 ... g.mp4?dl=0
When attempting to paste using CMD+V, the first time only the "V" goes through, but after deleting it (I don't close/reopen, I just delete the "V"), it'll paste fine (by CMD+V'ing again).
Steps to reproduce:
https://www.dropbox.com/s/f4n9g6d2ydi98 ... g.mp4?dl=0
Re: [Antron] [0.16.x] Mac OS X Import blueprint string bug
This seems to be fixed in 0.17. I just tried it on 0.17.18, and Command+V worked as expected. Would you mind checking again?
Re: [Antron] [0.16.x] Mac OS X Import blueprint string bug
This was indeed fixed in 0.17.x.