Age | Commit message (Collapse) | Author |
|
|
|
Change-Id: Ide1d0b6c5cab56d5c383853d349d70b21401a533
|
|
ported from the broken java ver.
adds a native ICU regex sanity test.
|
|
Create a merged XLinguServiceManager2 interface for this service to implement.
Which is backwards-compatible, but does not require creating a new service.
Change-Id: I297bada1066cd74809108641b56ee4d5898112ec
|
|
...in sc.ScModelObj::com::sun::star::sheet::XDcoumentAuditing, where a call to
setFormula causes an arrow's getPosition to change Y coordinate by one. This
workaround should be removed again when there is a fix for the root cause.
Change-Id: If58f6c0cdc692ce2a8da35aa4d35baefa15663a5
|
|
More tags removed and with it, more commented code was found. So remove it all.
Not functional changes here, just a cleanup.
Change-Id: Id4a6b3126ca32f3460dec3056b9caa370d0ee69c
Signed-off-by: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
|
|
* As UCB is only ever initialized with "Local"/"Office", remove this
configuration vector completely. The "create" ctor creates an instance
internally initialized with those "Local"/"Office" keys. Special (test) code
can still instantiate an uninitialized one via plain createInstance. And for
backwards compatilibity process startup still ensures to create an initialized
instance early, in case there is still code out there (in extensions) that
later calls plain createInstance and expects to get the already-initialized
(single) instance.
* XInitialization is an "implementation detail" of the UniversalContentBroker
service, do not expose in XUniversalContentBroker.
* ucbhelper/configurationkeys.hxx is no longer needed and is removed.
* ucbhelper/contentbroker.hxx is an empty wrapper and is removed; however, that
requires ucbhelper::Content constructors to take explicit XComponentContext
arguments now.
* The only remaining code in ucbhelper/source/client/contentbroker.cxx is
Android-only InitUCBHelper. Is that relevant still?
Change-Id: I3f7bddd0456bffbcd13590c66d9011915c760f28
|
|
Change-Id: Iacfcb2e16cb0e3c25a4cd0678a374fe5111284f7
|
|
Change-Id: I694cff583fddb713a59e5d6b8e15ea06a2be63b6
|
|
Change-Id: I4229ea7a4ad4d669db824e14ee6a8acb2ac205a0
|
|
Java IDE's get upset if the package does not match the path, so move some
files to make them match.
Change-Id: Ia6a1f3dc572cc1d30492491de9cf1462f2887e6f
|
|
Change-Id: I13be16beac258c551e58654b4fc37877d7bb9695
|
|
Change-Id: I7eb24b2d552ec5da752b58ba790ed58fb88728b0
|
|
Change-Id: I20a79d3d8f71dc48fc2662563f9c890dd3d94aac
|
|
Change-Id: Ieafe29dd9e23bb40a2a80bd231c21e30faa9a40e
|
|
Change-Id: Ib6f3af37906583af376687962b758d348431585f
|
|
Change-Id: Ibe162afcf95682286e1a66a8029dd4b1d6ad7cfc
|
|
Change-Id: Ibaccfd0312ab6697d8c9887367ea664163767587
|
|
Change-Id: I9f49970e5e06d1afd3fc066a20d1671c93e262fc
|
|
With gb_Jar_add_jar and gb_Jar_add_system_jar adding to the manifest
classpath automatically it is no longer necessary to call
gb_Jar_set_jarclasspath manually except for the URE jars, which
are apparently not supposed to be added automatically.
Change-Id: I1e743e7ecb9cb5651e02005aa09e127bea1b0a29
|
|
Change-Id: I7d875dd74f8eff05f7a291100841779abbf5fd1c
|
|
reportbuilder, license file not needed.
Patch contributed by Armin Le Grand
http://svn.apache.org/viewvc?view=revision&revision=1305814
Adapting extras/ to our wordbook setup.
|
|
like 3d3b3f656f92790225b89aa31ee61163fb2fc7e5
Change-Id: I6e80717de009e8a3a89ffc80cb945cc832917f8c
|
|
Change-Id: I2b863b43db59e6904f97d9ad22fdb04013e8c76d
|
|
This is all of the code I missed in my first set of patches.
Change-Id: I8c7c9e5ac28dc3c2f3ac062c806fbf0787c997bd
|
|
Change-Id: Ied9c8635cde96d2d00d66a68cd8387799455c2ec
|
|
Change-Id: Ib687f314272f6a8f0d6c609a1fd06e4061fd0f39
|
|
Change-Id: I7ea32cad40a6657e4e5886d04af008cb6d67ac6e
|
|
Change-Id: I12f8c448961919e153047e28fee2a0acf3af1002
|
|
Change-Id: Ibb568e841ff574d5232429ce0ba99e421ed7f05c
|
|
Change-Id: I630b22da7fbfd2a1c821420d045146e5042c5c28
|
|
|
|
|
|
Change-Id: If17439ae83eb063a7ab054c3701e23dd48f1edd1
|
|
Change-Id: I8018d9b5fa01d1720c0392dc5fdc4a0656f25a35
|
|
Change-Id: I6c145e984c885c7e06caa1c27bfb354ea49ad9ce
|
|
Change-Id: Ice06e639213aeb6f7f23cbf4634947dd25613db1
|
|
Change-Id: Ib9a3e9620064aaea3d51f432b523861656363f7e
Signed-off-by: Fridrich Štrba <fridrich.strba@bluewin.ch>
|
|
Change-Id: I60a02dea64a5f6fd34c2de86e60bdfb9171b3ea0
Signed-off-by: Fridrich Štrba <fridrich.strba@bluewin.ch>
|
|
Change-Id: If58683331c50f2a95204e8e2dea11edbef3ccb63
|
|
related, i#87757 and 8bafe38c569afa2e1055eb647cb7ff161ddd1230
which itself is related to ce14342c4292628a641a72d4f63d9c048e030c6a,
These character bounds are backed by what's the glyph bounding box for the ink
used for the glyph. Whitespace has no ink so its an empty Rectangle. Which
brings the awesome RECT_EMPTY into play.
It might be a bit dubious in the first place to back getCharacterBounds with
the glyph bounding box in the first place, rather than maybe the advance width
or some such. But lets assume that decision was intentional.
So, the qa test should accept that a glyph might be of 0 width anyway.
Then, tweak rectangle merging so that we can preserve the correct top-left
position of an empty glyph
So, we can determine the correct character index given the top-left position
of an empty glyph
Change-Id: I5e18460ff7cd90cd27d5eede2aa0a5494c36a5d3
|
|
...in the vein of e43966b29cc36ce36245cfb2c63c3e24a0eb523f "Fix up unit tests
that assumed two or more sheets per default"
Change-Id: I450f561721edeaa6855499d20c2196ceb8d2f546
|
|
|
|
Do not check length of first word for AccessibleStatusBarItem, which
now contains "Words: 0" since ce14342c4292628a641a72d4f63d9c048e030c6a,
but the test stupidly assumes that its text does not contain a space.
|
|
Change-Id: Ib852987c2040d47cd3de08c6aebc649a068378d6
|
|
Change-Id: Id7d5744af4800ef5ac6bd70b97f79a76299a2e6b
|
|
this removes dmake completely out of the build for migrated modules
build.pl now assumes modules to be gbuild, unless there is a
prj/dmake file
Change-Id: I674a036b182ee13c5ec093e83cb3d38133112d3b
|
|
This is related to 10e580c57b907420e8c6d816325445a40a720e4a
|
|
Naming convention for gbuild methods:
- "add" is used for stuff that is logically a part of the target
(i.e. not registered at the Module, but defined in the target's makefile)
- "use" is used for stuff that is logically a different target
(i.e. it is registered at the Module, has it's own makefile, may be
in a different module than the target)
|
|
|