Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Ic5d1090722945dce338973e9e3091546ed792057
Reviewed-on: https://gerrit.libreoffice.org/20160
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Mike Kaganski <mikekaganski@hotmail.com>
|
|
Unknown names make the formula fail
PythonTest_sw_python, especially set_expression is ok
Variables are taken into account
Thanks to Mike Kaganski for his help on this patch.
Change-Id: Ia6f9c54d90ce88138fd9c9df9422b34ce8223ca2
Reviewed-on: https://gerrit.libreoffice.org/20122
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Mike Kaganski <mikekaganski@hotmail.com>
|
|
we were reusing the stride of the surface we were cloning,
but the new surface has a different underlying size.
remove the custom stride argument and just change our stride
calculation to use the same scheme that cairo and GDI uses, which
remove another platform/drawing-system variable
Change-Id: I257dac9757b121642e9ccfde7db0911edc9f3fb1
Reviewed-on: https://gerrit.libreoffice.org/20149
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Zoom level of SwEditWin is kept in sync with the client, so that the
pixel-based comment widgets can be positioned correctly. But that does
not mean in general the SwEditWin map mode should not be disabled: so
that we don't have to tweak the map mode for each and every
postMouseEvent() call and still be able to send them using logic
coordinates.
Change-Id: I6f686b93d2509d52fdd34e84a502cf04e1ce6e59
|
|
Without this, vcl::Window::ImplTrackTimerHdl() will be called on a
deleted vcl::Window.
Can be reproduced with a comment having a scrollbar in a LOK client,
then clicking on the down button of the scrollbar a number of times ->
crash on exit.
Change-Id: I5d67f96e8baa199f65ec5cf39cb5d39c8162ff33
|
|
With this, if a comment has a vertical scrollbar, then not only the
buttons of the scrollbar can be clicked on, but also the slider of the
scrollbar can be dragged.
Change-Id: I2e39e18bf60c42a878bb8bfd808f1d47be27eecb
|
|
Currently, negative scaling (mirroring) is lost in
SdrTextObj::NbcSetSnapRect, when rect is justified.
This patch cares for this.
Possibly it's better to make these changes directly in
SdrTextObj::NbcSetSnapRect?
Change-Id: I353ff01626e15b398de95e28eae78572991dfdc3
Reviewed-on: https://gerrit.libreoffice.org/20109
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Armin Le Grand <Armin.Le.Grand@cib.de>
|
|
Change-Id: I619c2cf1765df97159fc52ee84e0e9e8d16a22fe
|
|
If a comment had a scrollbar, and the user clicked on the down arrow of
it, then the button remained in the "pushed" state, as the scrollbar
invalidations were not routed to the LOK client.
With this, the button gets back to its non-pushed state after the mouse
button is released.
Change-Id: Ie4ba5d0ec07229b0cfc08532e8e91ae25f7a4c9e
|
|
Regression from commit 2b78f2cd7b9e4bab0f3b3b9119238f36a1bbc7b2 (rhbz#988516:
DOCX import: fix context stack when importing header/footer, 2014-03-05),
though that just made an existing Writer layout problem visible.
RTF/WW8/newer (drawingML) DOCX import doesn't have this problem, as those
import pictures as sw graphics, not draw ones.
<w10:wrap type="through"/> is normally mapped to our page wrap (as it uses
"through" in the "not only wrap around, but also in the holes of the shape, if
it has any" context, not in our "text should go through it, so no wrapping"
one), but for some reason in this case (most probably due to the extreme large
negative margins) Word handles the situation as our through, i.e. the text
should not go to the second page, as it would normally happen with a "Word
through" wrapping.
Work around the strange situation by ignoring the wrapping request for extreme
top margin values.
Change-Id: I20555b1fa7a769e20c40a3a5ff3873807403e937
|
|
Change-Id: I0d9c79d0756ef85260d3b69cb1e879d7665bf356
|
|
Change-Id: I323a038e5581b00cd3a4ea2f362c66540377759e
|
|
Change-Id: I975f35031b1833be376881d534dc6f91fae6072f
|
|
Change-Id: I3e146c4287df70bbf58443caecfa62453c116ecb
|
|
Change-Id: Iefd6d4a08a4a5f90f4f2f95889f6425aabe61334
|
|
Change-Id: Ib1c334825a6629224fe0c8fba564656d53e67410
|
|
cairo can therefore always render to a svp virtual device with
need for a fallback
Change-Id: I5d03ae541820389e26f7448444444be009fb28a4
|
|
are 1 or (rarely) 8 bit and lock that down.
Change-Id: I3d946ebef34ffb71c5adea7aa420af50e9584e05
|
|
With this, if a comment has enough content that it gets a vertical
scrollbar, then tiled rendering output looks OK, even with non-100%
zoom.
Change-Id: I699aadc11b6c34fb0791e70705719fd61169d972
|
|
Since commit 2b5bf2f1c57d6585ec898c4c44a74c5b47f09ab9
"graphic import improved" from 2006-11-20 by Oliver Specht,
there is an unused code reading pixel size (PROP_SIZE_PIXEL) of an
image in a part of GraphicImport::createGraphicObject() that imports
the wrap polygon.
When there's no PROP_SIZE100th_M_M in graphic, the imported wrap
polygon was simply dropped, and then automatic contour was generated
for graphic. Now we import contour correctly in this case.
Also, as paragraph background overlaps non-opaque graphics,
we need to set opaque to true regardless of behindDoc value of
wp:anchor.
Change-Id: Ifa5eec9f8ccaf5ba051732b6e4f965ae8606a1cf
Reviewed-on: https://gerrit.libreoffice.org/20103
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Michael Meeks <michael.meeks@collabora.com>
Tested-by: Michael Meeks <michael.meeks@collabora.com>
|
|
It was used for both x and y positions, hard to read.
Change-Id: Ie2461662671405a6348aa24c3946b376c123f699
|
|
This reverts commit e110397a2816037b421bdcdeed0a2fdab5cd99d7.
Variables weren't dealt with this.
|
|
New fix which deals with specific "foo" case
Change-Id: I479b30abf22315ddca6151cba220574029cb1a91
Reviewed-on: https://gerrit.libreoffice.org/20113
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
|
|
This reverts commit 010ed5e6f4505647b0f9043d1cf5001db2057e0d.
The fix was too naive and generated a problem during PythonTest_sw_python with set_expression test
|
|
Just indicate there's an error if the function name is unknown
Change-Id: Idad6dd1911c2e8a0206f70fb933fcfd540a887d2
Reviewed-on: https://gerrit.libreoffice.org/19919
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
|
|
...than by template parameter pack (even if that requires using ServiceDecl*, as
initializer_list cannot take reference types)
Change-Id: Ia986201b52d8daedfe925f132ebc79bc2c0ba378
|
|
Change-Id: I42fa834464fd4cd7f0c1f11e310c1145fb1f071b
|
|
This one is special, as normally its map mode is in pixels, but we need
all sub-widgets to work in twips when tiled rendering.
With this, the scrollbar widget (both the buttons and the
button/background area of the scrollbar itself) is painted at the
correct location when Writer comments have enough content so the
scrollbar is visible.
Change-Id: I4ee9ef8618974b965339078d2262364ec19732ef
|
|
Change-Id: I56969839a93af975466ab6c28f2f87557e4d7f1b
Reviewed-on: https://gerrit.libreoffice.org/20074
Reviewed-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>
Tested-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>
|
|
Change-Id: If255e6bebe501f1b0959613ce091b322af064628
|
|
and use them
Change-Id: If4dc9df63db37185228aeaaab2979498d61304ec
Reviewed-on: https://gerrit.libreoffice.org/20055
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
|
|
Checking for a bool is certainly cheaper than a chain of member function
calls.
Change-Id: I9520194e58e75264f3fcbb413a618e3995f59a4e
|
|
These have been defined in the widgets
Change-Id: If46a6862872286a454804846128bd8658f60af9b
|
|
Instead of invalidating the whole area, invalidate the sub-widget when
the whole area of the sub-widget would be invalidated.
With this, a test comment with enough comment to have a scrollbar
results in 3 paintTile() calls instead of 11 ones (70% save).
Change-Id: I2fe317549eefac9a63aaf50f5a9a242e15c4dc86
|
|
Change-Id: I2220ab194384fb397716bf3227d38716ba54f537
|
|
Change-Id: Ia513821b43729951c7b097fea498f0e22b9d10ea
|
|
in chart2, we remove a local equivalent of the method
Change-Id: I25129a3d1ea1dd724eb9cd38a57be37a78b3d100
|
|
Change-Id: I09f3c5cc9e98639bf2b7c4cb37197cb9fb819c82
|
|
Change-Id: Ie7b0d7f7d4549afbd9152d6afb0d0b6078e24bd9
|
|
Change-Id: I19efc6050c78162e0889437d4c8285d1a6714e82
|
|
Change-Id: I9a6a75457078dc6383673f4c1a2012b69b5cefdd
|
|
The new GenericPopupToolbarController takes by default
the popup menu controller that registered for the same
.uno:Something command, and sets ToolBoxItemBits to
ToolBoxItemBits::DROPDOWNONLY. If a different command
specified using the "Value" property - takes the popup
menu controller that registered for this command, and
sets bits to ToolBoxItemBits::DROPDOWN.
Change-Id: I75c5300bd27fcc9f618f2ee0df2aa6aefd088239
Reviewed-on: https://gerrit.libreoffice.org/20040
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Maxim Monastirsky <momonasmon@gmail.com>
|
|
Change-Id: I9ca5739462742a4e3ec3a034918891e53022d6de
|
|
and improve the script a little
Change-Id: I2792ea4dd5df3a50736fbe209225c3f16fb86b84
Reviewed-on: https://gerrit.libreoffice.org/20033
Reviewed-by: Noel Grandin <noelgrandin@gmail.com>
Tested-by: Noel Grandin <noelgrandin@gmail.com>
|
|
Regression from commit 54a2c8c006e2f216e9d8c6b0ed625180c843c48b
(tdf#39080 Interactive hide-whitespace mode, 2015-08-30), the problem
was that SwPageFrm::IsOverHeaderFooterArea() checked if the header is
active before accepting that the user clicked in that area.
Don't require an active header at least in non-hide-whitespace mode, as
the member function is used in the "could there be a header here" sense
in SwEditWin::MouseButtonDown() to show the controls that allows
actually adding a header.
Change-Id: I6f905920113aed1512e333e718a8f26d88a3245d
|
|
Change-Id: I0f45b1a6ab198a8403073eea05497e76f758250c
|
|
Change-Id: I3310813c971aa7abffccc0b7f462e05caa83482e
|
|
When tiled rendering, then only the render context (or failing that,
SwViewShell::GetOut()) has the correct zoom level, so use that when
doing pixel-to-logic conversion or scaling pixel values.
Change-Id: I265a642b8253c6eced42da2a0e06a2de25c36ca8
|
|
Change-Id: Id78cae55eb89520bd87713f9ea6c009c922f2870
|
|
...than fixing the avalanche of loplugin:staticmethods issues caused by
b5eaa0f9f00cd62f4769c3e8860d788844ccf557 "use unique_ptr for pImpl in sw/,"
given that SwMailMergeConfigItem_Impl has mutable state?
Change-Id: I342511d0f39086f33e2a8abd2c377341455d54a7
|