sistemicorp

Note: a drawback to using the mouse event to fake a `wait_for_input` is that if the mouse is not over the application the faked mouse event does not get sent...

Template for a work around using the render loop. ``` from threading import Timer, Lock import dearpygui.dearpygui as dpg dpg.create_context() dpg.create_viewport(title='Custom Title', width=600, height=300) with dpg.window(label="Example Window", tag="mywin", width=300): dpg.add_text("Hello...

Perhaps there is a glfw solution per the [docs](https://www.glfw.org/docs/3.3/input_guide.html), Event Processing section. Specifically, If the main thread is sleeping in glfwWaitEvents, you can wake it from another thread by posting...

Spent an afternoon trying a solution tho this problem but failed. I thought I would detail what I tried in case someone can suggest something. The Linux platform was used...

Minimal example to test new feature, ``` from threading import Timer import dearpygui.dearpygui as dpg import time # Expected Result: # - DPG frame rate is > place new feature...

Some experiments, Adding compile flag `--full-compat` made no difference. Changing class callback to, ```python def cb_button2(*args): print(args) ``` Showed (compiled), ``` (,) ``` The Python run showed the exact same...

I tried several ways to see what the extra argument that Nuitka is passing in, but I failed to determine it. I did this by trying variations of the method...

Thank you for the feedback, I have passed this along to the DPG devs. Meanwhile, more test info... I changed the code to this, and I press the buttons in...

Also, using a lamda function also works around the issue, as shown for `button3`, ```python class myClass(object): def __init__(self): pass def cb_button1b(self, sender, app_data, user_data): print(f"B1b sender: {sender} {app_data} {user_data}")...

I am testing the patches on behalf of the devs. Your comments have also been very helpful!