Open
Description
Hi! I was redirected here from HexaEngine/Hexa.NET.ImGui#22 and I have some questions about using this in my app. I took a very brief look over the repository so I probably missed a lot (sorry lol). There are a few features I'd need from this for it to be feasible:
- Either being able to customize the config system path, or being able to skip it all together
- From a brief look it looks like this has its own config system which just writes to
config.json
in the current directory. I currently have my own config system and it'd be nice to just save the window pos/size there and keep my existing code/format - The ImGui app .ini also comes to mind for something to save
- From a brief look it looks like this has its own config system which just writes to
- Configurable fonts, and the option to keep the default font (I love the default Proggy Clean font, but people often need other fonts for accessibility reasons)
- Customizable app icon (not a huge requirement)
- Image rendering
- I currently have a system that tracks the usage of images and automatically disposes old images, so I can write very lazy UI code and scroll through feeds without any issue
Besides these blockers for integration of my existing project, this seems like an amazing project and I will 100% be using it in the future. Do these exist/can they exist/are there workarounds for these? Thanks!
Metadata
Metadata
Assignees
Labels
No labels