Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I020c7ce4d9aa93cb0292378a410cdb9f7788e920
Signed-off-by: Michael Stahl <mstahl@redhat.com>
|
|
Change-Id: I5d09d460e145bc3dc04d0cdd27bc4a1094053669
|
|
Change-Id: I98b88ca3369a2c888fd63796e39d42376d513002
|
|
Change-Id: I015c89740631dfcbe62cab62f75b4a44d2b3b35a
|
|
Change-Id: Id9296115f30858e7fd470a199e59343a96d7deec
Reviewed-on: https://gerrit.libreoffice.org/16712
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Samuel Mehrbrodt <s.mehrbrodt@gmail.com>
|
|
"Noli me tangere" literally means "don't touch me"
Change-Id: I7804030703ab78b3dd8899e6479005eaaffae554
Reviewed-on: https://gerrit.libreoffice.org/16704
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Change-Id: I65a60acd956768f6a023c83053700803e5a8f1f2
|
|
themeing has changed around quite a bit, and there's insufficient interest to
get older versions looking right
Change-Id: Ia2ee58d66c859e3bf00b54413fac1efb00d38dd3
|
|
IMDeleteSurrounding is used by input methods to take multiple
keystrokes and convert them into a special character. Then the
composing keystrokes are removed.
Before this fix, the cursor placement was not adjusted,
so the special character was inserted in the wrong position
and if 3+ keystrokes were involved, the wrong characters were deleted.
Change-Id: I35b97bc150dc68ffe65eebc59450e21e0033bd16
Reviewed-on: https://gerrit.libreoffice.org/15961
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Change-Id: I845a3eda41263a07e1e69eb6ff37ff5ab2576905
|
|
Change-Id: I906f53ca5428b51077b4ac28462c2e8827f2a31f
|
|
Change-Id: I173618b2e6a2ad69918da8b85ec0eef7099f1d3d
|
|
Change-Id: I280408bae5d9c15c6bbc7da5f3e4ec8dd20757e8
|
|
The setConfimOverwrite function must be set after setOperationMode function
Change-Id: Id5ab54be502e9c96eba3d7ab600b5e06e241c8fd
Reviewed-on: https://gerrit.libreoffice.org/16517
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Katarina Behrens <Katarina.Behrens@cib.de>
|
|
Change-Id: Ib07f3e484f0065a0c72cc0672fc5d975c00f38fa
|
|
To create and destroy thread-affine Win32 Windows and DCs, non-main
threads SendMessage() special messages like SAL_MSG_CREATEFRAME.
The main thread must handle these messages and return the result to
un-block the other thread.
This works fine as long as the main thread is in its message loop anyway
and blocked on GetMessage(); however if the main blocks trying to acquire
the SolarMutex that is held by the sending thread, deadlock results.
In order to work around this, there is some peculiar code in
ImplSalYieldMutexAcquireWithWait() to avoid blocking the main thread on
mpSalYieldMutex but instead block in GetMessage().
The crucial detail is that GetMessage() will immediately dispatch any
message sent via SendMessage(), which avoids the deadlock.
https://msdn.microsoft.com/en-us/library/windows/desktop/ms644936.aspx
https://msdn.microsoft.com/en-us/library/windows/desktop/ms644927.aspx
Most of the Win32 WndProc that acquire SolarMutex do so via
ImplSalYieldMutexAcquireWithWait(), but the main thread may also
temporarily drop SolarMutex and re-aquire it with the questionable
SolarMutexReleaser hack, which calls ImplSalAcquireYieldMutex()
instead, which blocks on mpSalYieldMutex.
Fix SolarMutexReleaser to call a new function
Application::ReAcquireSolarMutex() that does the right thing here:
acquire SolarMutex via ImplSalYieldMutexAcquireWithWait().
It turns out that this problem was already fixed before in commit
6a8fd4c76a969ac98d1aff91ff7442f43aee0006 but the problem was
insufficiently documented in the commit and it introduced the bug
that Application::Reschedule() was called without having the SolarMutex
locked, which caused timers to run without SolarMutex, so the commit
was reverted in 1ef1781390845d03b6e1518bbac81b818be62f3d.
Change-Id: I60aae555a9ee3c6390f584feddbc6b3cb7de0250
|
|
Change-Id: I91d21e3d1663880de14792ded0a1e079d1a40f09
|
|
Change-Id: I0f10d03c1e4481e8efa765e52b5264071c86a3cf
|
|
in favor of hooking in via get_accessible
Change-Id: I8c265e0d9a5f8bdf02b7ba4be71fc58194cf5aa4
|
|
Change-Id: I89cfde9b4c97852d36817b716ac08bd32096915b
|
|
Change-Id: I6c82e5071038990489e85ac27758867205ba476a
|
|
Change-Id: I4bf77a912296f2d4a14c8bedf6b6bed6b52f9023
|
|
Not sure here if we should set true or false by default
Change-Id: I120c33bf726150506d282e972facd4dca0db83aa
Reviewed-on: https://gerrit.libreoffice.org/16456
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Change-Id: I96dbe2c1213c78da1114f9270953334a38c7b2ae
|
|
Change-Id: I6a41ae2b8056737008add98c35d06f3859e71171
|
|
Change-Id: I35de4ed31bfb9830f52aa5a25ea12bdf719c56ef
|
|
Change-Id: I4b4f09ee3fb7edbda3b6bb5af024c0966e3a2082
|
|
Change-Id: Ib3c6d6689c4b79a636a3f2f0f985f3573aa46f3d
|
|
Change-Id: I261596e5d20360ecfaf57f9ddc4419ca305e3194
|
|
Change-Id: I6805178d2a344243d487ace3331ca71b667cd819
|
|
a hold over from before
6efb7f65eea764ffe5b71f65f9b7eea125183ec3
I believe
Change-Id: Idea86f782cad4da98bbe4308968277886923ee5e
|
|
I took example from https://mail.gnome.org/archives/commits-list/2013-June/msg06434.html
Change-Id: I5fb090c3245848c92238f34259f1a2f77f9080c7
Reviewed-on: https://gerrit.libreoffice.org/16432
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
This reverts commit cf92da3d6e1de14756efe3f1ee79f393a2f3787d.
iff can mean "if and only if" so not a typo
|
|
Change-Id: I3fc60856b5a56e71d70b55c89323be074bdec3b3
|
|
Change-Id: I3e97200d59a97271617a6e9a88c807a07a33edfe
|
|
Change-Id: Ic316b18eace3445edef346fe319cbb0e557607fa
Reviewed-on: https://gerrit.libreoffice.org/16412
Reviewed-by: Michael Meeks <michael.meeks@collabora.com>
Tested-by: Michael Meeks <michael.meeks@collabora.com>
|
|
Change-Id: I196812200ab82ba0d457b59022f472f942615220
|
|
Change-Id: Ia54eeae792efe65ca03ac08c8f5e70a7643a0b69
|
|
Change-Id: Ifc63714b6b9e797b668cccc46052cb9d791122ea
|
|
Seen with gtk3-3.10.9.
Change-Id: I0fc3f6187e270bb13d110bee7c817b5f48d4ce50
|
|
because the gtk3 fpicker puts them in the new header bar
are now
Change-Id: I78334476b42366ffdc64da9460eb017c8bc61622
|
|
Change-Id: I406977acab12a2f805de1f57b91378e9b80195d4
|
|
its clearly accidental to do this only for gtk3, left over from various
screen/xinerama untangling efforts
Change-Id: Ic91f41fad5748f68fbefca1d6798fef6e2efe469
|
|
Change-Id: Ie96ccd3b3b0e2bebf10496f91d110d9a1a62e133
|
|
Change-Id: Ibf2184f565225423f57597fe96164565b5a3194a
|
|
No need to introduce a special env. var for this I hope.
Change-Id: I700299c4f40d504a4a437e9bb73f5b24856f9bf8
|
|
Change-Id: Ibc9e93c702e885b14d7c0beac453479e9171f329
|
|
Change-Id: Iee0c33cba80243b39b6de96cf58b8b274346e522
|
|
Change-Id: Ic6a373fd3d809f7fc8b3d7f724be7a56383f3fa8
|
|
(like 8313f68355a7f1f51e930c74f215d823ff086457)
Change-Id: Id170cc95f5271d3e5c3fa84dafd848e7f8a96503
|