> Why can't we just have the screenshot being obtained by an image provider? Why
> would Application save its screenshot internally at all? It was useful before
> QtComp, as it was a cacheing system that made sense at the time, but now I
> don't see the benefit at all.
I don't get your comment. That what is happening already. The image provider is just an API between C++ and QML so that QML can use an URL to refer to an QImage held in the C++ side.
> Why can't we just have the screenshot being obtained by an image provider? Why
> would Application save its screenshot internally at all? It was useful before
> QtComp, as it was a cacheing system that made sense at the time, but now I
> don't see the benefit at all.
I don't get your comment. That what is happening already. The image provider is just an API between C++ and QML so that QML can use an URL to refer to an QImage held in the C++ side.