On 3/11/2016 4:19 PM, Larry Gusaas <larry.gusaas@gmail.com> wrote:
On 3/11/2016 4:19 PM, Larry Gusaas <larry.gusaas@gmail.com> wrote:
No. It is a LibreOffice bug. You broke the usability of LibreOffice
on Macs with your code change.
*I* broke it? Sorry Larry I'm just a user like you.
It worked before.
Past performance is no guarantee of future performance.
Libreoffice *fixed* a bug that brought to light a Mac bug.
Deal with it.
It isn't Libreoffice's responsibility to 'work around' everyone else's
bugs.
Any new user of LibreOffice on Macs will find out the database
doesn't work.
No - they will find that a *few* features/functions won't work.
The reality is *most* will never know it.
It is not Apples's responsibility to make your software usable
There is a *bug* in Apple's provided JRE package that has been there for
a very long time.
The Libreoffice devs finally decided to make a change to their code that
stops 'working around' Apple's long standing bug (at least thats how I
read the comments)...
There is a simple workaround that *you* can employ - install the JDK -
until Apple fixes *their* JRE package bug.
Enjoy...
--
To unsubscribe e-mail to: discuss+unsubscribe@documentfoundation.org
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be
deleted
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.