Scene vs. multiple views

[lni]

I think this is a candidate case for two scenes. As for synchronization, simply connect signals and slots from the scrollbars together.

Scrollbar synchronization is not a problem. But the item's synchronization may be complicated.

The pen may be changed (assuming I have a pen editor), the brush may be changed, or the width of the track may be changed.

At the end, I need to print them in the same paper without QSplitter...

[wysota]

The pen may be changed (assuming I have a pen editor), the brush may be changed, or the width of the track may be changed.

It's not changed by some "outside force", when you apply the change to items in one scene, you can apply them to items on the other scene as well. You can even store pointers to items from scene A in corresponding items in scene B (and vice versa) to be able to quickly map between them.

At the end, I need to print them in the same paper without QSplitter...

I don't think that's a problem. After all you are rendering scenes, not widgets.

[lni]

It's not changed by some "outside force", when you apply the change to items in one scene, you can apply them to items on the other scene as well. You can even store pointers to items from scene A in corresponding items in scene B (and vice versa) to be able to quickly map between them.

Ya, somewhere I need to keep link of two items in different scene. But I need a good design with UML class diagram

[wysota]

It seems I have managed to answer my own question from 13 years later

[d_stranz]

You're getting old if you can't remember the details of a conversation you had only 13 years ago...