Skip to content

Conversation

@rcoreilly
Copy link
Member

No description provided.

@rcoreilly rcoreilly marked this pull request as draft September 10, 2025 01:20
…) here -- it is not necc in general and can be very expensive, and it breaks xyz now that it is not calling update every render, which was not good. xyz now has a much more sensible update / render integration with core logic. names are still confusing for the xyz vs core versions.
… it is just an imperative Render() call now that does all the updating -- minor additional computation of world matricies is NOT worth all the extra overhead of managing all these things, and is often needed and assumed anyway. so much cleaner.
…image; xyz RenderGrabImage() method gets image back from render.
…ng issues with grab image when holding down the button.
… in an async timer sending click events directly to the button, so it absolutely needs AsyncLock!
…work for updating view nodes from physics nodes. function based and much simpler, more flexible, robust. still need to update example to use makers.
…g wall. world Init function has to be more dynamic so it can be set in NewView..
@rcoreilly rcoreilly marked this pull request as ready for review September 14, 2025 21:32
…s an arg, which is simpler for imperative and works fine for plan-based init functions in a wrapper. moved the README to the docs and moved XZY into Architecture instead of Widget.
….Scene, which makes it easier to have a default off-screen rendering physics thing that can later optionally be incorporated into a GUI.
…stroy any existing GPU stuff when doing "NewForScene" functions.
…doesn't affect main xyzcore display. This is used in physics render from node.
…device if Frame/Phong not set; fully robust. Also SetAspect convenience.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant