Hello Eike,
Thanks for reviewing my patch.
Eike Rathke-2 wrote
* For TextToColumn some fields are preset and not changeable and
configuration does not provide properties, do not attempt to access
non-existing properties. In fact unotools/source/config/configmgr.cxx
mocks about these cases if built with debug.
OK
Eike Rathke-2 wrote
* Do not use RTL_CONSTASCII_USTRINGPARAM with new code, OUString knows
about ASCII literals.
Actually, I'm quite lost with all types of string. Where can I get tuto
about string, String, OUString, UString, etc.?
Eike Rathke-2 wrote
* Converted an if(meCall==...){}if(meCall==...) to a switch case.
I noticed that caption of Dlg is missing filename in case of File Import.
Patch enclosed correct this.
http://nabble.documentfoundation.org/file/n4002172/0001-fdo-47674-Save-setting-for-Import-Ascii-Text-Dlg.patch
0001-fdo-47674-Save-setting-for-Import-Ascii-Text-Dlg.patch
Eike Rathke-2 wrote
* Sensible indentation, please ;-)
I'm new with Linux and not comfortable with vim. I'm coming from MS-Windows.
I learned C at school in late 80's, then TurboC, Borland C++ and C++ Builder
by myself. So I have still a lot to learned :)
I promise to improve my coding ;)
Sincerely
Laurent BP
-----
LibreOffice 3.5.5
--
View this message in context:
http://nabble.documentfoundation.org/PATCH-fdo-47674-Calc-save-settings-for-import-ascii-text-dialog-tp4000438p4002172.html
Sent from the Dev mailing list archive at Nabble.com.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.