Updating backend ImGui/ImPlot/ImNodes to latest versions #2275

SamuMazzi · 2024-02-07T09:02:42Z

name: Updating backend ImGui/ImPlot/ImNodes
about: Updated backends
title: Updating backend ImGui/ImPlot/ImNodes
assignees: ''

Description

This PR aims to update the Im* backends of DPG to way more recent versions.
Currently DPG relies on ImGui 1.83 (last commit around May 2021), ImPlot 0.11 (always around that date) and ImNodes (which is the less updated). With this PR we'll have ImGui 1.90.6 and ImPlot 0.17 (for the major updates see below).

Background: ImGui is currently sponsored by big tech companies like Adobe, Blizzard, Activision, etc. so we can expect a lot of improvements with the update (there are already ton of them) and we can expect a lot of people working on the really ugly/hard things like graphical backend libraries.

Why?

In my workplace we are about to ship a product based on DPG. Because of my job, I had to edit the backend and then I found out that what I edited was already modified in the new ImGui and then I also found out that the ImGui version we were relying on in DPG was really old.
We want to stick with this library but I honestly told them that I don't see the point of relying on an almost dead (okay, no, maintenance mode) library, so we decided to either upgrade it or drop it and replace it with something else.

I know that this is quite a huge change, and that several problems can arise but I also think that it can be definitely worth it. Also with this huge community all of these changes can be "easily" tested.

Changes

If you want to take a look to the original releases you can find them here for ImGui and here for ImPlot
You'll probably find better explanations (and images/videos) of what I'm gonna tell you below.
(Keep in mind that many other improvements have been made, but these are the most important ones in my opinion)

OpenGL

(This has been on of the hardest problem to solve actually)
Currently, for the build, DPG relies on gl3w in the examples folder of ImGui. This doesn't sound like a really stable thing and indeed a couple of releases later, that's been removed, so I added gl3w directly in the thirdparty folder.
Also ImGui decided to make some heavy changings in order to be more cross-platform. One of these, which is also my biggest concern about all of this work, is about the buttons of the keyboard. These are now less than before, and they have been all mapped to predefined values in ImGui. So if someone used them heavily now they could have some problem.

Issues solved (afaik)

Fix destroy_context doesn't clean up the window #2173, Window freezes when using stop_dearpygui #2013, Viewport stuck after closing when executing blocking instructions afterwards on MacOS #1593 (last 2 issues are closed but not solved, but they are all related)
Fix add_text_point raises exceptions even when used with only required inputs #2108
Fix dpg.set_axis_limits just lock the axis min limit and let the max limit be free (+vice versa) #2016

New Features

For all the Drag* widgets there are new parameters delayed, no_cursor, no_fit, no_inputs
Now there can be 3 X axes other than the currently supported 3 Y axes
Plots: now you can decide a _mod button to enable certain actions only when that button is pressed (i.e. select, zoom, override, etc...) and you can also decide the zoom rate
New StackToolWindow
Plots: many parameters have been added to each kind of plot
Plots: new series like Infinite line series (just a wrapper for Vertical and Horizontal line series), Digital Series, Group Bar Series
Plots: New way to query the plots (take a look at the demo)
Plots: new functions set_axis_limits_constraints() and set_axis_zoom_constraints()
Plots scale: there are currently four scales for the axes' plots, but more will be added and in the roadmap there's the goal to implement, like in ImGui, a custom callback scale.
dpg.add_plot_tag(): now there can be tags attached to the axes
New widget: SeparatorText()
Several updates to tables (some of them still have to been implemented)
CTRL + Tab navigation across windows
New params for InputText
New params for dpg.add_window()
New params to dpg.add_legend()
More params for ColorMapScale
Add recursive mode to filter_set (beta)
New param "disabled" for dpg.add_group() (equivalent of new feature ImGui::BeginDisabled())

Breaking changes

get_plot_query_area() deprecated in favour of get_plot_query_rects()
New mvStyleVar options
When adding new axes now you need to specify which ones (i.e. dpg.add_plot_axis(mvXAxis2))
Now all the lines will automatically have AA
Added several params to dpg.add_child_window()
mvVLineSeries and mvHLineSeries are deprecated in favour of mvInfLineSeries

Changes expected in the future from ImGui

Major concerns

As I said earlier, now there are less keyboard buttons than before, I think that they'll add more in the future, but I don't know how to solve this problem.
In my workplace we have never used ImNodes so we haven't tested that a lot. There haven't been any huge updates during these years so there shouldn't be a lot (or any) problems. If someone's willing to help and take a look, they'd be welcome.

