Better handling of copy pasting of scene strips #118336

New Issue

Sebastian Parborg · 2024-02-15T16:58:20+01:00

Sebastian Parborg commented

2024-02-15 16:58:20 +01:00

After the copy paste rewrite in e7f0bb24f7, you can no longer paste scene strips without having the scene it refers to being scrubbed.

This means that the end user will have to manually link in and/or select the correct scene to use after pasting.

This was done because:

We can not know with high certainty if the scene name used in the strip refers to the same scene between .blend files. For example if a user copy pastes a scene strip using scene Scene.001. We can not be certain that if Scene.001 already exists in the file they paste the strip in is the same scene.
We could of course simply link in the scene data. But it could potentially get really confusing for end users if some strip data is copied with others are linked in. Especially since this means that the file they paste the strips into will depend on other .blend files on their file system.
If we instead go the other route of always copying all scene data, it could make files get bloated very quickly as then all scene data like textures and meshes etc would get copied. Even when pasting into the same file.

Some of this could of course be side stepped by somehow teaching users to use ctrl+d when copying scene strips inside the same file. But this needs a clear design for how the data copying should work and how it should be presented to the end user.

Therefore we need a good proposal for how to handle (or if we should not handle) these cases in a manner that is usable and non confusing for the end users.

After the copy paste rewrite in e7f0bb24f7, you can no longer paste scene strips without having the scene it refers to being scrubbed. This means that the end user will have to manually link in and/or select the correct scene to use after pasting. This was done because: - We can not know with high certainty if the scene name used in the strip refers to the same scene between .blend files. For example if a user copy pastes a scene strip using scene `Scene.001`. We can not be certain that if `Scene.001` already exists in the file they paste the strip in is the same scene. - We could of course simply link in the scene data. But it could potentially get really confusing for end users if some strip data is copied with others are linked in. Especially since this means that the file they paste the strips into will depend on other .blend files on their file system. - If we instead go the other route of always copying all scene data, it could make files get bloated very quickly as then all scene data like textures and meshes etc would get copied. Even when pasting into the same file. Some of this could of course be side stepped by somehow teaching users to use ctrl+d when copying scene strips inside the same file. But this needs a clear design for how the data copying should work and how it should be presented to the end user. Therefore we need a good proposal for how to handle (or if we should not handle) these cases in a manner that is usable and non confusing for the end users.

Sebastian Parborg added the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Better handling of copy pasting of scene strips #118336