-
-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add floating point value box to raygui #356
Conversation
@benjibst this is a breaking change for raygui because it requires a new function from raylib, not merging it for now but I keep the PR open while thinking what should be done with it... |
@raysan5 ah ok, got it, maybe one solution could be to just use the c standard library? |
Yeap, probably that's the best solution at this point. |
@benjibst What is the state of this PR? Is it possible to move |
@raysan5 last time i tried to implement this with a static text buffer, but the problem is that when you edit the value of one textbox, and then switch to the other textbox, the float value in the text buffer is shared so the value of the second textbox gets overwritten |
@benjibst I see the issue now. It happens when switching from one text box to another directly without exiting the first one "properly" so it's like two text boxes are active for one frame... mmmh... thinking if it can be addressed in some way... |
@benjibst I'm merging this PR and I'll try to find some solution in the meantime... Thanks again for all the work you put on this improvement! :) |
ah, do you mean like: if you exit from one valuebox properly, it can parse the string and then clear the buffer? so that the next valuebox knows its allowed to overwrite the static buffer with its own float?
…________________________________
From: Ray ***@***.***>
Sent: Tuesday, May 7, 2024 12:05:33 PM
To: raysan5/raygui ***@***.***>
Cc: Benjamin Schmid Ties ***@***.***>; Mention ***@***.***>
Subject: Re: [raysan5/raygui] Add floating point value box to raygui (PR #356)
@benjibst<https://github.com/benjibst> I see the issue now. It happens when switching from one text box to another directly without exiting the first one "properly" so it's like two text boxes are active for one frame... mmmh... thinking if it can be addressed in some way...
—
Reply to this email directly, view it on GitHub<#356 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASELDNQD7FYQZKJKNDPLTO3ZBCRO3AVCNFSM6AAAAABAPWXI76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJXHEZDSNJWGI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@benjibst Yes, that's my idea but I'm not sure if it would work... As per my understanding, at the moment it fails because when you "jump" from one GuiValueBox to another, the state logic for editMode keeps executing without an exit logic... but I could be wrong... it needs to be tested... |
No description provided.