Notes

Everything was tested with Valgrind in order to be sure that there wasn't any kind of accidental memory leak (or at least not more than those who were already there).

Don't look at the README.md and TODO.md, it's nothing but development garbage, it'll be removed when merged. In case you'll read the TODO you'll see that there are still many (not too many) things to do. These are all new features and I'd say, almost all little ones, or difficult to implement, so they can actually be implemented later in the future.

My main goal here was to have a real feedback from the most expert users on this work.

I hope I was clear enough!
I'd like to improve this library because I think it's really great, so any kind of suggestion will be well accepted.

- added submodule implot - discontinued docking support - updated documentation - bump imgui and implot versions to ImGui 1.83 and ImPlot 0.13 - renamed variables to match the new backend - added new flags to several plots - Added legacy support for new IO backend - Changed (but not functioning yet) query in plots - Added gl3w to "thirdparty" to avoid dependency in imgui "examples" folder - Modified build process - Added style variable `mvStyleVar_DisabledAlpha` - Added flags to Drag* widgets

For those who're wondering, it wasn't possible to do an incremental update to the latest version mostly because of several problems with the OpenGL libraries. In the end, bump directly to the latest version seemed the most stable and overall best solution. - `str_ends_with` added to check images extensions - assertion enabled - Implemented some of the ImGuiChildFlags - Removed old parameters for plots - Mocked (/commented) several functions so that they can be improved later (ImageButton, ColormapScale, PlotXLines, etc...) - Cast every key input to ImGuiKey - IMPORTANT: Changed GetItem logic because it was deeply broken (for some unknown problem, so maybe the problem is still there) - Removed useless dependencies - Assigned default values in struct for mvPlotConfig "_mod" - Replaced `IM_OFFSETOF` with `offsetof` - Updated ImGui to version 1.90.1 - Updated ImPlot to version 0.16 - Updated ImNodes to latest release - Added TODO.md

- added Infinite Line Series - udpated todo

- Start migration to new IO (deleting GetKeyConstants) - Update all .py files - Updated some of the flags of plots (still not all of them) - Added if statement to BeginTooltip, to mantain consistency with other widgets - Add "SeparatorText()" - Add script to build and generate python files automatically - Started Stack Tool window - IsMouseDoubleClicked() -> GetMouseClickedCount() as suggested in ImGui - Fixed metric windows - Several refactors - New table params

- Removed keys data structure - Fix regression custom series - Fix drawing plots

Also: - added parameters for stairs plot

Also: - removed deprecated keys - fix typo in param of subplots function

- Fix no_outliers typo - Clean .md files - Added flags for InputText

- Added GroupBarSeries - Reimplemented quering in plots - Cleaned internal mvPlotConfig - Fixed demo

- Removed 'area_series` in favor of `line_series` + `shaded` flag - Added remaining flags to plots - Refactor of `XSeriesConfig` structs - Added some mvKeys - Updated documentation mainly for DragTools and ChildWindow

- Added ImageSeriesFlags - Update implot version

- Fixed ColormapScale and added flags - Added DigitalSeries - Updated demo, also removing dependency to numpy

src/dearpygui_commands.h

v-ein · 2024-05-05T07:49:29Z

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++ with a new name.
DEPRECATED_REMOVE_KEYWORD_ARG will issue a warning and won't pass the argument at all.

I'd suggest that we add one more option, where a warning will be issued but otherwise the argument will be passed into the C++ part the way it did before, with its original name. This can be used for arguments that we want to retain for backward compatibility (maybe delete later), but also want to point the user to a newer, better way to do the same thing. We can name it simply DEPRECATED_KEYWORD_ARG. It will also need an extra message coded in argument definition, so that we can say something like "use argument X instead".

src/mvAppItem.cpp

src/mvPlotting.cpp

src/mvAppItem.cpp

v-ein · 2024-05-05T22:10:46Z

src/mvAppItem.cpp

-        setup.about = "Adds an error series to a plot.";
+        args.push_back({ mvPyDataType::DoubleList, "values" });
+        args.push_back({ mvPyDataType::StringList, "label_ids" });
+        args.push_back({ mvPyDataType::Integer, "item_count" });


