-
Notifications
You must be signed in to change notification settings - Fork 47
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
Remove ImGui dependency on ApplicationServices once 1.72b is widely used enough #48
Comments
Hi, sorry about this. The integration code was not yet upgraded to work with latest ImGui versions and this seems to be caused by new macOS clipboard support in 1.71 (ocornut/imgui#2546). Until I fix this and link the missing framework, can you build with an older version of ImGui? The code was tested extensively with 1.69, 1.70 could work too. |
Thanks a lot, 1.69 works just fine. |
If there is a need to use the latest version of imgui you can add the Carbon library to your CMakeLists and that should fix the error:
EDIT: |
Should be fixed with b157344 -- to make it work, please update the |
Note as as-per ocornut/imgui@29d9394 and ocornut/imgui#2546 (comment) I have reverted this change. It is possible to explicitely enabled the default cocoa handler by using |
....That wasn't explicit in the message above, but it means you may revert linking to ApplicationServices... Magnum probably has its own clipboard handler anyway. |
@ocornut thanks a lot for taking the time to comment! 💚 I'll keep it around for now so people using 1.71 don't run into the same issue again, will remove it a few releases later. |
I decided to just link to ApplicationServices always, as it's no additonal hurdle on our side and it's nicer to users. Internal TODO removed in 4e99409. |
I am trying to build the magnum integration with imgui on mac, but the build always fails with the following error:
which are windows specific functions, I tried building it on windows the same way I did on mac and it worked. So I believe it is a mac specific issue.
Anyway to overcome this issue?
The text was updated successfully, but these errors were encountered: