You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using ImGui::SliderScalar with a combination of scientific notation (e.g., "%.1e") plus ImGuiSliderFlags_Logarithmic plus small values, the dragging behavior is incorrect. It jumps between the values min, 1e+1 and max, which can be seen from the verifiable example.
This is probably highly related to #4341, but there the problem was simply described as losing "numbers from range (min, 10>". When the maximum is small, too, it seems like the problem is even greater, as not only a small amount of values is lost, but the slider will also assume values outside the min-max range.
I can also confirm, like #4341, that logarithmic_zero_epsilon is likely also the culprit here, too. It is set to 10, as ImParseFormatPrecision returns -1 for the scientific notation.
Version/Branch of Dear ImGui:
Branch: master (at latest commit)
Back-ends:
any
Compiler, OS:
Ubuntu 22.04 + GCC
Full config/build information:
No response
Details:
When using ImGui::SliderScalar with a combination of scientific notation (e.g., "%.1e") plus ImGuiSliderFlags_Logarithmic plus small values, the dragging behavior is incorrect. It jumps between the values min, 1e+1 and max, which can be seen from the verifiable example.
This is probably highly related to #4341, but there the problem was simply described as losing "numbers from range (min, 10>". When the maximum is small, too, it seems like the problem is even greater, as not only a small amount of values is lost, but the slider will also assume values outside the min-max range.
I can also confirm, like #4341, that logarithmic_zero_epsilon is likely also the culprit here, too. It is set to 10, as ImParseFormatPrecision returns -1 for the scientific notation.
Screenshots/Video:
No response
Minimal, Complete and Verifiable Example code:
The text was updated successfully, but these errors were encountered: