Skip to content
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

Update Raygui to version 4.0 #38

Open
leotada opened this issue Sep 20, 2023 · 4 comments
Open

Update Raygui to version 4.0 #38

leotada opened this issue Sep 20, 2023 · 4 comments

Comments

@leotada
Copy link
Contributor

leotada commented Sep 20, 2023

https://github.com/raysan5/raygui/releases/tag/4.0

@schveiguy
Copy link
Owner

Thanks for reminding me. I will take a look!

@LiamM32
Copy link
Contributor

LiamM32 commented Mar 29, 2024

If I did this, how would I go about it?

It looks like the current raygui.d was made by copying raygui.h, and then making edits until it's valid in D.

It looks like the file in this repository doesn't have the old raygui.h as part of it's git history. But should I somehow take advantage of git's features to add all of the new lines from the newer raygui.h into the current one, while excluding the lines that were never placed in the D version? Or should I just compare them by eye and try making the changes to raygui.d to mimic the functions in Ragyui 4.0?

@schveiguy
Copy link
Owner

What I did was use ctod and then just fixed what didn't compile. I don't think there's an "upgrade" path, you just have to do it again.

@LiamM32
Copy link
Contributor

LiamM32 commented Apr 9, 2024

What I did was use ctod and then just fixed what didn't compile. I don't think there's an "upgrade" path, you just have to do it again.

I'm trying to do an upgrade process where I placed raygui.h in a new git repository, and then made changes to it in multiple branches to reach both you're version of raygui.d, and one generated using CtoD from Raygui 4.0

What's strange is I tried using CtoD on both version 3.5 and version 4.0 of raygui.h, and the results are very different. On 3.5 it knew what if was doing. On 4.0 it's left way too many things unchanged from the C version.

Perhaps there was some newly-added symbol early in the file that made it trip.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants