That’s also not going to work out because a lane is always tied to a pool. You can see that for yourself if you check the model explorer whilst in your diagram: the pools are visible as separate models but the lanes will always be related to a specific pool. So if you drag the lane into your diagram you’ll also be adding the pool it’s a part of.
Well, one way to do that is to simply turn of all the indicators
A little more serious though: although there’s nothing wrong with that approach it does make me wonder why you’d want to focus on that? Because although the use of different views definitely has its advantages there will also be times when their use isn’t very useful.
Still, there is an easy trick to accomplish this: create all the model elements outside your diagrams, so using the model explorer for example:
This would create the master in your model repository so to speak, not associated with any specific diagram. As a direct result you can now drag it into any diagram of your choosing and that will always create a new auxiliary view.
I suppose an advantage here is that you’d never risk of accidentally deleting your model elements because every time you delete something from your diagram it’ll only be a view and nothing more.
But on the other hand I also can’t help wonder if this doesn’t over complicate things. But that’s a question I cannot answer This is actually what I personally consider to be one of VP’s key strengths: 2 individual users can easily have 2 totally different workflows. The key here is to always use what works best for you.
I hope this can help!