This repository has been archived by the owner on Dec 2, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
pixel centers #347
Comments
Wow, totally forgot to reply on this. -0.5f doesn't do the trick, but -1.0f does. I can make that demo fill the entire window by moving the window around. However, I didn't see a maximize button so I manually filled it out, and I can manually move the window to a negative x / y coordinate. |
Just wanted to bump this, let me know if there's any more info I can provide. |
Hm just a quick guess. What happens if you activate window border or increase and decrease the border width? |
Interestingly, I just went to repo and realized I believe this only repros for me when I'm running the official NVIDIA drivers vs mesa. Will change drivers back to NVIDIA soon soon and try to repro again. |
ghost
mentioned this issue
Sep 19, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On menus that are rendered starting at (0, 0) I'm having an issue where I see a 1 pixel line at the top of the menu across Windows / Mac / Linux platforms. From a quick look, this seems to be related to the 0.5 offset applied to each vertex coordinate generated from inside of nuklear.
I'm not a graphics buff, but it seems that applying this offset here may be causing a fragment to not be generated during rasterization as the pixel is assumed to be outside of the primitive (precision issues?). Should the 0.5 really be being applied by nuklear when generating the coordinates?
Edit: To note, I'm rendering with AA, padding spacing, borders, etc. all off and removing the offsets does indeed fix the issue I'm experiencing.
The text was updated successfully, but these errors were encountered: