On 20/04/2016 16:29, Andrea Bernabei wrote:
> because topMargin should be available for the dev to use it for whatever
> he needs it to. The developer should not have to mind about setting it
> to accomodate a behaviour that is handled by PageHeader.
>
> So, on one side, you have to make space for the header, on the other
> side, you should (must, I'd say) still let the developer decide a custom
> topMargin to implement whatever usecase he needs it for
But the documentation clearly states (and it has always been like this):
"The topMargin of the flickable will automatically be updated to always
match the height of the header."
On 20/04/2016 16:29, Andrea Bernabei wrote:
> because topMargin should be available for the dev to use it for whatever
> he needs it to. The developer should not have to mind about setting it
> to accomodate a behaviour that is handled by PageHeader.
>
> So, on one side, you have to make space for the header, on the other
> side, you should (must, I'd say) still let the developer decide a custom
> topMargin to implement whatever usecase he needs it for
But the documentation clearly states (and it has always been like this):
"The topMargin of the flickable will automatically be updated to always
match the height of the header."