Home » U++ Library support » U++ Widgets - General questions or Mixed problems » ScrollView - a question - maybe proposal..
Re: ScrollView - a question - maybe proposal.. [message #51095 is a reply to message #51014] |
Tue, 22 January 2019 18:22 |
luoganda
Messages: 197 Registered: November 2016
|
Experienced Member |
|
|
i didn't take measure for:
readrawing whole area vs just scrolling and drawing the rest, which is ideal for plotting software, but:
- simple optimized BitBlt for scrolling will be probably always faster that drawing fragmented old 's' patterned pixels along y axis
- BitBlt is probably 2D hardware optimized func - even on most hardware, i don't know if this is true, but probably, i am not sure for SetPixel - although i don't know the workings itself in upp, how this is done. So this "point" may not apply here for optimizations.
- SetPixel must do any math used in BitBlt, which BitBlt can probably do only once or at least less times - for example clipping
- program becomes more complex for apps such as plotting, because it needs to allocate(more memory is eaten) and manage old pixels too, in this case storing and redrawing old pixels + new
Up is for windows BitBlt, but the same probably aplies for linux functions.
It would be handy that this is somehow available, if not in Ctrl itself, at least in Bazaar.
I agree that this could write someone else, not just core upp programmers..
|
|
|
Goto Forum:
Current Time: Sat May 04 04:30:08 CEST 2024
Total time taken to generate the page: 0.02478 seconds
|