use solenv/bin/add-modulelines script for the task
and remove all UTF bom from *.src and *.hrc files
svx/source/dialog/hdft.src
Change-Id: I745d4f0fe9b05436a142a03f8512970f91c41bd4
The Wakeup() in the base class, SvpSalInstance, is not virtual. So this
Wakeup() does not override the Wakeup() in the base class, as the author maybe
thought. I don't see in git history that it would have ever been called
explicitly on any AndroidSalInstance objects either. Or am I missing
something?
Change-Id: I932398e7c0a37a3048c5d372996fe6ac6f209887
Don't try to find the class org.libreoffice.experimental.desktop.Desktop in
the AndroidSalInstance constructor. It won't exist anyway except in that
specific app. Look up the class in the damaged() method where it is needed.
And actually, of course we should not hardcode the name of the app class like
that, but the app should pass its class down to the native code.
Change-Id: Ic15d5cc2c8d53be558711ca7a145d5489e34d298
rather than based on their names, which changes if
there are more than one dialog in a .ui
set them explicitly in the manual-build-dialog
case of the SfxTabDialogs
Change-Id: I293c77df05d9e11e3f1cf3b358a9dd27fe668b0f
Font is usable for viewing if not restricted from embedding completely
(since otherwise either viewing is allowed or a less restrictive setting
is present). Font is usable for editing if it's installable or editable.
Change-Id: I57604a54390b935bae3699dda581d1093fc245e3
MSO embeds even fonts which allow only embedding for viewing the document
but not editing it. So embed such fonts too, but do not actually use
them from the document. What MSO does when such a font is not present
locally when opening the document is switching to read-only mode,
warning about this and providing a button for switching to editing mode
by dumping the font(s). That should be done for LO too, but right now
dropping view-only fonts is better than using them for editing.
Change-Id: I19c28fadb091e6b21beaf4cbf8b47e3078256d1c
The scrolling concepts seem quite obscure and firmly tied to concepts like
"pages" and "lines". For touch devices one would want to be able to request
scrolling simply in *pixels*.
It is the scrollbar objects (in vcl and toolkit, and yes, UNO is also involved
over in toolkit) that all the action goes through so they must exist even if
they should not be displayed.
(Both on Android and iOS we should presumably use these system-specific
ephemeral scroll indicator thingies that show up only during scrolling but
otherwise fade away. Hmm, probably the VCL (or toolkit?) scrollbar code should
use platform-specific code to display those then.)
Change-Id: I1f82648561e41ae25f2427fd0fe60249c927a9a1
Change-Id: Iad623c9300919fbae34279268a5a720f978c6434
Reviewed-on: https://gerrit.libreoffice.org/2514
Reviewed-by: Joren De Cuyper <joren.libreoffice@telenet.be>
Reviewed-by: Thomas Arnhold <thomas@arnhold.org>
Tested-by: Thomas Arnhold <thomas@arnhold.org>
Don't know what this affects, though. Things seem to have worked as expected
even with the hardcoded bogus value?
Change-Id: I945bdcd53260fc5f43cf0031dfd96637168475f0
In the damaged() method do a callback up to Java code in Desktop that
invalidates the view. For now store the view in a static field, but need to do
that in a cleaner way eventually. There might in some circumstancest be
several instances of the Desktop activity present. Obviously should also run
just one LO thread.
Get rid of the temporary self-invalidattion in onDraw() silliness.
Start the LO thread that runs soffice_main() from Java, not from native
code. Apparently only threads created from Java have proper class loaders in
Android.
No need for an own DoReleaseYield() in AndroidSalInstance, the one in the
SvpSalInstance base class does what needs to be done.
Change-Id: I4cb85b352fca1f1375f726620ec8c93d2047f113
