- 19 Şub, 2013 40 kayıt (commit)
-
-
Michael Meeks yazdı
-
Tor Lillqvist yazdı
Change-Id: I13d5715248612c9b1b50314d72f5eca202debd04
-
Caolán McNamara yazdı
Change-Id: Ie31da5896d98908fd540146d1105ecc4257fa071
-
Caolán McNamara yazdı
surely given we stream this in on Load, we should stream it out on Store, rather than dump it out Change-Id: Ibf499dad8ebe6eb7a60cdbaf667d35eed8331685
-
Caolán McNamara yazdı
Change-Id: I7cc181ca1cad1e8bce9cb44a7c2e2c7f534921e5
-
Luboš Luňák yazdı
Change-Id: Ibeb24ca336c599e75108a25d1a017f97092681e7
-
Radu Ioan yazdı
- replaced osl_trace with sal_info - added new log areas to log-area.dox Change-Id: Ib47c4b4c9604bca1f8a635dd01bb89702b47b591 Reviewed-on: https://gerrit.libreoffice.org/2010Reviewed-by:
Thorsten Behrens <tbehrens@suse.com> Tested-by:
Thorsten Behrens <tbehrens@suse.com>
-
Chr. Rossmanith yazdı
Change-Id: Iac8a36a1f4a9c56d7b8689acd1b2273550a8c968 Reviewed-on: https://gerrit.libreoffice.org/2257Tested-by:
Caolán McNamara <caolanm@redhat.com> Reviewed-by:
Caolán McNamara <caolanm@redhat.com>
-
Lennard Wasserthal yazdı
If a Metafile's scaling is incompletely defined, there are some arbitrary values used. This bug is just filed as regression because aoo 3.3 used the WMF part and Lo the EMF part! Please use environment variable EMF_PLUS_DISABLE if you have further problems with EMF files. This Patch also adds an (untested) TWIPS scaling, which was missing. known issue: vertical text ratio still scaled differently than lineart. Change-Id: I7c0139853961eb338476a9e3a5e08d3f87225f2e Signed-off-by:
Lennard Wasserthal <Wasserthal@nefkom.net> Reviewed-on: https://gerrit.libreoffice.org/1886Reviewed-by:
Tor Lillqvist <tml@iki.fi> Tested-by:
Tor Lillqvist <tml@iki.fi>
-
Fridrich Štrba yazdı
-
Caolán McNamara yazdı
Change-Id: I33bc390aaa8f6e3cc2505632670970038140eb3c
-
Caolán McNamara yazdı
Change-Id: I69bf7bc33a619c4aa9483e2dc3d5540e4dfa7458
-
Tor Lillqvist yazdı
Change-Id: I360fb8db35b36194c4f7ae08c93126e2a7bda853
-
Chr. Rossmanith yazdı
useful when removing RTL_CONST_STRINGPARAM Change-Id: Ic131876a3fb38e69185342c4c7a46d536d60c8e5 Reviewed-on: https://gerrit.libreoffice.org/2256Reviewed-by:
Caolán McNamara <caolanm@redhat.com> Tested-by:
Caolán McNamara <caolanm@redhat.com>
-
Tor Lillqvist yazdı
Once this was fixed it seems to work nicely. Add keywords in File:Properties and they show up in Finder's Properties, and Spotlight finds text from the document contents. Change-Id: I203576a5a7e53ca3485b0a82f0c6d06122f361d1
-
Norbert Thiebaud yazdı
Change-Id: Idcc2d548363ddab04dd8acaa1dfb854a19ca47ef Reviewed-on: https://gerrit.libreoffice.org/2200Reviewed-by:
Fridrich Strba <fridrich@documentfoundation.org> Tested-by:
Fridrich Strba <fridrich@documentfoundation.org>
-
Miklos Vajna yazdı
Change-Id: Ic99a5a11b32d4712b91d58021e1e9ff3bab7890d
-
Luboš Luňák yazdı
The one command running the soffice wrapper that does also some extra work is the usual and simple case, running soffice.bin is needed only when launching LO in gdb. This reverts commit eee2fe2e. Conflicts: Makefile.in
-
Norbert Thiebaud yazdı
Change-Id: Ifdbfecdb5443024f7186882cf09d8fba998e94f2 Reviewed-on: https://gerrit.libreoffice.org/2213Reviewed-by:
Caolán McNamara <caolanm@redhat.com> Tested-by:
Caolán McNamara <caolanm@redhat.com>
-
Norbert Thiebaud yazdı
Change-Id: Ie8b8741fbad8e5e9f600dc1497b64ecd27515818 Reviewed-on: https://gerrit.libreoffice.org/2204Tested-by:
Caolán McNamara <caolanm@redhat.com> Reviewed-by:
Caolán McNamara <caolanm@redhat.com>
-
Jean-Noël Rouvignac yazdı
Cleaned up the call sites. Change-Id: I6c688cecd4f872ed064ccfa3af4b402a779860dc Reviewed-on: https://gerrit.libreoffice.org/2155Reviewed-by:
Caolán McNamara <caolanm@redhat.com> Tested-by:
Caolán McNamara <caolanm@redhat.com>
-
Caolán McNamara yazdı
Project: help a97475f929677fa26b59ecabe30ecbfa7159a521
-
Stefan Schick yazdı
-
Bjoern Michaelsen yazdı
Change-Id: I7fe4da07852d538216b92b9350903b7022bdc9fa
-
Bjoern Michaelsen yazdı
Change-Id: I54880cd7d404692b8fee16c331c8e7a64508f52b
-
Bjoern Michaelsen yazdı
Change-Id: I06d6dec259f4e1d28d0fb13497097bbfae156b2f
-
Bjoern Michaelsen yazdı
Change-Id: I14bd9c0a4b9b55963da67102468d573f7132fab7
-
Bjoern Michaelsen yazdı
Change-Id: Ibc8178e2dd7209705cb752f9570e414483c319a7
-
Bjoern Michaelsen yazdı
Change-Id: Ib895be66ecb4c95a86696007fdda453d3a3b34e0
-
Bjoern Michaelsen yazdı
Change-Id: I7fdf7fd285d6b8c584d8fe225729f15f3f9798ad
-
Bjoern Michaelsen yazdı
This reverts commit 324d2f94. Change-Id: I0c1c3412554de2093c9c94de89ff74a89869fa6d
-
Gergő Mocsi yazdı
::rtl::OUString was replaced to OUString and all occurences of String was replaced to OUString in dbaccess/source/core/api Change-Id: I9771708408e04dcebe18f49a75c83036740f0ca2 Reviewed-on: https://gerrit.libreoffice.org/2239Reviewed-by:
Caolán McNamara <caolanm@redhat.com> Tested-by:
Caolán McNamara <caolanm@redhat.com>
-
Lionel Elie Mamane yazdı
That's so that heavily related ones stay together: PRINTREPEATEDVALUES PRINTWHENGROUPCHANGE Change-Id: I90513da4ae9ce0798dec91e5057b112735c1cdc2
-
Lionel Elie Mamane yazdı
Change-Id: Ia3d8612e3774ee62b6d885cc9ab801361642c3a3
-
Lionel Elie Mamane yazdı
Change-Id: Id14dd289f8803378838725fbe08e327c9b1d233d
-
Lionel Elie Mamane yazdı
Change-Id: Iffd518a36f1418302955b0d85af8700cf8f9f75a
-
Lionel Elie Mamane yazdı
Factorise the "should this element be printed" decision into an utility function, which is used by 1) AbstractReportElementLayoutController (in charge of non-formatted values: string, image, OLE object, ...) which already obeyed PrintRepeatedValues. 2) TableCellLayoutController (in charge of formatted values: dates, numbers, ...) which blissfully ignored PrintRepeatedValues, but obeyed the display condition. Rename the inconsistently named PrintWhenGroupChange PrintWhenGroupChanges print-only-when-group-change print-when-group-change to PrintWhenGroupChange / print-when-group-change Change the meaning of "PrintWhenGroupChange" to "override PrintRepeatedValues in first occurrence in group". Since this feature never worked under the old semantics, no loss of feature. Since we change the XML attribute name, no ascending compatibility problem: it will be reset to its default value. Pursuant to the new meaning of PrintWhenGroupChange, change its default to *true*, which is the sane default. Change-Id: Idbe8e90565a354f70db222d047b3d51eeddbbb9f
-
Lionel Elie Mamane yazdı
Consider the following situation: Property Name Property Order Index ------------- -------------------- propA4 4 propB5 5 propB4 4 And the loop goes over these properties in this order. propB4 should be before propB5, but with the old code, propB4 would be pushed after propB5: it asks for position 4, but as positions 4 and 5 are already occupied, it gets pushed to position 6. Remaining difficulty: properties from different property index ordering series will be interleaved. This should be solved at object model level; ideally property order index should be unique, at least within an object. Change-Id: Ie235a4b22155df97df139f1dc354247845626620
-
Lionel Elie Mamane yazdı
Change-Id: Id21de98433f52c8659a3432c1c47354e18166f06
-
Lionel Elie Mamane yazdı
Change-Id: I96685f405989fdd3b090b6a482edf8ad65bfd4e9
-