As soon as you start dragging “My View 379” in the editor, you get this abort/error message.
Do you want me to create an issue on the vstgui github project?
Note: in the previous post, the reason why reducing the size of the window would make a difference is because the control that is triggering this issue ends up being not visible anymore, hence not rendered, hence the problem disappear…
I am glad you were able to reproduce the issue and fix it. What does that mean for SDK 3.7.9? In this state, it is broken for Windows. Are you going to release an update for the SDK? How are you going to handle it?
It’s a bug not anyone is affected. You need to render a polygon to trigger it. No view or control shipped with the SDK uses it so I don’t think an update is needed. People can update vstgui to the latest GitHub version if they are affected.
I would argue that SDK 3.7.9 contains a breaking bug. The fact that the bug does not impact any widgets rendered by the SDK is irrelevant. Any user using polygon (which is not an obscure feature) will be affected. The fact that VSTGUI can be updated “separately” to fix the bug is not very user friendly.
If you don’t want to release a fixed SDK, I would suggest, at the very minimum, to add a very big disclaimer in the release notes so that other user don’t waste hours trying to figure out why their code is suddenly not working…
should already use cached graphics path objects instead as it is more performant on modern graphics systems.
The version of VSTGUI was already released a few month ago and no one has reported the issue yet, so it is not widespread in use at all. I will change the SDK on GitHub so that anyone cloning the SDK afterwards will get the fix.