-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Editor atlas support #71
Conversation
…ve into editor-atlas-support
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we could perhaps do a better job of caching in the editor code, but we could address that later. Looks good to merge.
(let [pass (:pass render-args) | ||
render-groups (collect-render-groups renderables)] | ||
(doseq [group render-groups] | ||
(plugin-update-file (:handle group) 0.0 (:texture-set-pb group))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems very expensive to do on every render call. Shouldn't we try to cache it as an output on the RiveModelNode
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, sounds good 👍
defold-rive/pluginsrc/rive_file.cpp
Outdated
case DRAW_MODE_CLIP_INCR: | ||
dmLogInfo(" DRAW_MODE_CLIP_INCR"); | ||
break; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really want to have this log spam in the render function?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eeeh oops, no!
Requires Defold 1.4.5+