-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 to latest GLFW #6587
base: main
Are you sure you want to change the base?
Update to latest GLFW #6587
Conversation
Thanks for submitting this pull request! The maintainers of this repository would appreciate if you could update the CHANGELOG.md based on your changes. |
Looks good. We can merge after testing. Thanks! |
Possibly fixes #1673 |
Test draw example and O3DVisualizer. Also test legacy visualizer. |
Hi @errissa can you check the error in the documentation CI? Also, do all examples run for you? I got a crash in one draw.py example on Intel macOS. |
Works for me on intel Mac now. |
Everything works, except double clicking on a file in macOS does not open the file with Open3D. Need to check how macOS is passing the file name to glfw. |
Hi @errissa let's go ahead and merge this PR and the filament update PR as is. We'll open an issue for the "double clicking on file doesn't open in Open3D viewer" and fix it later. |
FIXME: Intel macOS: No window when opening app without a file (e.g. double click). |
Not sure if this was still was an open question, but this PR does indeed fix #1673 on an M3 Mac. |
@rxba thanks for testing this PR. We haven't merged this yet because of a macOS [only tested on Intel mac] issue in the Open3D viewer, where double clicking on the app, or launching from the command line doesn't bring up an empty window. Trying to open an asosciated file (double click or command line) gives an error instead of opening it. Can you test and see if you get this error on your Apple M3 machine? |
@errissa when you get a chance, can you take a look at this? Thanks! |
@ssheorey Can confirm this is also an issue on ARM Mac. I just tried |
You can make Open3D the default viewer for 3D file types (gltf, obj, ply, etc.), so that double clicking on the file opens it in Open3D. With this PR, you instead get an error message box saying cannot open file of type GLTF, etc. |
I see, can confirm the same behaviour on ARM, e.g. opening a .ply on this build errors with |
Sorry to be off-topic for this thread, but as described in #7000 I have been unable to run a new app written in c++ using |
Type
Motivation and Context
Updates Open3D to use the latest GLFW as the version we had been using is several years old and predates Mac API changes. Also, updated to build system to build GLFW as external project to make it consistent with the rest of Open3D's use of third party libraries.
Checklist:
python util/check_style.py --apply
to apply Open3D code styleto my code.
updated accordingly.
results (e.g. screenshots or numbers) here.
Description