Age | Commit message (Collapse) | Author |
|
Change-Id: If63aa3dbc5731f4c17d877cc05dd62ec760984c9
|
|
Change-Id: Ib0c2f0c2b67f40ce75469b434a67c62187aca93d
|
|
Change-Id: I72ce0c0cb1c8d461559ad997ad2c88a25d9e8a20
|
|
Not using UNO API here alone made this code fly.
Change-Id: Ib3eff168bbe49e49fb413909b7a14057f808cdf9
|
|
Change-Id: I4272b45a1c8ad34b540ee39d9ef9dd717d4f6325
Reviewed-on: https://gerrit.libreoffice.org/5572
Reviewed-by: Kohei Yoshida <kohei.yoshida@suse.de>
Tested-by: Kohei Yoshida <kohei.yoshida@suse.de>
|
|
Compiler plugin to replace with matching number(), boolean() or OUString ctor,
ran it, few manual tweaks, mark as really deprecated.
Change-Id: I4a79bdbcf4c460d21e73b635d2bd3725c22876b2
|
|
Change-Id: I898d7a2d3f0ea472daddb9dd32f772a5d7268773
|
|
Change-Id: Iee0521e4f7851f5b51cf6ab7a973bf8b46fb09f5
|
|
This reverts commit 0654a592df05df676540764c004bd5b4e8b693a9.
Sorry Kohei for the noise
|
|
Change-Id: I17b45a5fb6ac5d30be5d3575fec76a61662decdf
|
|
Actually the detection code works just fine without having the detection
service set the filter name here. But it's supposed to.
Change-Id: Ic6a4325b5ceb532d0691781388f66c24cd695ca5
|
|
Change-Id: I4e71517f34988c3fc2d4b8e7627722d690c1b487
|
|
The new format detection service is much simpler than the old one.
In the new framework, each detection service receives the name of format
that it is expected to check against, and it should either reject it by
returning an empty string in case the file is not of that format, or
if the file is indeed that format, set the appropriate filter name and
return that type to the caller.
We no longer need to deal with preselected filters (which is dealt with
in the detection framework itself) or return an entirely different format
that's different from the one being asked to verify.
Change-Id: I3f36951b0ad821d836fb8a56b852e40d43095f09
|
|
Change-Id: If7aa24718c3a4bc1656277f0bb741b41fcaf6f4f
|
|
Change-Id: Ic0dda47f02cd392234876a8945e240bbc915fa6a
Reviewed-on: https://gerrit.libreoffice.org/5453
Reviewed-by: Petr Mladek <pmladek@suse.cz>
Tested-by: Petr Mladek <pmladek@suse.cz>
|
|
Change-Id: I5726261c9fbe479e2b5be6862324d23a30d4ab40
Reviewed-on: https://gerrit.libreoffice.org/5452
Reviewed-by: Petr Mladek <pmladek@suse.cz>
Tested-by: Petr Mladek <pmladek@suse.cz>
|
|
Change-Id: Ide59f0fa382c148abeac2b3dde17cc913183391d
|
|
Change-Id: Ia0a11f636b864e5dd7c8ef6f4e8d1c3bb6f0a26f
Reviewed-on: https://gerrit.libreoffice.org/5507
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Change-Id: Ia742718cebca57237145b16a8bf363a35a95f818
Reviewed-on: https://gerrit.libreoffice.org/5445
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Change-Id: If00f4f6248f40e3a8feb0c11b3d46b85748a97bc
Reviewed-on: https://gerrit.libreoffice.org/5459
Reviewed-by: Michael Stahl <mstahl@redhat.com>
Tested-by: Michael Stahl <mstahl@redhat.com>
|
|
Change-Id: I85995bc3e1fc3c1f01b4d9bded3707ea0b296fa9
|
|
Change-Id: I95844f01d3f7ed6e22b8d78b7a2366b131bd325b
|
|
Change-Id: I92729c7272e87c2aede6cd5134c84d17b466e57f
|
|
Change-Id: Id1eedc86056f7de24913f8156a819f8a0695fd59
|
|
When selecting cells with ctrl+shift, the legacy behaviour was to
take in account to which cell the cursor moved. This allowed the
user to make some convenient selections. This behaviour can now be
turned on with a switch in the configuration (Tools > Options >
Calc > General > Input Settings > "Use legacy cursor movement
behavior when selecting").
Change-Id: I00ae7b4ee001b416cc680c7a650631daec71e51b
|
|
Change-Id: I5d5f65766d4ad3b319b2cbe4f6491d0aab7f02df
|
|
Change-Id: Ia2cd69eb0a180cdfb747a82edefbe1527138b26d
Reviewed-on: https://gerrit.libreoffice.org/5444
Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>
|
|
After commit fc861c7088e9b639a1c2c80f8ba4535c798aeb34 there is now an order
dependency, between any ScPatternAttr flags indirectly set and
SheetDataBuffer::finalizeImport which sets the attributes directly for a column
So the ATTR_MERGE_FLAG that has ScMergeFlagAttr ( and associated
SC_MF_AUTO flag ) is scrubbed when by the direct writting of the attribute
from SheetDataBuffer::finalizeImport -> Document::SetAttrEntries
I've reordered that Table import here and split the finalize ( which happens
before heetDataBuffer::finalizeImport ) so that the databaseranges which were
created before sheet import still happens, the autofilter part of the import
is now deferred ( until after SheetDataBuffer::finalizeImport )
Change-Id: I11bb45ee7b330760fd93ecca30b23399414ac3a7
|
|
This code block happens to be a performance hot spot right now.
Change-Id: I4fa2c4ea27cb6ae4c4331d0bb474eddc167b69fa
|
|
Criteria in SUMIF, AVERAGEIF, COUNTIF, SUMIFS, AVERAGEIFS, COUNTIFS are
not cell ranges.
Change-Id: Iace25057ab3c9af1e2ec3c45c6803d42272f962b
|
|
Change-Id: I39e41abc17979f6b84b787d1078de05475ea8a62
|
|
Change-Id: Ic7ee570935b5d827dc01a483877ea5021da5abea
|
|
Change-Id: Id16a2b29b1d6cf02b94cc6c423e2475a9cbeb8a3
|
|
Change-Id: Iacfb93a4cf9a7b7ac0ae27b9fa6f765e74604dc2
|
|
Change-Id: I72c5e3e47040e78976f46f585b50ab6c12f84986
|
|
Change-Id: I20adfc9148b8afa7a59245349f233604bd9a1d2e
|
|
Change-Id: Ie80c29a73db295ccc8fe975f8fe7027b9a1eb79a
|
|
And do it once when importing xls, xlsx, and ods documents.
Although xls(x) file formats support shared formula natively, it's
still beneficial to re-group it as some old xls documents limit the
length of shared formula span to only 64, or some don't use shared
formulas at all even though they could. And re-grouping just once
is not terribly expensive.
Change-Id: Iff9c605d19baa187553ddab6af8b9fbd4c366d7d
|
|
Regression introduced with 337066eb1fa395990b78d1032c399a4688d2a6f9,
flags and formula token array weren't written if the formula result was
an error value.
Change-Id: I8ccd55a7b43d5ceb79002e01f0b3d33d36d85538
|
|
Change-Id: I8bf6cf93a2f9b5daee77f3dd75b0366caa9ec25d
|
|
Change-Id: I2ea9797156df306b25b25ef42ed865483e08b6af
|
|
Change-Id: I387ef3c2c8345bb5be75909596f59af80b966443
|
|
fdo#60805"
This reverts commit 46d122d4cc405c4070eb4945abd20cdf3a5fac33.
Unfortunately this re-introduces the previous problem of the cell borders
drawn too thick when anti-aliasing is enabled. Also, even with this reverted
the problem will still persist if the user manually disables anti-aliasing
in the Options dialog. So, we *do* need to find a way to draw the
double-borders etc correctly without anti-aliasing.
|
|
Change-Id: I06a8158b7f503976b19383014a7c8a867c0184ea
|
|
Unfortunately this patch creates a very weird ( and took me forever to find
) bug ( fdo#60805 ). Basically certain double line borders seems to
dissappear at certain zoom levels. I guess maybe its possible to tweak
the create2DDecomposition to process the line as hairline at those problematic
zoom levels ( but I suspect that actually would look worse ) Best maybe
would be to tweak the rendering/painting ( but isn't that processor specific
maybe ? ) as is maybe this problem. I admit this is outside my comfort zone :/
This reverts commit a551cad4e35b6b664167d65dfc25e5a0f6990687.
Change-Id: Idb25493ffb038cb1f8ae9b364a29052abafd940d
|
|
Change-Id: Ia3c452f21328e2d5773f245e729905a70d14c29e
Reviewed-on: https://gerrit.libreoffice.org/5312
Reviewed-by: Eike Rathke <erack@redhat.com>
Tested-by: Eike Rathke <erack@redhat.com>
|
|
do not use them where not needed
(cherry picked from commit 4ccb1eb7d58005ab3b501b7c6ff128fadbcd5066)
Conflicts:
basegfx/inc/basegfx/matrix/b2dhommatrixtools.hxx
basegfx/inc/basegfx/polygon/b2dpolygontools.hxx
basegfx/inc/basegfx/polygon/b2dpolypolygontools.hxx
basegfx/inc/basegfx/tuple/b2dtuple.hxx
basegfx/inc/basegfx/tuple/b3dtuple.hxx
sc/source/ui/inc/output.hxx
sc/source/ui/view/gridwin.cxx
sc/source/ui/view/output.cxx
vcl/win/source/gdi/salgdi.cxx
Change-Id: Ie265814a51180bffe3c821a3f2148cb3bb54ecad
|
|
Change-Id: I77726f009338ae49877c5f58fe6c14d386089bbe
|
|
Change-Id: I178f9eb702afb6143c583d5fd54003a427d895fa
|
|
Change-Id: Ib1deab33a8771e196d0520bae872eb0d492c913e
|