Re: [Rosegarden-devel] Three similar crash cases

[Chris C. <ca...@al...>]

On Sun, Jan 11, 2009 at 11:49 AM, Chris Fryer <chr...@go...> wrote:
> I thought the replacement of QScrollView with QScrollArea was brave.
> From an initial look, QScrollArea operates directly on a widget as opposed
> to QScrollView operating on a viewport.

I'm not completely sure that I have ever in my life written code to
use either of these classes (I didn't write the scroll view
implementations in RG, and I'm struggling to think of any other use of
them elsewhere either), but I thought the difference was that
QScrollView contains its own viewport widget and QScrollArea needs a
separate widget.  i.e. it's not so much that QScrollArea _can_ operate
on a widget, as that it won't do anything without one.

For CompositionView this means we would need a separate widget to put
in the QScrollArea.  But we don't actually want to do that, because
CompositionView doesn't want the size limits that would affect a giant
widget.  We either need to make a single widget with two separate
scrollbars, or just continue to use Q3ScrollView (or even port the
basics of QScrollView into our own code files).

I think.


Chris