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

Skip temporary copying to framebuffer. #502

Closed
wants to merge 1 commit into from

Conversation

vespakoen
Copy link
Contributor

This is work done by @troughton (see: troughton@42f187a).

See his comment in this issue: #354
I just wanted to turn it into a PR on this repository so more people can see it, and possibly try it out / continue working on it.

I also fixed some deprecation warnings I got in XCode on Catalina.

I can compile and run this, it make SolveSpace very fast again!
However, there is some flashing in the toolbar occurring now and then, and there are probably other issues that I haven't stumbled into yet.

Notice that this PR does not bring in the changes that @troughton made to src/render/gl3shader.cpp since I am not sure what the purpose of these changes are.

Can someone tell me how to crash it / what needs to be done to get this working reliably?

@CLAassistant
Copy link

CLAassistant commented Nov 23, 2019

CLA assistant check
All committers have signed the CLA.

@whitequark
Copy link
Contributor

I also fixed some deprecation warnings I got in XCode on Catalina.

Please put these in a separate commit. Having a single commit with deprecation updates and behavior changes makes the history hard to understand.

However, there is some flashing in the toolbar occurring now and then, and there are probably other issues that I haven't stumbled into yet.

If you add a constraint, and double click on the text, can you edit it? Or does it disappear / become black eventually? What about scrollbars and tooltips? That's the reason it uses offscreen rendering right now.

@vespakoen
Copy link
Contributor Author

Allright, thanks for the info on what to test for, I'll do that in a bit. In the meantime I made a new PR that does not include the deprecation warnings over here: #504

So I am closing this one.

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

Successfully merging this pull request may close these issues.

None yet

4 participants