Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
transition
|
|
|
|
|
|
A reminder: Listing some source files in this Xcode project does *not*
mean that Xcode would have any deeper knowledge about them. So Xcode
(and other IDE) fans, don't get overly excited, this is *not* a start
of making an Xcode project for all of LibreOffice or anything like
that. I just add arbitrary source files to this project when I happen
to want to set a breakpoint, and can't conveniently do it by going up
the call stack until something in that particular file.
Change-Id: Iac77dff17f56ec3f2826fd887cc065160b65936e
|
|
|
|
Change-Id: I6e2075894fc9b1bda7c002728d7853e8ed5910f7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Might make it a little bit easier for new contributors.
Change-Id: If4475c1ea7f55c34971beecd7573aaaf545e7106
|
|
Change-Id: I344d64212aa1d42171f18dae7659ab7f56fecbcb
|
|
Not suitably licensed.
Change-Id: I221cccb9d2ff5b6cb5e25161b6d5bfe504acb10e
|
|
Change-Id: I400fad08c0ae7b6b34bad63693f54856867e4dac
Reviewed-on: https://gerrit.libreoffice.org/3502
Reviewed-by: David Tardon <dtardon@redhat.com>
Tested-by: David Tardon <dtardon@redhat.com>
|
|
|
|
Change-Id: I5c7d02daced542222c2cb3881fafd2d58fe7f14d
|
|
I get exactly the same kind of artefacts as in the Android app, which
I guess is good as it is at least consistent, as the implementation at
the LO layer is identical...
Change-Id: Icf0690fd2c48a133cb66de2ab7977b7088d2199e
|
|
Change-Id: Ie0a9b6e64c35a046afbb5c26c1b75bdd0d897a23
|
|
Change-Id: I737e43d35eb2ebd6aeadeb5695cb3ecc74cc4484
|
|
Now it re-orients and re-sizes the LO "frame" correctly upon rotation,
but it still starts wrongly if starting in landscape orientation.
Change-Id: I4c12a7e00d687391435a47400b6e8b4c7e49bdda
|
|
Change-Id: I94cfdc1b334539399faff29c046185bbbf698d23
|
|
Change-Id: I93102156c4713191c8ad49da9b9d2eda5be722e8
|
|
Change-Id: I191bc093def5d2965b463dcff9e1289901064ce8
|
|
Change-Id: I9833437256243c26b9ff468937ec9f975c2e898d
|
|
Don't have our View class implement the UIKeyInput protocol any
more. It won't work properly anyway. The docs say: "Only a small
subset of the available keyboards and languages are available to
classes that adopt this protocol".
Instead, use a transparent UITextView on top of our View to accept
keyboard input.
Seems to work as expected.
Change-Id: I3093ea7fbfa0ecab0dc5d0a38e5695723e8ed4ad
|
|
Only react to hide notification for now, call lo_keyboard_did_hide()
Change-Id: I2f429039d2a84269783d103ad635ff4c407c4a15
|
|
Change-Id: Ib68928d7213a7dbba830b20c882ba53c6f3deb4c
|
|
Change-Id: I9321dcf9d863cb59eee9b2a012d887a17cb1b454
|
|
Change-Id: If37b5e646562357c4c6c9ce0a3821d92bbfc07f9
|
|
Change-Id: Idac1c756faa47236e4ebc3c7400f7e4412f02a44
|
|
Change-Id: I87c74eb6e4f9aa4f06bfca00817b4d04d7d84b40
|
|
Change-Id: Id8c405e63abec3d8c1d3c5f8fb7f40ba082c9f47
|
|
Change-Id: Id0fdba93a5d3a46a79cebea8839bdfd467ef4f6f
|
|
Change-Id: I42991d7a9c9e0bd4a023739051393935efa5c29f
|
|
Moved portions from module i18npool, all of former i18nisolang1 library
that now is i18nlangtag. Included are languagetag, isolang and mslangid.
This i18nlangtag code is now even used by module comphelper, so
disentangling i18npool and making this an own module was needed to not
create circular module dependencies.
Change-Id: Ib887c3d6dde667403fd22d382310ba5f1a9b0015
|
|
Change-Id: Ib9da3de2cedf423a18819aa83fa55de77a288a72
|
|
Change-Id: I21e6affaf08322f9e9cf1554e76f935f2c3e29b3
|
|
One can set environment variables to be used when debugging an app in
Xcode, which is when it is interesting to see SAL_INFO output anyway.
(This is very different from Android, where one can't set environment
variables "before" an app starts, as apps there aren't separate
programs that would be exec'ed.)
Change-Id: I3971d1b2d1a849deac2722a90271ef2458db1643
|
|
Change-Id: I433419e1ed7bda566bb13bf14346948d131abee6
|
|
Change-Id: I0015f7d751cb0e45262774c19a120f428cb35af2
|
|
long"
This reverts commit 3aae02d02d418222b0b51748008ed5c9c1f1d3c2.
|
|
When initially calling lo_render_windows() from a redrawRect(), just
post the user event asking for a redraw of the (headless) windows, and
return without actually drawing anything to the context.
Then when the RenderWindows() callback for that user event eventually
gets called (which during startup and/or loading of a document might
be several seconds later, as there is lots of other activity going on
also as "user events"), ask the UI thread for a fresh redraw, and wait
for lo_render_windows() in that phase to signal the actual redraw of
the "headless" windows into the context.
Unfortunately this doesn't work well enough. It is not a good idea to
not draw anything in response to a drawRect() it seems. The affected
rectangle gets initialised to black. So there is now irritating
flashing. One sees an almost ready document (and the UI elements which
still are there), but then it goes away for some time before finally
re-appearding. Quite silly. So I will revert this, and I am committing
it just to keep the code for reference in git.
Change-Id: I9ee490345f093d80113c36f9e3268cab5a810dd0
|