Skip to content

Question: migrating backends to new Fonts setup #8735

@gucio321

Description

@gucio321

Version/Branch of Dear ImGui:

Version 1.92.0, Branch: docking

Back-ends:

ebiten backend from https://github.com/AllenDang/cimgui-go

Compiler, OS:

Arch + wayland (doesn't matter)

Full config/build information:

doesn't matter

Details:

My Issue/Question:

Hi,
I'm a little bit confused with the release of 1.92 tbh 😄
I'm doing a migration on cimgui-go right now (AllenDang/cimgui-go#448)
And got stuck with our ebitenbackend. (we were adding this and asked questions here in #7372, #7405).

Is there any "tutorial" about migrating fonts stuff already? How should my backend handle fonts now?

Also, I know this is not preffered, but can I (abstracting from my backend issue, just in a normal code) store TextureID somewhere and every time I want to display image convert it to TextureRef (I mean create it every frame) or this is a HUGE mistake?

Screenshots/Video:

No response

Minimal, Complete and Verifiable Example code:

N/A

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions