Unix Domain Sockets are inaddressable remotely, and more efficient,
as well as allowing future SCM_CREDENTIALS / SCM_RIGHTS.
Change-Id: Ia2472260f75feb43e9022cdfa0fe005ccd489454
Because of the use of std::shared_ptr in lokit_main(), the (singleton)
lok::Office (or LibLibreOffice_Impl) object gets destroyed when
lokit_main() exits. We shouldn't keep our own copy of a raw pointer to
it around. Just call lok_init_2() to get the pointer where we need it.
We don't need to call lok_init_2() already in -[AppDelegate
application:didFinishLaunchingWithOptions:].
Updated shrinkpack to work with (relatively) new versions of npm: https://github.com/JamieMason/shrinkpack/issues/83
The new version stores the tars in the 'archived-packages' folder and not the 'node_shrinkwrap' one, that's why there are so many files in the diff.
Change-Id: Iebcadaeee0e27f831b7ff16a50819a908e7f05a6
Reviewed-on: https://gerrit.libreoffice.org/69878
Reviewed-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>
Tested-by: Samuel Mehrbrodt <Samuel.Mehrbrodt@cib.de>
If we get a 'touchend' immediately after a 'touchstart', simulate a
'mousedown' immediately followed by a 'mouseup'.
Change-Id: Ib20eae4cc23518e34a1d948f8e498f50046f72d7
It is the combobox contents you are dragging with the gesture, so it
should move in the same direction, not opposite.
(If you would be draging the scrollbar's "thumb", then the contents of
the combobox would indeed move in the other direction. But on a touch
device, it definitely is the contents that the user is dragging.)
Change-Id: I9dc9e3cc7e3a1412176fd1d84c5587c86410d191
After zooming scrollbar was updated and scroll
position was incorrect what caused first pages
not accessible.
Regression was introduced by:
ffd7151443
Second problem was jumping to the cursor
during zooming. Solution was to not update
the cursors on zooming start.
Change-Id: I0891799b03ed4eccb211ee43eb30e546317a90fc
Reviewed-on: https://gerrit.libreoffice.org/69606
Reviewed-by: Szymon Kłos <szymon.klos@collabora.com>
Tested-by: Szymon Kłos <szymon.klos@collabora.com>
(cherry picked from commit f496c1e9c588b382fbdb10ae90a0cd85390274e8)
Reviewed-on: https://gerrit.libreoffice.org/69748
Always pass firstTouchPosition{X,Y} instead of current X,Y
position to _postWindowGestureEvent so that panning is continued
even when you go out of widget (combobox) bounds.
Change-Id: I769b013f933881d8d1294ffd094e1cf7871cb701
Pan gesture should work for comboboxes, for which panning is
implemented in core.
Change-Id: I0a7e49e9335159a302716f666e2334a9d532c115
Reviewed-on: https://gerrit.libreoffice.org/69720
Reviewed-by: Tomaž Vajngerl <quikee@gmail.com>
Tested-by: Tomaž Vajngerl <quikee@gmail.com>
(What we cache is also the textual data: URLs even if we store them
using .png file names.)
This avoids the current back-and-forth-encoding: First we
base64-encode the complete binary "tile:" message (one text line
followed by a newline and the binary PNG) to pass to WebKit, then in
the JavaScript snippet passed to WebKit we decode the base64 and turn
it into an ArrayBuffer, and then we unpack the ArrayBuffer and encode
the PNG part to use as a data: URL.
Also, make loleaflet.html depend also on the two files that are inserted into
it with the m4 syscmd thing, bundle.css and global.js.
Change-Id: Iba261aeff70786eec114e5508b748dadd8663038
It was causing the code to connect to a real socket instead of the
FakeWebSocket.
Change-Id: I0d08277e7138317ac06a13022eaba7ec672e0429
Reviewed-on: https://gerrit.libreoffice.org/69500
Reviewed-by: Jan Holesovsky <kendy@collabora.com>
Tested-by: Jan Holesovsky <kendy@collabora.com>
We don't want to unload the document and show any "Idle document -
please click to reload and resume editing" overlay.
What the iOS (and presumably Android) app *would* need, though, is
proper restore functionality. I.e. if you have a document open, and
the app is put in the background (i.e. the user does something else),
and the OS kills it (as is perfectly normal for iOS or Android to do
to idle background apps), then when the user returs to the app, it
should reopen the same document and restore the view location and zoom
level.
Sure, I would have preferred to fix the actual bug instead, but that
was much harder. See bug report for some notes about what I tried.
Now done for iOS app only (window.ThisIsTheiOSApp), probably should be
done for any mobile app (window.ThisIsAMobileApp).
