Age | Commit message (Collapse) | Author |
|
Change-Id: I3c1163f9757a4592692bb8a920d1dc679bf53699
|
|
Change-Id: I228c0bca3133e94b28db2540dbd41e8b4fd1eee9
|
|
Change-Id: I457deb8d544b97874701dec37d8baee237ce4ebb
|
|
Change-Id: If2553d96472e6ced9b2fad4c202d0793a1fce3bc
|
|
Change-Id: If23cb2f799df99cab92c13e09628fc139cdedb00
|
|
Change-Id: I239849056dd88f785dce239c4d53d6c905177b64
|
|
Change-Id: I0346c98ec1e075009ac6b563119ee44178e9c773
|
|
|
|
Change-Id: Iaa0c751f101df6db25e9fca9123b81ac63033159
|
|
Change-Id: I54454fec250b74238a1c064cc2136889e1a28972
|
|
These were the last free functions that passed around a LOKDocView_Impl*
manually just because it was not possible to have them in a C++ class
when lokdocview was C code.
Change-Id: I6229a853336db0e47f7d1ba4687d198e076934a3
|
|
Change-Id: If2aff61df7efd5c291e4cc7c7196e7f6f3937b32
|
|
Primarily because I'm worried about the untyped GList.
Change-Id: I0ae6610019f6e80b0cad12086782fd89ac74943b
|
|
Change-Id: Ie1d61b35f07400c2bd1c32240c15eb908d587d59
|
|
Change-Id: Id1e14f259af68acbd29784436bb2c5062a0d6563
|
|
Change-Id: I52537a96af596db076c38dc607abe857d0771257
|
|
Change-Id: I48a6906382fd41906a06704855d2f054467c1716
|
|
Change-Id: Ibace4a943fb61e2f897c9571cc2c8814935b6e75
|
|
Change-Id: Iac5d9e97f04af92ff6f6945d691abe94a3d785b0
|
|
Change-Id: I1117ec42bdf0f2cb19f77723b87597d301d20ddb
|
|
Change-Id: I1526ab6969effa043cb7d429961aa7611e1fdd06
|
|
Change-Id: I81ce20c54bb62bec68152ca228eb222f3fd3c597
|
|
Android behavior is: if there is a graphic selection, then drag inside
the shape is a move.
lokdocivew behavior was: drag on the border of a graphic selection is a
move, but inside, it's just a pair of clicks.
Since commit 658534d36f87f9ab03d862e57b04ea268b73ccab (SdrMarkView tiled
rendering: suppress handles during text edit, 2015-03-19), we can depend
on the availability of the handles to decide if we want to move the
shape or do text editing, so do the same in lokdocview as well.
Change-Id: I2b105089e9acbbda75568622d4f2b1adecfe08f1
|
|
Change-Id: I0910afdb6a0d031cb64f545b5b2c0d16f18a0f04
|
|
It simplifies lok_docview_init() a lot and makes harder to add a
LOKDocView_Impl member without initializing it.
Change-Id: I02d91b97fecd86896c11facca98fabd6a79157e5
|
|
And move private data out of LibreOfficeKitGtk.h, so that clients are
forced to use the getter/setter functions.
Change-Id: I6565312b5ec5a8e882c3763164ff5aa81ed9720c
|
|
Change-Id: Iaecedd01d7e7bba90e49ddaa5f36859d9218242d
|
|
It's not necessary since the normal widget renders normal 256x256px
tiles, not just a single huge one.
Change-Id: Ia1c6a6c8692769093232d66aa63fde096390a7b2
|
|
This order seems to be less confusing.
Change-Id: I95a7e3e2f6244915c820bb86e67745a777714e2d
|
|
Change-Id: I166b4b713c2ea52c62c52045bb2073b6d84c1547
|
|
Fixes the crash on startup.
Change-Id: I991537644dfb6a5335d08d3d03c3d25491a0c335
|
|
Change-Id: I317f8f5397bfeb9c0d6ecaaa656cb31e66eece0b
|
|
Change-Id: Id986d5408981b6ae7bf3c8c96c5226d2445a5f0d
|
|
Change-Id: Ie4e28f9315c9de2062d63c5eb5e9c7481c719cef
|
|
Previously there were two cases when the user clicked inside a graphic
selection:
1) If the click started at a handle, it was a resize.
2) Otherwise it was a move.
Change 2) by requiring a click on the border for move, and otherwise
interpreting the click as a normal one. This makes it possible to edit
shape text with a blinking cursor.
Change-Id: Ifc063790cacb3da2684f6f72eaadd86323dd3aef
|
|
While Writer uses "0" for the "minimal width" case, editeng uses 2. We
used to round up 0 to 30, do it for any value smaller than 30.
Change-Id: Ib3cc7645b55881fc51f0729163cdea5eb9ca4f0a
|
|
Implements also Bold button as an example in the gtktiledviewer.
Change-Id: I3b07d51165f28534aadbb4673f964ec10d5fc6ef
|
|
Change-Id: Ib91bfea95d957362d807a3de53b12e2fc9389fbb
|
|
Otherwise it's not possible to later move the keyboard handling code
from gtktiledviewer to lokdocview, and handling keyboard in
gtktiledviewer but mouse in lokdocview is confusing.
Change-Id: Ib036e2cbf65ffa28771a41b01c0fda2b7b895f47
|
|
Change-Id: Ib24003178bb576ff1450d674d74ef8978b350b92
|
|
Editing can start by clicking into the widget or by pressing the toggle
button on the toolbar. In the first case the widget should emit a signal,
so the the toggle button's state can be up to date.
In both toggle button <-> LOK widget direction only update the state if
it's not yet up to date to avoid infinite loops.
Change-Id: I84c9e7757cd7cde42a95f67f0cb28f9ad6984e7a
|
|
This is mainly to be in sync with Android, but this also makes blinking
text work in viewer mode.
Change-Id: Ie307cab722bae5030ca9bdfb442555a728aa33cc
|
|
Change-Id: I57a9c94ed0fb67befd226afe78a90bee9a7fb358
|
|
Not too important for now, but in case later we want to show some kind
of preview, then this will be the place to do it.
Change-Id: I531761178491f606834b4b359281122be4c8bca9
|
|
Change-Id: Ibf9d62c52edeaad4aada7960820e1bb8fa6c2c63
|
|
It's the same as resizing, except that the action starts inside the
graphic selection, but not over any handles.
Change-Id: Ie2465fc4534d2d919ccb0f316874477f02a5d103
|
|
With this, it's now possible to resize images in Writer.
Change-Id: I2f557d6a64efda54959627d21406aef85160e470
|
|
Change-Id: Ic9804857df2237507f412bc6e248e5a7e83f8803
|
|
The problem being that any lib later loaded via osl_loadModule (e.g.,
libgcc3_uno.so) would not bind to the same global (RTTI-related) symbols as
libsofficeapp.so and its dependencies (so, e.g., -fsanitize=function would
erroneously assume that bridges/source/cpp_uno/shared/component.cxx's
uno_initEnvironment is called with a different, non-matching uno_Environment
type).
Change-Id: I08b0cbc1f9eb74641eb617c46587a0a528a56c31
|
|
Remove the unnecessary ones, but make sure that e.g. the sofficeapp library is
built (which was not covered by depending on services.rdb).
Change-Id: I1adfa4aaaf60787c944d71cc289cdafba8351c1b
|