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

Shouldn't out arguments be returned values? #11

Closed
neclepsio opened this issue Sep 21, 2022 · 4 comments · Fixed by #65
Closed

Shouldn't out arguments be returned values? #11

neclepsio opened this issue Sep 21, 2022 · 4 comments · Fixed by #65
Labels
enhancement New feature or request

Comments

@neclepsio
Copy link
Contributor

For example:

func GetDrawCursorPos(pOut *ImVec2)

should be:

func GetDrawCursorPos() ImVec2
@AllenDang
Copy link
Owner

It's auto generated code, process arguments is a lot easier than recognize out value.

@sonoro1234
Copy link

sonoro1234 commented Oct 9, 2022

this function have nonUDT=1 in definitions.json to let recognize it should be a return value

@AllenDang
Copy link
Owner

@sonoro1234 You could have a try and raise a PR

@sonoro1234
Copy link

sonoro1234 commented Oct 10, 2022

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

Successfully merging a pull request may close this issue.

4 participants