Vladimir Ein

Did you mean the option "picker_mode", not "color_picker"?

As to why this happens: - Without the fix, `_before_id` points to the first child of a horizontal group. - Then `_add_config_options` inserts a table into that group, and puts...

Another approach to fix it could be to insert the table before that horizontal group: ```py with dpg.group(horizontal=True) as _before_id: dpg.add_text("picker_mode:") ``` This doesn't require an extra empty group.

Callbacks are intended for your code to react to **user actions** - i.e. to something outside of your control. From your app's point of view, such events occur at random...

Is there any reason this ticket stays open?

@cromachina have you had a chance to read my comments? Do you need more help, explanation or something?

It crashes in `mvFileDialog::getInfoDict()`, in the very first call to `PyDict_SetItemString()`, which extracts file name from `ImGuiFileDialog` and feeds it into `ToPyString()` (and consequently `PyUnicode_FromString()`): ```cpp PyDict_SetItemString(dict, "file_path_name", mvPyObject(ToPyString(_instance.GetFilePathName()))); ```...

Another piece of wisdom can be found in [this comment on #299](https://github.com/hoffstadt/DearPyGui/issues/299#issuecomment-1305007580).

> Has this been implemented in DPG? I can't tell for sure but I bet it hasn't. Just because nobody really needed it. It's basically a set of shade series...

Here's what probably happens behind the scenes. There's a discussion on the Nvidia forum that has given me an idea (another discussion on Discord revealed that this issue occurs on...