Vladimir Ein

A note on deprecated keywords: I've suggested `DEPRECATED_REMOVE_KEYWORD_ARG` in a couple of places. For all these cases, we need to document: - why the keyword is being removed; - what...

A couple of words on declaring arguments deprecated. Right now, DPG has two options to deprecate an argument: - `DEPRECATED_RENAME_KEYWORD_ARG` will issue a warning and pass the argument to C++...

A note on key modifiers in the plot (this seems to be the only place where we can pass modifiers): While it might look natural to pass `dpg.mvKey_None` to disable...

> When adding new axes now you need to specify which ones (i.e. `dpg.add_plot_axis(mvXAxis2)`) This breaks the old behavior of having multiple Y axes of type `dpg.mvYAxis`. While I'm all...

Yeah, kind of that. We can even define a new constant, like `dpg.mvKey_ModDisabled`, to abstract off that "-1", and make it more readable. And then maybe add a note in...

I'm done with my "first pass" through the changes. Once all comments I added above get resolved in this way or that, I'm going to scan through the changes once...

Here is a list of all the new and deprecated arguments and functions - I think we'll need to add it to Release Notes. Going to update this list right...

Do you want to open the Metrics window or to see what's under the cover? To open it, use `dpg.show_metrics()`. The Metrics window itself is implemented in C++, you can...

Take a look at this comment: https://github.com/hoffstadt/DearPyGui/issues/2257#issuecomment-1899936296.

What's the range of your Y values (`energy`) ? It might help if you set `no_tick_marks` on the Y axis to False for a while - to see if the...