Hello,
Suggestion: it feels like the code generating the .ash file could emit the value using the value defined in imgui.h rather than hardcoded power of two:
" enum ImGuiInputTextFlags \r\n"
" { \r\n"
" eImGuiInputTextFlags_None = 0, \r\n"
" eImGuiInputTextFlags_CharsDecimal = 1, // Allow 0123456789.+-*/ \r\n"
" eImGuiInputTextFlags_CharsHexadecimal = 2, // Allow 0123456789ABCDEFabcdef \r\n"
" eImGuiInputTextFlags_CharsUppercase = 4, // Turn a..z into A..Z \r\n"
" eImGuiInputTextFlags_CharsNoBlank = 8, // Filter out spaces, tabs \r\n"
" eImGuiInputTextFlags_AutoSelectAll = 16, // Select entire text when first taking mouse focus \r\n"
" eImGuiInputTextFlags_EnterReturnsTrue = 32, // Return 'true' when Enter is pressed (as opposed to every time the value was modified). \r\n"
etc.
This will make the generator code a little less readable. But please note that dear imgui provide no binary forward compatibility and those values are expected to change (and regularly are changing).
Regards.
Hello,
Suggestion: it feels like the code generating the .ash file could emit the value using the value defined in imgui.h rather than hardcoded power of two:
etc.
This will make the generator code a little less readable. But please note that dear imgui provide no binary forward compatibility and those values are expected to change (and regularly are changing).
Regards.