item_count and group_count: We already have the total length of the values list, and can therefore deduce one of these arguments from another. I suggest to replace them with a single value specifying the number of bars in a group, and name it group_size (see also comments on the current group_size argument below). Then then number of items can be calculated from the list size.

What's more, I think we need to add more safety around list sizes. Right now, if labels is shorter than the number of groups, DPG will segfault. Since both values and labels are positional args (i.e. both will for sure be passed in), we can check that their sizes are correct (e.g. values is a multiple of group_size, and labels is no longer than len(values)/group_size), and raise an exception if they aren't.

Where do you suggest to put these checks? I was thinking in the draw function: maybe it's not the ideal place to put them, but otherwise I should put them in set_positional_configuration, set_configuration and fill_configuration_dict and I should replicate code and I don't love it tbh.

The drawback of checking them in draw_group_bar_series is that we can't raise an exception there. I'd prefer to signal the error right away. This means we need to check these sizes in set_positional_configuration and set_configuration, but not in fill_configuration_dict. To prevent code duplication, let's add a helper function like ValidateBarGroupConfig(mvGroupBarSeriesConfig& outConfig) and call it from both set_positional_configuration and set_configuration. You can even declare it static so that it's not visible outside of mvPlotting.cpp.

To raise an exception, use mvThrowPythonError. If I remember correctly, there's no need to return anything to Python in this case. Don't look at how DPG does it - in many cases throughout DPG code, it returns None after mvThrowPythonError - this is actually wrong and it crashes in debug mode (documented in #2097).

Okay, I was implementing this and then I recognized that if I use the function as you told me (with mvGroupBarSeriesConfig& outConfig as parameter) I can check the state only when it's already been set, then if there's some error I should restore back to how it was.
Or mvThrowPythonError takes care of it by itself? (But I don't think so)

mvThrowPythonError will just store exception info inside of Python so that when it gets back from C++, it raises the exception.

Yes, looks like we need to either back up the old state, or to have a function like SetBarGroupData(mvGroupBarSeriesConfig& outConfig, some-other-parms) that would store values, labels, and group_size in the config in a single atomic operation (first checking that new values are valid). "Some-other-parms" here could be three PyObject* obtained from keyword args or from positional args, and SetBarGroupData would parse them into local variables, replacing NULLs with values from the config. It can then validate the values and store in the config.

src/mvAppItem.cpp

src/mvAppItem.h

Now it's based on the detection of the OS and no more on the function `strnicmp` itself

src/mvAppItem.cpp

v-ein · 2024-05-06T22:04:23Z

src/mvAppItem.cpp

-        args.push_back({ mvPyDataType::Double, "y" });
-        args.push_back({ mvPyDataType::Integer, "x_offset", mvArgType::KEYWORD_ARG });
-        args.push_back({ mvPyDataType::Integer, "y_offset", mvArgType::KEYWORD_ARG });
+        args.push_back({ mvPyDataType::DoubleList, "x" });


x, y: Changing these to list-type and at the same time asking the user to only pass one element (rather than enforcing it via type system) looks really weird. What's the reason behind this?

I think it was because of consistency with all the other series... I'm pretty sure I tried to accept single elements but I couldn't. Anyway I'll try again and I'll tell you if and where I get stuck

src/mvAppItem.cpp

src/mvPlotting.h

docs/source/documentation/themes.rst

src/embedded.cmake

src/mvBasicWidgets.cpp

v-ein · 2024-05-06T22:30:04Z

src/mvBasicWidgets.cpp

@@ -6398,17 +6431,17 @@ DearPyGui::draw_tooltip(ImDrawList* drawlist, mvAppItem& item)
 			}
 			apply_local_theming(&item);

-			ImGui::BeginTooltip();
+			if(ImGui::BeginTooltip()) {


While this condition might makes tooltip rendering more efficient in some cases (not in the current version of ImGui though 😁), it will also lead to item state "getting stuck" like it was on menu widgets in #2245. We need to update the state even when BeginTooltip returns false. Obviously state.visible will be false in this case; rectSize should probably be (0, 0); not sure about content region - probably (0, 0) too.

I applied this, tell me if it's correct in the next commit. Otherwise, if this can lead to others issues, I can simply remove that if statement

…ments - add `DEPRECATED_KEYWORD_ARG` to use in cases where you accept a deprecated argument but you suggest the user to move to the new one. - changed `invert` to `reverse_dir` argument in `color_map_scale` - changed some helper text - restored `cumlative` as deprecated argument - add old functions as deprecated: `add_hline_series` and `add_vline_series`

- `mvGroupBarSeries` to `mvBarGroupSeries` and change its parameters - `mvTag` to `mvAxisTag`, together with `add_axis_tag` instead of `add_plot_tag`. Also now it is a type 1 item. - change some parameters' names - reintroduce removed parameters as DEPRECATED and changed other parameters' names in `add_plot`, `add_axis_plot` and `add_label_series` - change `no_outliers` to `outliers` in Histograms - reintroduce deprecated `is_plot_queried` and `get_plot_query_area`

…eters - add style variables: `TabBorderSize`, `TabAngledHeadersAngle`, `TableAngleHeaderTextAlign` - fix `angled_header` parameter for TableColumn - effectively reactivate `frame_padding` in `ImageButton` - fix typo in `ImGuiStyleVar_TabBarBorderSize` - add some `span_` parameters to `tree_node` and added them to Demo (others still need to be tested) - update ProgressBar documentation to tell the user the possibility to enable indeterminate progress bar - update ImGui backend to 1.90.6

src/mvContext.h

src/mvGraphics_linux.cpp

src/mvItemRegistry.cpp

sandbox/CMakeLists.txt

src/dearpygui.h

src/mvContainers.h

src/mvDrawings.cpp

src/mvItemRegistry.cpp

v-ein · 2024-05-12T21:45:31Z

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 the corresponding modifier, mvKey_None doesn't actually work. ImPlot uses ImHasFlag to check if the modifier is pressed. The way ImHasFlag is implemented, ImHasFlag(keys, 0) will always return true, not false. To disable the modifier, one can pass -1 instead of mvKey_None, which is totally non-obvious. We probably need to document this somewhere.

It would be even better to modify the code so that mvKey_None leads to false in modifier tests, but that means making changes to ImPlot or even ImGui, which is a long way to go.

src/mvMetricsWindow.cpp

src/mvPlotting.cpp

src/mvPyUtils.cpp

src/mvStackWindow.h

src/mvTables.cpp

src/mvAppItem.cpp

src/dearpygui_commands.h

dearpygui/demo.py

src/dearpygui.cpp

docs/source/extra/video-tutorials.rst

src/dearpygui_commands.h

- fix typos and remove useless comments - restore old documentation - revert BOM changes - revert adding of `set_anti_aliasing` function in favour of adding new parameters to `configure_app` - change documentation of some parameters - remove useless variables like `unsaved_document` - fix "Mouse clicks count" so that now shows the number of counts and not the button creating them - implement `_query_dirty` to make the query rects behave correctly inside plots and fix callback for them - change `DEPRECATED_KEYWORD_ARG` parameter - hide redundant window in `StackWindow` - fix bug related to tooltip with angle headers - restore missing Docking style colors

src/mvAppItem.cpp

src/mvAppItem.h

dearpygui/demo.py

v-ein · 2024-05-19T19:54:55Z

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 for the new syntax with dpg.mvYAxis2 and dpg.mvYAxis3, I think we can somewhat reduce the pain for DPG users by auto-assigning multiple axes of type dpg.mvYAxis to Y1/Y2/Y3 depending on their order in the list. Here's a fix that does just that:

v-ein/DearPyGui-fixes@c62d78d...bugfix/auto-y-axes

In addition, the fix removes axesNames and axesFlags from mvPlotConfig since they actually got useless with the updated ImPlot.

Here's a script to test it all:

import dearpygui.dearpygui as dpg

dpg.create_context()
dpg.create_viewport(title=f"Test - {dpg.get_dearpygui_version()}", width=500, height=750)

with dpg.window(label="Old way"):
    with dpg.plot():
        dpg.add_plot_axis(dpg.mvXAxis)
        dpg.add_plot_axis(dpg.mvYAxis, label="Y1")
        dpg.add_plot_axis(dpg.mvYAxis)
        dpg.add_plot_axis(dpg.mvYAxis, label="Y3")

if hasattr(dpg, "mvYAxis2"):
    with dpg.window(label="New way", pos=(0, 350)):
        with dpg.plot():
            dpg.add_plot_axis(dpg.mvXAxis)
            dpg.add_plot_axis(dpg.mvYAxis, label="Y1")
            dpg.add_plot_axis(dpg.mvYAxis2)
            dpg.add_plot_axis(dpg.mvYAxis3, label="Y3")

dpg.setup_dearpygui()
dpg.show_viewport()
dpg.start_dearpygui()
dpg.destroy_context()

(The label on Y2 is omitted deliberately in order to test label assignment).

src/mvPlotting.cpp

v-ein · 2024-05-19T20:52:20Z

src/mvAppItem.cpp

@@ -4188,31 +4322,14 @@ DearPyGui::GetEntityParser(mvAppItemType type)
        args.push_back({ mvPyDataType::DoubleList, "y2", mvArgType::KEYWORD_ARG, "[]" });
        args.push_back({ mvPyDataType::DoubleList, "y3", mvArgType::KEYWORD_ARG, "[]" });
        args.push_back({ mvPyDataType::Bool, "tooltip", mvArgType::KEYWORD_ARG, "True", "Show tooltip when plot is hovered." });
+        args.push_back({ mvPyDataType::Bool, "no_fit", mvArgType::KEYWORD_ARG, "False", "the item won't be considered for plot fits" });
+        args.push_back({ mvPyDataType::Bool, "no_legend", mvArgType::KEYWORD_ARG, "False", "the item won't have a legend entry displayed" });


no_legend: Why do we need this argument on custom_series? Won't leaving the label empty be sufficient? AFAIK using empty labels to hide the legend entry works on all types of series in both old and updated DPG.

The ImPlot code treats both ImPlotItemFlags_NoLegend and an empty label identically:

if (!ImHasFlag(flags, ImPlotItemFlags_NoLegend) && ImGui::FindRenderedTextEnd(label_id, nullptr) != label_id)

src/mvAppItem.h

src/mvAppItem.cpp

SamuMazzi · 2024-05-20T13:19:42Z

While it might look natural to pass dpg.mvKey_None to disable the corresponding modifier, mvKey_None doesn't actually work. ImPlot uses ImHasFlag to check if the modifier is pressed. The way ImHasFlag is implemented, ImHasFlag(keys, 0) will always return true, not false. To disable the modifier, one can pass -1 instead of mvKey_None, which is totally non-obvious. We probably need to document this somewhere.

So you're telling to just put in the explanation of the parameters that you can disable that feature by just putting -1? (Ignoring the alternative of modifying implot itself) Otherwise tell me if I got it wrong

v-ein · 2024-05-20T17:02:16Z

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 setup.about since we already have a bit of text about modifiers there. Like this:

setup.about = "Adds a plot which is used to hold series, and can be drawn to with draw commands. For all _mod parameters use mvKey_ModX enums, or mvKey_ModDisabled to disable the modifier.";

src/mvGlobalHandlers.cpp

src/mvAppItem.cpp

src/mvPyUtils.cpp

src/mvContext.cpp

src/mvContext.h

…r fixes - Remove hideable arguments in `add_table` in demo - Improve documentation and change some parameters' names - Remove `disabled` parameter in `add_table_column` - Update state of tooltip when not shown - Change type of `decimalPoint` - Restore old `Mx` instead of `ImPlot::GetCurrentContext()->Style.LineWeight` - Remove useless performance improvement in `GetItem`

… widgets Also, improve internal handling of flags and names of axes together with slight changes to parameters default values

src/mvPlotting.cpp

.gitmodules

…raw_rectangle`

SamuMazzi and others added 30 commits February 7, 2024 09:46

feat (ImPlot): Add mvAxes and fix flags for plots

b5f7291

core: Better support for plot mods and added keys

c727a8f

fix: label axes plots and free error on exit

1a09f3d

fix: tool metrics not crashing anymore

d5128dd

fix (ImPlot): Avoid assert moving SetNextAxesToFit before BeginPlot

ed59f90

feat (ImPlot): add new plot and several flags

ccc4427

- added Infinite Line Series - udpated todo

core: Changed internal IO handling and bugfixes

ef317a7

- Removed keys data structure - Fix regression custom series - Fix drawing plots

feat (ImPlot): add plot flags

acd580f

fix: Fix bug on exit

e890a12

Also: - added parameters for stairs plot

fix: fix bug flags plots

f04917e

Also: - removed deprecated keys - fix typo in param of subplots function

feat (ImPlot): Implement set axis limits/zoom constraints

4922e75

fix: fix crash on exit when there's no viewport

653b898

feat (ImPlot): Add formatter and scales to axes

3b6350e

- Fix no_outliers typo - Clean .md files - Added flags for InputText

core: new feats in ImPlot and new demo

655d9aa

- Added GroupBarSeries - Reimplemented quering in plots - Cleaned internal mvPlotConfig - Fixed demo

core: Update

05d5417

- Removed 'area_series` in favor of `line_series` + `shaded` flag - Added remaining flags to plots - Refactor of `XSeriesConfig` structs - Added some mvKeys - Updated documentation mainly for DragTools and ChildWindow

feat (ImPlot): Enable mods for plots

42c5764

core: Add Presentation to MetricsTool and clean code

888ae9f

- Added ImageSeriesFlags - Update implot version

core: update plot section of dpg demo and update todo

0cb7e4b

feat (ImPlot): Add mvTag and labels to DragLine and DragPoint

0f844d5

core: add subplot and axes to demo's plot section

81fa0bd

core: add tools and custom to plot's demo

8140e05

core: fix 2d histrogram and bar plots

2642611

core: update demo and add new plot

f06beb5

- Fixed ColormapScale and added flags - Added DigitalSeries - Updated demo, also removing dependency to numpy

core: Update density demo

49bf4a2

core: add some widget to demo

1e54dd7

core: Update shaded plot demo and cleanup

172d767

core: fix Tag on axes and cleanup

f20556e

v-ein reviewed Apr 27, 2024

View reviewed changes

src/dearpygui_commands.h Outdated Show resolved Hide resolved

v-ein reviewed May 5, 2024

View reviewed changes

src/mvAppItem.cpp Outdated Show resolved Hide resolved

v-ein reviewed May 5, 2024

View reviewed changes

core: fix detecting of case-insensitive string compare

46cd05d

Now it's based on the detection of the OS and no more on the function `strnicmp` itself

v-ein reviewed May 6, 2024

View reviewed changes

SamuMazzi added 4 commits May 7, 2024 12:58

table: fix header label

ec643f4

v-ein reviewed May 11, 2024

View reviewed changes

v-ein reviewed May 12, 2024

View reviewed changes

v-ein reviewed May 13, 2024

View reviewed changes

src/dearpygui_commands.h Outdated Show resolved Hide resolved

v-ein reviewed May 19, 2024

View reviewed changes

v-ein reviewed May 20, 2024

View reviewed changes

wellcoming mentioned this pull request May 20, 2024

Unable to customize AxisScale #2333

Open

v-ein reviewed May 21, 2024

View reviewed changes

SamuMazzi added 2 commits May 21, 2024 17:28

plots: add mvKey_ModDisabled and show_label parameter for drag_…

5e94ed9

… widgets Also, improve internal handling of flags and names of axes together with slight changes to parameters default values

v-ein reviewed May 21, 2024

View reviewed changes

src/mvPlotting.cpp Outdated Show resolved Hide resolved

.gitmodules Show resolved Hide resolved

SamuMazzi added 3 commits May 22, 2024 12:45

plot: add ImPlot submodule

7af5307

plot: restore mvAreaSeries and query_toggle_mod

a0c1a43

core: fix mvMouseButton X1/X2 and deprecate color parameters for `d…

ec26852

…raw_rectangle`

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Updating backend ImGui/ImPlot/ImNodes to latest versions #2275

Updating backend ImGui/ImPlot/ImNodes to latest versions #2275

SamuMazzi commented Feb 7, 2024 •

edited

v-ein commented May 5, 2024

v-ein May 5, 2024

SamuMazzi May 6, 2024

v-ein May 6, 2024

SamuMazzi May 7, 2024

v-ein May 11, 2024

v-ein May 6, 2024

SamuMazzi May 7, 2024

v-ein May 6, 2024

SamuMazzi May 21, 2024

v-ein commented May 12, 2024

v-ein commented May 19, 2024

v-ein May 19, 2024

SamuMazzi commented May 20, 2024

v-ein commented May 20, 2024

Updating backend ImGui/ImPlot/ImNodes to latest versions #2275

Are you sure you want to change the base?

Updating backend ImGui/ImPlot/ImNodes to latest versions #2275

Conversation

SamuMazzi commented Feb 7, 2024 • edited

Description

Why?

Changes

OpenGL

Issues solved (afaik)

New Features

Breaking changes

Changes expected in the future from ImGui

Major concerns

Notes

v-ein commented May 5, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

v-ein commented May 12, 2024

v-ein commented May 19, 2024

Choose a reason for hiding this comment

SamuMazzi commented May 20, 2024

v-ein commented May 20, 2024

SamuMazzi commented Feb 7, 2024 •

edited