You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ok, so I'm creating a database font editor, and I'm using a canvas to render the fonts using love's rendering functions because it's easier than figuring out how to use fonts with imgui (which is my bad).
But here's the thing: when the canvas makes the window become big enough to have a scrollbar, it causes this:
But when you scroll down all the way, or when you set focus to other imgui windows, or even when a tooltip shows up, it goes back to what it's supposed to render:
Note that the background also becomes white, when it was supposed to be gray. It looks like the canvas is not unsetting itself, maybe?
Since this is a problem with love2d's canvases, I assumed this would be an issue in the wrapper for love2d, and not necessarily imgui itself. There are many workarounds I can think of, but if there is an actual problem with the actual wrapper I thought it'd be better to address it. I hope it's ok to post this issue.
The text was updated successfully, but these errors were encountered:
Ok, so I'm creating a database font editor, and I'm using a canvas to render the fonts using love's rendering functions because it's easier than figuring out how to use fonts with imgui (which is my bad).
But here's the thing: when the canvas makes the window become big enough to have a scrollbar, it causes this:
But when you scroll down all the way, or when you set focus to other imgui windows, or even when a tooltip shows up, it goes back to what it's supposed to render:
Note that the background also becomes white, when it was supposed to be gray. It looks like the canvas is not unsetting itself, maybe?
the code looks like this:
Since this is a problem with love2d's canvases, I assumed this would be an issue in the wrapper for love2d, and not necessarily imgui itself. There are many workarounds I can think of, but if there is an actual problem with the actual wrapper I thought it'd be better to address it. I hope it's ok to post this issue.
The text was updated successfully, but these errors were encountered: