Review Request 125719: make pre-specified view size precede initial object size in QuickViewSharedEngine

Takahiro Hashimoto kenya888 at gmail.com
Tue Oct 20 15:46:17 UTC 2015


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/125719/
-----------------------------------------------------------

Review request for Plasma.


Summary (updated)
-----------------

make pre-specified view size precede initial object size in QuickViewSharedEngine


Repository: kdeclarative


Description (updated)
-------

Now QuickViewSharedEnginePrivate size is initialized with its rootObject size in QuickViewSharedEnginePrivate::executionFinished(). 

In the case of setting its size before completing QuickViewSharedEnginePrivate::executionFinished(), it is forcely overwrote with rootObject size unexpectedly.

This problem happens when running ksplashqml on higher or lower resolution screen than breeze background image size(1920x1080) (see attached screenshot)

I think it would be  better that the view size which is specified by manual precede default size initialization process.  Adjusting view and object size can be done by syncResizeMode() in QuickViewSharedEnginePrivate::executionFinished().

This patch make the view size adjust to its rootObject size when view size isEmpty().

AFAIK, QuickViewSharedEngine is now used by screenlocker greeter and ksplashqml. I cannot imagine this change affect another use cases. Please let me have any advice:)


Diffs (updated)
-----

  src/quickaddons/quickviewsharedengine.cpp b57d7dc 

Diff: https://git.reviewboard.kde.org/r/125719/diff/


Testing (updated)
-------

apply this patch and confirmed ksplashqml content was adjusted to screen size correctly.
screenlocker remain working fine to me.


Thanks,

Takahiro Hashimoto

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20151020/6b9a794b/attachment-0001.html>


More information about the Plasma-devel mailing list