[bug?] v 0.9.1 - unable to paste external text into comment box
On macos 14.7.5, plugdata 0.9.1, VST3 version:
I am unable to paste external text (incl. links) into Plugdata, especially comment boxes. There is no paste menu entry upon right-clicking a comment box, and obviously the paste icon in the top of the context menu does not capture the external copy (from macos, apple-c that is)
Thanks much for all you do!
Please first try the nightly version and confirm. I believe this was already reported and fixed.
@dromer Hi there, thanks for your suggestion. I cant find any related report here, besides #1979 - however that one doesn't cover my case. Can you point me to the report instead, that solved my particular comment-related case? Thanks a lot.
Can you please try the latest nightly first? There have been countless changes to the code since then. The entire canvas works differently etc. etc.
@dromer Okay, why not. I don't want to potentially harm my existing setup, but I'll try. This version v0.9.2-test1 ?
Latest nightly would be better: https://plugdata.org/download.html
Latest nightly would be better: https://plugdata.org/download.html
@dromer and all: Last nightly build does not address my issue. I suppose you would have known, if you would have tried yourself :)
@jayrope ok, good to know.
On macos 14.7.5, plugdata 0.9.1, VST3 version:
I am unable to paste external text (incl. links) into Plugdata, especially comment boxes. There is no paste menu entry upon right-clicking a comment box, and obviously the paste icon in the top of the context menu does not capture the external copy (from macos, apple-c that is)
Thanks much for all you do!
The keyboard shortcut issue is probably related to the specific DAW. It works for me in the standalone and in REAPER on macOS, but it depends on how the DAW handles keyboard shortcuts. In REAPER, it only works if you enable "Send all keyboard input to plugin" for example.
I managed to get the right-click menu working for text/comment/message objects, so now you can use that to work around it :)
Fixed with cd0f361f059e07e00c5ba9f1d1e216abe9ecd330