dpg.set_axis_ticks() does not work as expected

[sedenka]

Version of Dear PyGui

Version: 1.6.3 (master@9989e6f)
Operating System: Windows 10

My Issue/Question

The function dpg.set_axis_ticks() is struggling to recognise proper axis to work with. It was working properly in the 1.6.2 but it is broken in the above-mentioned commit. Moreover, adding a colorbar dpg.add_colormap_scale() causes flipping of the axes (all the ticks are put on the y-axis instead of the x-axis). The issue may be related to #1852.

To Reproduce

Steps to reproduce the behavior:

1. Run the code
2. See tick labels

Expected behavior

The code should set tick labels a-c to the y-axis and a-f to the x-axis.

Screenshots/Video

1.6.2 (works as expected):

1.6.3 (built from source):

1.6.3 (built from source) with colormap scale modification:

Standalone, minimal, complete and verifiable example

# Here's some code anyone can copy and paste to reproduce your issue
import dearpygui.dearpygui as dpg

dpg.create_context()
dpg.create_viewport(width=300, height=200)

values = (0.8, 2.4, 2.5, 3.9, 0.0, 4.0,
          2.4, 0.0, 4.0, 1.0, 2.7, 0.0,
          1.1, 2.4, 0.8, 4.3, 1.9, 4.4,
          0.6, 0.0, 0.3, 0.0, 3.1, 0.0)
xticks = (("a", 0.0), ("b", 0.2), ("c", 0.4), ("d", 0.6), ("e", 0.8), ("f", 1.0))
yticks = (("a", 0.0), ("b", 0.5), ("c", 1.0))

with dpg.window(label="Example Window", tag="Primary"):
    with dpg.plot(height=-1, width=-1):
        xaxis = dpg.add_plot_axis(dpg.mvXAxis, label="x")
        dpg.set_axis_ticks(xaxis, xticks)
        with dpg.plot_axis(dpg.mvYAxis, label="y") as yaxis:
            dpg.set_axis_ticks(yaxis, yticks)
            dpg.add_heat_series(values, 4, 6, scale_min=0, scale_max=6)

dpg.setup_dearpygui()

dpg.show_viewport()
dpg.set_primary_window("Primary", True)
dpg.start_dearpygui()
dpg.destroy_context()

Modified code:

...
with dpg.window(label="Example Window", tag="Primary"):
    with dpg.group(horizontal=True):
        dpg.add_colormap_scale()
        with dpg.plot(height=-1, width=-1):
...

[wlwatkins]

have you managed to get some new results? i guess looking at #1897 nothing has changed.

although i cannot reproduce the working with your code and v1.6.2

[hoffstadt]

Fixed in next release.