Age | Commit message (Collapse) | Author |
|
In the tiled rendering case it does not need to check
if the window size is (0,0). But it still has to trigger
LOKit LOK_CALLBACK_INVALIDATE_TILES
Change-Id: I4c458edfd6e44599b8c8148e0f8543fb0563e627
|
|
Mac / Win cairo is not built / used, this cairo code can be removed to
reduce code bloat.
4th Revised version with Android fixes
Change-Id: I6e56850f535ca13b77839b7d67e227c5f39d388e
Reviewed-on: https://gerrit.libreoffice.org/16218
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
|
|
Change-Id: Ia5c8c0f38a347f398d587970a22e03f29ffd37af
|
|
Change-Id: I244a9eb6bce6b1c649653ec38ebb9a39f8b4c145
Reviewed-on: https://gerrit.libreoffice.org/16212
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
Tested-by: Noel Grandin <noelgrandin@gmail.com>
|
|
and replacing them with a call to XToolkitExperimental::
processEventsToIdle
Change-Id: I9fd6cb8af43d902587186310aebe78b5a5ee6932
Reviewed-on: https://gerrit.libreoffice.org/16201
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
Tested-by: Noel Grandin <noelgrandin@gmail.com>
|
|
Change-Id: I99a935ac7c1aee881bca77f95bd5d1a45d8901ea
|
|
This clobbers the functionality from commit:
06d731428ef6cf93c7333e8228bfb6088853b52f
make idle timers actually activate only when idle
Since now all rendering and re-sizing is done in idle handlers it
does effectively the opposite of what was intended. A better solution
would allow special-casing the processing of just rendering,
re-sizing and window management to spin for eg. progress bar
rendering.
Also add helpful debugging labels to the idle & timeouts.
Also cleanup the Idle vs. Scheduler handling.
Also ensure that starting an Idle triggers a mainloop wakeup.
Also add a unit test.
Change-Id: Ifb0756714378fdb790be599b93c7a3ac1f9209e6
|
|
Change-Id: I97d74eebcb45f413dbc73ab96db447228eeb158f
|
|
Change-Id: Ic25e9aca7a2a61ac677720427fae7a18a8a179fa
|
|
Let's hope passing an empty NSDictionary works fine.
Change-Id: I90a9b09d421ae8cd202b602db97b2c08b149fd07
|
|
Seing the fix, it probably also impacts scrolled floating menus.
Change-Id: Ia740573c3ed54cf01a57575a2ca00d49165be28d
Reviewed-on: https://gerrit.libreoffice.org/16187
Reviewed-by: Philippe Jung <phil.jung@free.fr>
Tested-by: Philippe Jung <phil.jung@free.fr>
|
|
Change-Id: I17607b0040f8adc2f0cbbe98a1d3a9af7b19c816
|
|
To avoid the floating point exception that can be seen sometimes on the
Jenkins_Linux tinderbox during CppunitTest_sw_uiwriter.
Change-Id: I270bfbe9c8fbb4cb3a86f45b5f4c3afb32213b9e
|
|
Change-Id: I6c9346917b813c662307999fe1c19a6c0665a656
|
|
Improve the plugin a little.
Create a python script to process the output.
Run it again.
Change-Id: I05c21d8a21c8f4243af739c412fda0a521f9b5f0
|
|
But actually I strongly suspect that this is dead
code.
[AquaA11yTextWrapper rTFForRangeAttributeForElement:forParameter:] is
called only from [AquaA11yWrapper rTFForRangeAttributeForParameter:],
and that is not called from our code, nor do I see any mention of
either rTFForRangeAttributeForElement or
rTFForRangeAttributeForParameter in documentation or when googling.
The NSView documentation does talk about accessibilityRTFForRange,
though. Could this be some copy/paste error since initial commit, code
that has never been tested? Would not surprise me a bit.
Change-Id: Ia1351c293e51e0b75d8b222f78ea19f7801a7c18
|
|
Change-Id: I07bf1403e6b992807541a499b786d47f835b2f81
|
|
Change-Id: I9d820446411eb7dfca37bb3baf5e994f4ba6f421
|
|
Change-Id: Ibb641ab458e49a30637f1dff715480c0ed5d8b42
|
|
Change-Id: I4ad581158fa68f30d07101697b716dc9b8fab746
Reviewed-on: https://gerrit.libreoffice.org/16139
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
|
|
Toolboxes derive from Docking Windows, they are
not layout aware, which is ok, but they need
to tell the thing they are inserted in that their
state has changed if the parent is layout aware.
i.e. docking windows are not toplevel things like
dialogs and need to pass on queue_resize to things
above them
Change-Id: If0eeff90314bef4e828355661a75a0d34a6fc1bc
|
|
Omit the plugin, and sw's FrameControlsManager for now.
Change-Id: Ifb98a2e6e03a9d099efc1668305b96bd9142ca5f
Reviewed-on: https://gerrit.libreoffice.org/16117
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Meeks <michael.meeks@collabora.com>
Tested-by: Michael Meeks <michael.meeks@collabora.com>
|
|
Change-Id: I495ae28194da449ab1b31b2b5ec0d9e08fbcc291
|
|
Also extend VclPtr lifecycle test.
Change-Id: I4d989375ca02327216eb1f37e466aefdb733579d
Reviewed-on: https://gerrit.libreoffice.org/16107
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Meeks <michael.meeks@collabora.com>
Tested-by: Michael Meeks <michael.meeks@collabora.com>
|
|
Change-Id: Ifb5355b3a8f33601bcec0c11ce1afe1c735695b6
Reviewed-on: https://gerrit.libreoffice.org/16100
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Meeks <michael.meeks@collabora.com>
Tested-by: Michael Meeks <michael.meeks@collabora.com>
|
|
Inspired by commit
4dd0ac62855c5b9382cac004c7eebb9bed983a2b
Change-Id: I6ca29aecde357a3cb5852acfc9b5443761052960
Reviewed-on: https://gerrit.libreoffice.org/16094
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
|
|
Unfortunately this breaks Android and iOS.
This reverts commit e4d55e8045c99af65a2cae57b26ec076825c9673.
|
|
"Cleanup crossplatform cairo" breaks Android and iOS.
This reverts commit e152b756b3558a3619e5bedb6b258cc7f0879e90.
|
|
Change-Id: I31724cd56516e6112b66159f722188b228e2eab5
|
|
Change-Id: I770dc9a91bc1239e64ec8e538be0f6a4b03dd08e
|
|
Mac / Win cairo is not built / used, this cairo code can be removed to
reduce code bloat.
Change-Id: I758d674291e25e0722f5c66a0096295e903786b1
Reviewed-on: https://gerrit.libreoffice.org/16049
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
|
|
Change-Id: I6e0399c16d3e900fbca56fc757f342ea893d0ad4
|
|
Change-Id: I19e96b882a5cc8991035a8275aebd4ff586bf9f3
|
|
Change-Id: I5deac9924b99ac1b3e1440623364004b0b44aaf5
|
|
Change-Id: I9a78a75b3d72586b1702ed6fa63bb0b62ce6cd72
|
|
Change-Id: I4fb8f2c9e2080e3aa542d2ccf838e6784baa8429
|
|
Change-Id: I6eb213d6dcf387936967271fba9e2de3879ef479
|
|
Change-Id: Ie4a7705cc3d042d08178e562a2c2ffaf0be3810f
|
|
Change-Id: I3fb71868a9f8f56c76353f3a2d84fdb078c8f8fb
|
|
As agreed in the Design team meeting today.
Change-Id: I660462fb7b56eb3c8f883f8540cf88801e48165c
|
|
Change-Id: Iadf157f3d2673047e2d81c74847b16d12478ca65
|
|
Change-Id: I782e93e6106b3940e7e83c615072beebca1c0965
|
|
Change-Id: I1d6fc43447c3c98e21d1d0752aa621c9ab2a92a7
|
|
Change-Id: Ie84924ee77805ce4b4f6d5a7e77213ce2d51877f
|
|
Change-Id: I46727514629103d8a97140483eca26135929a688
|
|
We will not update with a new version from mozilla.
Change-Id: Icf9571e1efecee18a19760b2eb3041e3d9e6f108
|
|
Change-Id: Ic57a0785db05908ffd9faef30544646d2e70ee5a
|
|
Change-Id: Ia0c8e9d8a22abaa2c06aea2a0f790dc34903ac37
|
|
MS had a really bad idea to store an animated GIF inside a PNG for
some reason. This situation was handled correctly in LO but we
still pretended that this was a PNG file, which was causing
confusion for some users that wanted to extract the image from
the document. With this change we extract the animated GIF from
the PNG and store just the GIF in the document.
Change-Id: I4c70d118e8decd7aa1b108b6b1d725301904a35b
|
|
Change-Id: I08c484c54e27c55157836d68a28d2a0e580499d9
|