-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Internal drawing bug #907
Comments
Note about the D3D9/OpenGL backend: For a 500 x 500 pixels window, When I revert the commit 9a9f4f0: with with When I use the commit 9a9f4f0: with with Note about other drawing bugs: with Exemple with float line_thickness = 2, at bottom right, Note 1: regardless of whether the anti-aliasing is enabled or not, the window should always be the same specified size. Note 2: when disabling anti-aliasing lines, you'll probably want to disable borders in your style as well (same as Dear ImGui). Updates: 1. I have fixed the lines not being drawn due to getting -0.5f on offset.x and offset.y. 2. About the problem with line_thickness > 1 when |
Hey, we're glad you're using Nuklear in many projects. Regarding 1px off, feel free to make a pull request with the improvement. I'm actually quite confident we shouldn't just blindly revert the commit, but come up with a better solution - any ideas? Maybe add the "anti-aliasing" also to other parts of Nuklear? |
Hello,
So after investigating a lot, I have found that there is still some internal drawing problems on nuklear.
E.g. #347, #401, #409, #424, #479, #480
On a separate note, the commit 9a9f4f0 is introducing breaking changes on the D3D9 backend, and probably many others.
As this is a serious issue, I am thinking and gathering a maximum of information, before doing a pull request.
I am working on many nuklear project for some time now, and expect some fixes from me.
The text was updated successfully, but these errors were encountered: