There's this Gitea option, where I think we'd only be enable sources and templates.
REPO_INDEXER_REPO_TYPES = sources,forks,mirrors,templates
But maybe we don't need to enable…
Code search is not enabled anywhere. It explicitly mentioned blender/, but the more general thing is that we don't want to be indexing forks, as Gitea treats every one separately. There is a…
Yes it works, but imho this extra clicking defeats the whole purpose of drag'n'drop... If I need to click through two different pop-ups every time I drag an image, I'm likely just as well using…
Gitea 1.22 add support for code search without an index. I'm not sure how fast it is on a big repository, may be worth testing at some point.
I guess we can make the build system support providing a PYTHON_PATH. To implement that in the cleanest way possible I guess it would be best to replace the platform specific bat and bash files…
I'm not sure if and how more advanced library datablock editing should work. I think we can seriously consider just not supporting it all, and keep the restriction of a single asset per blend…
@guishe has been doing a lot of work on these kinds of drop handlers as well, maybe he has an idea for how best to integrate this.
I forgot the C++20 issue. @salipour we could also use help to make HIPRT build with C++17. That's the version used by the VFX reference platform (https://vfxplatform.com/) that Blender and other…
I made further changes to properly handle Orochi, disable encryption, some fixes for Windows (but still untested), fix library detection on Linux.
Next steps would be:
- I would like to get…
Move this code to render_result_free? So we can't accidentally miss it.
Maybe it's nicer to add a RE_ReferenceRenderResult to keep all the reference counting in the render module.
I think it's just people who don't read the instructions. But I don't care much about the wording either way. If the triaging team is happy with the changes go ahead.