project: Make sure our subclass ends up in the asset cache
Currently we just create our subclass of GES.Project
without calling GES.Asset.request()
at any point in time, meaning that there could be several instances of Project with a same ID in the process which should never happen for assets. This could create issue with nested projects in the future.
We should probably add a __new__
implementation for class Project
that returns GES.Asset.request(Project, the_project_id)
or something like that I would think.
We need first a unittest which checks that two successively created Project
objects have different .props.id
.
Edited by Alexandru Băluț