-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fixed warnings + added a new macro #1
Conversation
Thank you for your contribution. I will review it, but at a first bird eye there are a couple of things that are not subject to change here in the upstream version:
Other notes:
Once again, thank you for contributing back your ideas. |
The |
I see. If someone is using the latest C++ standard in Visual Studio, this code generates a warning. Maybe it would be better to suppress it via some pragma then to keep it C++14 compatible. |
Hi @BullyWiiPlaza , thank you for your contribution. I have fixed the issue with a different trick. Now it is effectively doing the same thing as |
|
You can go ahead and commit all changes you like by yourself, that's fine. |
Summary: Accepted and Included changes:
Not included:
|
Hello,
thanks for your useful header.
I fixed compile warnings, including:
constexpr can be used
hides previous local declaration
due to_ui_scope_guard
being multiply defined in the same scope when using more than 1 of your macrosI also added a new macro
with_Frame
which might be useful to start a new ImGui frame. It supports injecting a platform specific rendering setup with thebegin_frame
function.I just wanted to contribute something back in case you care, if not, that's fine, too.