In-Game: Add a "step size" argument to dbg_slider() and dbg_slider_int() so users can control the value #2971
Comments
|
Yeah, I'm rather using integers with step = 1 (if not bigger numbers) for things that benefits from slider, so current way it works (allows to set decimal numbers, with accuracy proportional to dbg view size), isn't what I would expect. |
|
If this isn't entirely possible, I suppose at least having SliderInt and SliderAngle could be helpful? https://pthom.github.io/imgui_manual_online/manual/imgui_manual.html |
|
While Imgui does not support it explicitly this has an example that could be used - ocornut/imgui#1183 - need to test it out and see what it is like |
|
Can this also be done to the Drag control? |
what do you mean Drag control? |
|
Fixed in 2024.6 - I have added a new (optional) parameter to both |
gurpreetsinghmatharoo
added
the
documentation
…ntrol YoYoGames/GameMaker-Bugs#2971 * Added optional step parameter to dbg_slider & dbg_slider_int * Added second example to dbg_slider that shows how to use the step size parameter * Added a note on what the step size actually means (i.e. possible values are limited to multiples of the step size) * Updated shortcut style on the pages
|
Documented the step size as an optional parameter on both the |
* develop.bart: docs(feature): added documentation for physics_raycast YoYoGames/GameMaker-Bugs#2762 docs(feature): documented gamepad_enumerate YoYoGames/GameMaker-Bugs#5329 docs(feature): skeleton_animation_clear optional parameters YoYoGames/GameMaker-Bugs#1570 docs(feature): documented dbg_view_exists and dbg_section_exists YoYoGames/GameMaker-Bugs#4931 docs(feature): documented dbg_view_exists and dbg_section_exists YoYoGames/GameMaker-Bugs#4931 docs(feature): YoYoGames/GameMaker-Bugs#1570 docs(general): mentioned that any attached files are uploaded privately docs(feature): smaller custom format screenshot YoYoGames/GameMaker-Bugs#5495 docs(feature): documented the new dbg_text_separator function YoYoGames/GameMaker-Bugs#4998 docs(feature): Switch to the docking branch of imgui YoYoGames/GameMaker-Bugs#4905 docs(general): document OS and audio device limitations when using audio YoYoGames/GameMaker-Bugs#5580 docs(feature): Add an option to specify "step" in the ImGUI slider control YoYoGames/GameMaker-Bugs#2971 # Conflicts: # Manual/contents/GameMaker_Language/GML_Reference/Asset_Management/Audio/audio_sound_length.htm # Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_slider.htm # Manual/contents/GameMaker_Language/GML_Reference/Debugging/dbg_slider_int.htm
YYDan
changed the title
|
tested in IDE v2024.600.0.557 Runtime v2024.600.0.572 and IDE v9.9.1.677 Runtime v9.9.1.818 @gurpreetsinghmatharoo, @YYBartT dbg_slider and dbg_slider_int work as expected but the step example in the beta manual, here and here, are missing a label value so send up displaying the expected step value |
…der_int() YoYoGames/GameMaker-Bugs#2971 * Added missing label on the dbg_slider page example * Fixed ref_create on the dbg_slider_int page example
|
@mgeddesGM That should be changed now in the |
|
verified on latest beta manual |
Is your feature request related to a problem?
Currently, there's no way to specify how precise the slider should be;
dbg_slideronly allows specifying minimum and maximum values, not the step between them. It means we can't easily make a slider that e.g. operates on integers only.Describe the solution you'd like
Allow specifying the
dbg_sliderstep. One option could be adding a step-specific argument after label, though it breaks the convention of label argument always being last.Another possibility would be passing additional configuration as struct, so that any additional configurations would only require expanding the struct, while keeping the function signature the same. Though it still is tricky with minimum and maximum arguments already being there.
Describe alternatives you've considered
No response
Additional context
Original suggestion appeared here: https://forum.gamemaker.io/index.php?threads/dbg_slider-missing-step-size-argument.105748/#post-637205
The text was updated successfully, but these errors were encountered: