Age | Commit message (Collapse) | Author |
|
Change-Id: Ifa15f4ed3107b1075b504f09d2cae69ee38d347a
|
|
...at least since f74efe63d9a70da723f046c1c6708b9254dfa887 "callcatcher: remove
newly unused code."
Change-Id: I7067e9e6af6693c1401510e2de196533d6963cb2
|
|
(cherry picked from commit a738920303e77022fa89740c16cb832ee3477fa2)
Conflicts:
odk/examples/cpp/complextoolbarcontrols/Makefile
Change-Id: I28af30dc04068c670d31be7494b7ce9a7a25c3a3
|
|
(cherry picked from commit 1307f0949c9b6e1ef2e8a3128c2113bbd7f17a58)
|
|
Change-Id: I7fb61144d8ff263e97de8cb7088b9eefdaafe52f
|
|
...which is explicitly supported by Boost.Container though, but we cannot use
boost::container::map here as Boost.Container is only available since Boost 1.48
and our base is 1.47 still. However, there appears no need for Children to be
sorted, and std::unordered_map (and thus boost::unordered_map) requires that
pointers to elements are not invalidated by insertions, which we do require.
Change-Id: I70ad6f40318d2bafae53ebb67d84c1c89a7d68f6
|
|
The margin of the floating table from top of the page is not being preserved correctly and it also get increased.
The w:tblpPr tag is also not preserved.
Reviewed on:
https://gerrit.libreoffice.org/9185
Change-Id: I8a27a4bab94a1afd27a7ba49ca55ff014918fffc
|
|
Change-Id: I22368254727d1b78337cce42425e27fc7e2588c4
|
|
Change-Id: Iad9c5270e90c7492598764038ad278309da73091
|
|
Change-Id: I9933a429f42f8a350a88aa77514f934560ed58f3
|
|
Look for code like:
xxx ? true : yyy;
Which can be simplified to:
xxx || yyy
Change-Id: Ib7ca86580bfd0cf04674328a3c0cf3747de4758d
|
|
Change-Id: I093ef950f7097021dec3b829d4e11e7b20fc9292
|
|
Change-Id: Id5ae0cf42aa8d6ed464eb1149ebdd172a284a75f
|
|
Change-Id: Icd2d219446cdf78c4be97f96e38c9e4b174f9ddd
|
|
Change-Id: Icee44999c175b5d964ebd51c56e9a1585506e036
|
|
Change-Id: I16bb4ec77cccf0ff9e73f02e13288562004eb5bc
|
|
Change-Id: I894cbb42b795f1adee41694011fa2477f87850f0
|
|
Change-Id: Ia36e042d30afcc13be5fa3452123ae0778217877
|
|
Change-Id: I4a86de032970bfd9cba6270e8e6c6a00e550d74e
|
|
Change-Id: I8943355de1b9440104e0281131fb0df3fc599bb4
|
|
Change-Id: I1f11cdff0de48e3281a58aec9ea37a78c637195e
|
|
Change-Id: I2febe40b1128eefa8838f3dc0836863ed96c0048
|
|
Change-Id: Ic54d87505ac628abfec6942403a066cdb3e02a01
|
|
Change-Id: Ie5f55feb39798dff27e0c6b41d5b88b6e9bf19bc
|
|
Change-Id: I4c2d0447526bda4ccbe2fa7edaf8be1886d214f0
|
|
Just remove the inner rectangle. Now it looks nice.
Change-Id: Icd3d3971292f958d1ffdd3dc6a7697005b5f9047
|
|
Change-Id: I89f1f5771eb7d96da233a8c7386b906b2a3a9c3e
|
|
Change-Id: I9906b4e58fd8672e51f6aa2e56ec68bb28772500
|
|
Also put a missing space before MAX
Change-Id: Ie2def48ec66d4de91bd16c39ed821c4028b6d1c6
|
|
Change-Id: Ib92adfc83c963ecfcfa7fdbc2ec71f363a181330
|
|
Change-Id: Ifd53e37d23c29efb2f084a39b48c88ea4bc0d70a
|
|
Change-Id: I77eaf1dad9ce4c855b5f88bd8568944fd4128227
|
|
Makes it possible to see the messages immediately on Windows; otherwise the
SAL_DEBUG() etc. is useless as it shows on screen too late.
Change-Id: I701922aa4fcacf66d6b044e0badca7ef1f9cac94
|
|
Apparently it can happen in JunitTest_sw_unoapi that between the
getAccessibleChildCount() and the getAccessibleChild() calls that the
children all disappear; try not to assert in that case.
Change-Id: Iec8e373281950bf684fa76d69f8c4625ecd1255a
|
|
This does not appear to work so well: for a row with multiple cells,
when the second cell frame's SwAccessible is disposed it will send an
event, and the AtkListener will then request all children of the row,
and this causes a new SwAccessible to be created for the first cell
frame that was disposed previously.
Unlike most other events, Dispose events cannot be sent delayed.
The SwAccessibles are disposed from ~SwCellFrm already, that should be
sufficient.
Change-Id: I6da72605e5386540f8d82535fca151e97d70869f
|
|
... with accessibility enabled: the SwCellFrms are deleted, but the
entry in the SwAccessibleMap::mpFrmMap is not removed, because Dispose
returns early since the connections to the nodes have been severed already.
This then crashes in some questionable code that iterates over and uses
the frame pointers in mpFrmMap that was added in
76c549eb01dcb7b5bf28a271ce00e386f3d388ba (where previously only the
WeakReferences were used out of that map).
Change-Id: I13885c6ab9a92e34e95925f275e15c20fdc600b7
|
|
... before firing events from them; use a thread-safe WeakReference.
(regression from 76c549eb01dcb7b5bf28a271ce00e386f3d388ba)
Change-Id: Ie060d27cc44415e9a75b75027f5510577ac17a6e
|
|
Change-Id: Ibca921eff3647507ffb7e9011a84aeefbec58d7a
|
|
maItemListRect serves as a sort of bounding box for what items /could/
be visible on screen, however it is only used for determining the id
of an item we have just clicked on -- given that we already know that
we are clicking inside the visible area this is an unnecessary check.
In fact this check is erronous as we no longer limit ourselves to "whole"
rows as of 806919adf9c9bafbaba92c2d2ab35d2e2f9863f8 -- i.e. the previous
assumption was that a view large enough for n rows will show precisely
n (whole) rows, whereas we might be showing (n-1) complete rows, and a
fraction of a row at the top and bottom of the screen, i.e. a total of
n+1 rows, where maItemRect only encloses the top n rows, meaning we
were erronously ignoring clicks on the (partly visible) lowest n+1 row.
Change-Id: Ia52ed2e0d217a9f077cef86ee9c1847252844995
|
|
Change-Id: I96e84e3ec756216fabe9739e6bd53d2a89d186b5
|
|
Change-Id: Ifd89b00c525ed4d75fcffe92845c4ca2f73705a8
|
|
Don't be fooled even when the document doesn't have a drawing layer
initialized. Sometimes a note creates caption on demand later, but if
the drawing layer isn't there the caption will not get created, which
ultimately causes this crash.
Change-Id: I37f4902fa84de91c9f793dc352127d9345a725e3
|
|
Change-Id: I7ac9792da93a1b5231ddac5398823667b28adf92
|
|
There is a good reason for that: File lists of
some file pickers handle double click event on
mouse down. So if a start center thumbnail is
exactly behind the file on which the user double-
clicked, it will receive the mouse up event, and
will also open.
Change-Id: I9fc9ceff0874d0486d5b568c9b35143c8d8aabf8
|
|
Change-Id: I3055df538fc4dfa625aa942ad0d0e6b6299c53b3
|
|
Change-Id: I6d7f6e035bb0dcc86f8aebfdfa4b7f9521bc8820
|
|
Change-Id: If22324ea65a45ac93f6c4b9cbaf9cfb11ef91195
|
|
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/Headers/Events.h
says that 0x27 is kVK_ANSI_Quote, which we call KEY_QUOTERIGHT,
i.e. the plain ASCII apostrophe, while 0x32 is not the ASCII tilde but
kVK_ANSI_Grave, which we call KEY_QUOTELEFT.
Makes the Command-' binding (see Kohei's
56cce6fd8151a916e1be540ac18724b46d1b15fc) work at least for the US
English keyboard. But not for the Finnish keyboard, for instance,
where the key labeled with an apostrophe (or "ASCII-style" single
quote) generates a different keycode than the single quote key on the
US English keyboard. (Which, I guess, isn't surprising as it after all
is a different physical key.)
In other words, situation normal, using keycodes is a horror as
always...
Change-Id: Ibf8f994370fec75849391e1dba30c7b7d54d237f
|
|
Change-Id: I2acd44d54966dd227f5dc23ca4acde3c50ca8347
|
|
Change-Id: I9fd2980a32bd0a3eb4849a53f29cc10b9a371f4c
|