OK guys I've made a new release (https://github.com/slages/love-imgui/releases/tag/0.7) with the last fixes and improvements, and I added some hand made bindings for overrided functions like imgui.Value, instead of using imgui.Value_2, imgui.Value_3, etc... Just use imgui.Value and it will select the best override depending on what you send to it, for instance:
I tried to automatize the process but it wasn't able to find a proper solution for it, so I added those bindings manually:
"Value"
"ValueColor"
"CollapsingHeader"
"TreeNodeEx"
"TreeNode"
"Combo"
"RadioButton"
"PushID"
"GetID"
"PushStyleVar"
"SetWindowPos"
"SetWindowSize"
"SetWindowCollapsed"
"SetWindowFocus"
"BeginChild"
Any chance of getting InputText to work? It requires a callback for updating the state I think (Or does it modify the buffer? if so, it should return the updated string as 2nd argument, too, like windows with "close" buttons do).
EDIT: nevermind. it's working wonderfully, I just accidentally set the buffer size to 0.
Just to show off, here's are my debug tools atm:
The console is working great, I basically copied it from the imgui_demo.cpp example.
Really nice, I'll add it to the first post galery! Glad to hear it about the console, I'll probably use it in my project too, and I'll soon implement the log window too, it's something I desperately need for a long time.
RamiLego4Game wrote:Just wondering, How can I create a multiline textbox with Lua syntax highlight..
Edit: Also, Why not adding this library to the wiki ??
Unfortunately there's nothing out of the box to get colored text in a multiline input box, but I found this thread talking about it: https://github.com/ocornut/imgui/issues/200
So it seems to be part of the todolist, but not sure when he will tackle it.
And yes, we should add it to the wiki, I'll have a look into it!
Just to let you know that I finally got my hands on a Mac, so I added to the pre-built binaries the MacOS X version of the module, I tested it quite a bit and it works just fine (it took me some time to figure out where to put it to get it properly loaded, first time that I use a Mac, hehe...).
Is there any reason you're not producing win64 builds? It's a real bummer to have to downgrade my LÖVE version (or to build my own constantly) for this to work. Requiring the module was causing a right fit with the 64bit version of LÖVE. (One of the small pains that makes me long for luasec to ship with LÖVE.)
Also, having the dll anywhere but the root of my project (right next to main.lua) seems to raise this error. I would really prefer to not have to have this dll next to the love executable / my main.lua file.
sandsmas: A LÖVE Editor My Libraries: Imgur, Palettes, Music Macros, Timer, Hooks
EntranceJew wrote:Is there any reason you're not producing win64 builds? It's a real bummer to have to downgrade my LÖVE version (or to build my own constantly) for this to work. Requiring the module was causing a right fit with the 64bit version of LÖVE. (One of the small pains that makes me long for luasec to ship with LÖVE.)
Also, having the dll anywhere but the root of my project (right next to main.lua) seems to raise this error. I would really prefer to not have to have this dll next to the love executable / my main.lua file.
I'll have a look into providing a x64 version! It's just that I've no use for it on my side, but I'll try to find a bit of time to create it.
And yes you can move it somewhere else, you just need to update your cpath for it, here's for instance what I'm doing on my side to select the appropriate version depending on the current OS: