Still a Lua newb, and probably will be always.
I am writing a utility that populates a large table and then displays information from that table. I initially populated the table in my main Lua init function and noticed that it took a significant time to complete. So much so that I figured it would not be viable to update the information in the table within my ImGui loop (talking 0.5 seconds or so here), but I wanted the information to be 'live' in the UI. Anyway, I tried moving the table population into my ImGui loop and it appears to speed up immensely, like hundreds of times or more.
I read some of the intro 'Lua on MQ' documentation, and my guess is that 'turboNum', which defaults to 500, is at play when running the function at initialization but that 'turboNum' does not apply when in the ImGui function (which makes sense of course). I was wondering how to go about changing 'turboNum' from the default 500 to something larger so that I can test out code in the main loop while still getting a realistic idea of how long it would take when running in the UI. Can this be done runtime as with macros? What would be the sytax?
I am writing a utility that populates a large table and then displays information from that table. I initially populated the table in my main Lua init function and noticed that it took a significant time to complete. So much so that I figured it would not be viable to update the information in the table within my ImGui loop (talking 0.5 seconds or so here), but I wanted the information to be 'live' in the UI. Anyway, I tried moving the table population into my ImGui loop and it appears to speed up immensely, like hundreds of times or more.
I read some of the intro 'Lua on MQ' documentation, and my guess is that 'turboNum', which defaults to 500, is at play when running the function at initialization but that 'turboNum' does not apply when in the ImGui function (which makes sense of course). I was wondering how to go about changing 'turboNum' from the default 500 to something larger so that I can test out code in the main loop while still getting a realistic idea of how long it would take when running in the UI. Can this be done runtime as with macros? What would be the sytax?