-
Notifications
You must be signed in to change notification settings - Fork 49
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
'loader' and 'sceneinventory' don't use the current project when using AVALON_DEBUG
#460
Comments
Good question. I think the reason was to ease starting these tools in a quick test environment, but I agree that the behavior sounds confusing. I believe originally that code was written by @mottosso looking at the BLAME reports on Github. Does Admittedly the |
After digging around a bit, it seems that It would be nice to have a 'proper' debugging mode and probably also have a 'demo' mode. But that seems like quite a bit of work to get right and in my opinion doesn't have a very high priority. I personally feel it would already be a good start to get rid of the 'confusing' behaviour in the |
Hi @mottosso, do you have time to have a quick glance and give your opinion? |
I'm equally stumped. :S Can't remember implementing this kind of behavior, would be happy to see it removed. Thanks for checking. |
While working on the Blender integration I ran into something I thought was an issue with my code. When you have set
AVALON_DEBUG=1
theloader
andsceneinventory
use the first project from the database instead of the 'active' one.See the relevant lines for the loader and the sceneinventory.
To be honest I found this quite confusing. Is there a specific reason for this? Would it be okay to remove this?
The text was updated successfully, but these errors were encountered: