Several objects become invalid after ending show prematurely. Data
transmission may be flawed, don't rely on valid base64 etc.
Change-Id: I9bb6929b9cd6b3183948662b472f92e2fa67a7e6
...let BRAND_BASE_DIR point to solver's unittest/installation during CppUnit
tests, and get rid of LIBLANGTAG_SHARE special case. (Intending to add further
code to CppUnit tests soon that requires a fake BRAND_BASE_DIR, so clean this
up now.)
Change-Id: Ia5f0f247e54952f901c37ca31eda53f9c6591458
This commit removes @author annotations, some templates comments. It has some
cleanup.
Change-Id: I995ba7b06d661fcec17f26c368d9449c0bf5ab45
Signed-off-by: José Guilherme Vanz <guilherme.sft@gmail.com>
Reviewed-on: https://gerrit.libreoffice.org/1146
Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com>
Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
Currently there are 4 different debug options:
--enable-dbgutil (the recommended one)
--enable-debug
--enable-selective-debuginfo
--enable-symbols (for advanced users only)
In this table the properties of each option is shown:
----------------------------------------
options\properties | O | S | D | T | U |
----------------------------------------
production-code | x | - | - | - | - |
----------------------------------------
--enable-symbols | x | x | - | - | - |
----------------------------------------
--enable-debug | - | x | x | x | - |
----------------------------------------
--enable-dbgutil | - | x | x | x | x |
----------------------------------------
where
O: optimization
S: debug symbols
D: debug STL
T: trace facility
U: additional debug utility (object counting)
Note:
--enable-selective-debuginfo has the same properties as --enable-debug
Change-Id: Ib8a28c6162f47526d6bb33f81f53835cd11894b2
Using a distance to click to select the best object to select between
normal text and background object.
Change-Id: Ib5b53161c7af2c16f4df379382f2e53fc6d8092b
Now, double-click actually selects a frame anchored in header/footer.
Code has been cleaned a bit as well.
Change-Id: Idb7f3520527a0cb6efe0ea41c62f452bc87c4e8d
The main problem here was due to the click to show the separator when
there is no header or footer under the frame. That code was just exiting
MouseButtonDown too early, which isn't good.
Moved the seperators showing code out of the SwCrsrShell as it has no
clue about the document-position and may lead to problems.
Change-Id: Ia62333b52c5d0659bbe7ec4fcfe6e664db132435
...as there are typically no direct calls to it anyway. What is apparently
needed is to decorate the cppumaker-generated headers instead:
* cppumaker obtains deprecation-information from the documentation strings in
.rdb files. As these are normally generated by idlc without documentation
included (no -C), idlc got changed to nevertheless contain documentation
consisting of just "@deprecated" in this case, to allow to easily tunnel this
information to cppumaker always.
* The mechanism of parsing for "@deprecated" in documentation strings is
somewhat crude, of course.
* For now, cppumaker only decorates C++ functions that correspond to UNOIDL
interface attributes and methods. More should be possible (but, e.g., being
able to decorate a complete C++ class corresponding to a deprecated UNOIDL
interface type depends on whether all platforms would accept
SAL_DEPRECATED_INTERNAL at the same position in a C++ class declaration.
* This could also be extended to other languages than C++/cppumaker.
* Always using SAL_DEPRECATED_INERNAL instead of SAL_DEPRECATED for decoration
is to keep things simple and our codebase working. Improvements are possible
here, too, of course.
Change-Id: Ia2917892f780d477652e4cd9f286588a6898c3f5
SfxItemSet takes a sequence of (start, end) property ranges
not a sequence of isolated properties
reading 1b0f7ee1e0 it appears that the properties
the new code wanted to query are included in the original ranges already
Change-Id: Ifecdf23270d7f3d875d1c0cd942bab659bbabf29
Even for an Android (or iOS, presumably) app with just viewer
functionality, some export code gets included in the single .so or
executable.
For now, when we know that we are producing only viewer apps for
Android and iOS anyway, it might be a good idea to be able to
carefully bypass some particularly pathological places in the code
that generate large amounts of code and/or data that is useless in a
viewer app.
Change-Id: I59b97024ff2855e7bbe53d6ec8782797705f61d8
