[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
|
[news.eclipse.tools.gef] Re: FigureCanvas vs. ScrollPane: a question
|
Randy,
Thanks for the info...I always get lightweight and heavyweight mixed up :(
Are you also saying that by using ScrollPane one would not be taking
advantage of optimized scrolling via bitblitting? I'm thinking yes...
Thanks,
Mark
"Randy Hudson" <none@xxxxxxxxxx> wrote in message
news:d1cunv$r0a$1@xxxxxxxxxxxxxxxxxx
> Actually, FigureCanvas is heavyweight (an OS window), and ScrollPane is
> lightweight (emulated).
> Make your choice based on:
>
> Use FigureCanvas if:
> -you want the native appearance of the OS scrollbars
> -you want optimized scrolling (using native bitblitting)
>
> Use ScrollPane if:
> - You need to nest the viewport inside a larger diagram
> - You want to customize the scrollbar itself
>
> "Mark Powell" <Mark.Powell@xxxxxxxxxxxx> wrote in message
> news:d19ubp$jm2$1@xxxxxxxxxxxxxxxxxx
>>
>> So, in the Draw2D API there are these two classes that can contain
>> Figures and provide scrolling: FigureCanvas, and ScrollPane.
>> FigureCanvas is lightweight (the O/S provides the scrollbars), and
>> ScrollPane is heavyweight (Draw2D paints the scrollbars).
>>
>> Is the choice of which of these widgets to use purely aesthetic?
>>
>> Are there any features other than how the scrollbars are rendered that
>> you get with using one versus using the other?
>>
>> For instance, are each of these classes taking equal advantage of
>> clipping to the viewable area during repaints via DeferredUpdateManager,
>> or is one of these classes "smarter" about clipping than the other?
>>
>> Thanks,
>> Mark
>>
>>
>
>