-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
μ, ä, ö, å, emoji not accurately displayed in popup menus + saving problem #396
Comments
Posted on Slack by @sagantech, here is |
Heya @sagantech I'm going about applying your diffs to our fork. Which of the MultiByteToChars did you change? All of them or one particular one? Thanks! |
I think you can safely change all of them although when I did it, I only changed the ones that I saw were producing bad results. |
Thanks. As you maybe saw, my first cut at the vstgui fork only included one of your changes. If we agree the way I did it was the way we want to proceed, I can sweep in these others quickly and also send them as pull requests to steinberg. |
I have a new one. I need to create an issue for it but after a popup vstgui calls the invalidate procedure before calling the callback which I think is really weird. Anyway it usually has no bad affect on Surge but in the case where the host audio engine is off, or doing something else, Surge does not display the correct value selected for a popup (waveform/window/etc.) until you select it twice. |
Cool. We are close to having our patch factory up and running. Another issue is best yes. If possible including the changes you make in diff format or with line numbers would make them much easier to apply. Thank you! |
This diff begins building Surge with a fork of VSTGUI rather than the VSTGUI which ships with the vst3sdk pointer. It accomplishes it by the following: 1. there is a fork of vstgui called `surge-synthesizer/vstgui` with a branch called `surge` which is master + diffs 2. There is a submodule in surge called `vstgui.surge` which points at that branch 3. There are changes to premake to point our vstgui implementation This version points to a surge which integrates three of @sagantech's changes Closes surge-synthesizer#394: Cannot move window after selecting preset Closes surge-synthesizer#396: Diacritical marks in menus Changes for submenu checkmarks on windows Also this diff implements our fork strategy described in surge-synthesizer#515 and closes surge-synthesizer#515 as a result.
This diff begins building Surge with a fork of VSTGUI rather than the VSTGUI which ships with the vst3sdk pointer. It accomplishes it by the following: 1. there is a fork of vstgui called `surge-synthesizer/vstgui` with a branch called `surge` which is master + diffs 2. There is a submodule in surge called `vstgui.surge` which points at that branch 3. There are changes to premake to point our vstgui implementation This version points to a vstgui which integrates three of @sagantech's changes Closes surge-synthesizer#394: Cannot move window after selecting preset Closes surge-synthesizer#396: Diacritical marks in menus Changes for submenu checkmarks on windows Also this diff implements our fork strategy described in surge-synthesizer#515 and closes surge-synthesizer#515 as a result. Former-commit-id: ce8bc4274c88df2915b9b3abac26078f273959a6 [formerly 7314657] Former-commit-id: 0c72f1c331f2281cbd9de138a495d999c172a39c Former-commit-id: c97dce7fb3bbc8c8d3a44af05e4c7b8022c6fde1
Describe the bug
Incorrect characters appear in popup.
To Reproduce
Steps to reproduce the behavior:
This appears to be a bug in VSTGUI and can be fixed by changing:
MultiByteToWideChar (CP_UTF8 , 0, utf8Str, numCharacters, allocWideStr, numChars) to:
MultiByteToWideChar (CP_ACP, 0, utf8Str, numCharacters, allocWideStr, numChars)
Expected behavior
I would expect to see proper characters in popup menus.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: