Scene vs. multiple views

[lni]

By "closest" I understand it's not exactly what you wanted. What functionality are you missing exactly?

OK, I am getting to it now... current code is this:

void QfwSummaryView::drawItems( QPainter * painter,
                                int numItems,
                                QGraphicsItem* items[],
                                const QStyleOptionGraphicsItem options[] )
{
  for ( int idx = 0; idx < numItems; idx++ ) {
    QfwSummarizableItem* item = dynamic_cast<QfwSummarizableItem*>( items[ idx ] );
    if ( item ) {
      painter->save();
      item->drawSummary( painter );
      painter->restore();
    }
  }
}

void QfwSummaryView::drawItems( QPainter * painter,
                                int numItems,
                                QGraphicsItem* items[],
                                const QStyleOptionGraphicsItem options[] )
{
  for ( int idx = 0; idx < numItems; idx++ ) {
    QfwSummarizableItem* item = dynamic_cast<QfwSummarizableItem*>( items[ idx ] );
    if ( item ) {
      painter->save();
      item->drawSummary( painter );
      painter->restore();
    }
  }
}

To copy to clipboard, switch view to plain text mode 

See the attached screen dump, I have 2 tracks with multiple curves, each curve shares the same Y axis, but they have their own X axis. The Y axis is long that require scroll bar, so the idea is to have 2 views: the bottom view is to draw those curves, the top view is to draw "legend" along with X axis min value and max value....

I am currently using the same QGraphicsScene, there is a boundingRect problem, for instance the area plot (in the right track) has narrow width, but the "legend" at the top is wider, yet exposure is controlled by the real object's boundingRect...

So, I think I need to have two scenes, can someone gives me a simple UML class diagram, as well as how to keep then in sync?

[wysota]

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

[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...