Date: prev next · Thread: first prev next last
October 2019 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=126117

--- Comment #5 from Doug <doug@dougscountry.com> ---
I don't quite understand why certain functions are not universally available 
across all the modules. 

Spell Check, Auto Complete, et.....
With the same abilities in each module.
If I can delete a bad complete entry in Writer, I should be able to do it in
Calc too.

Generalized code libraries of these functions could solve the issue.

and no, I have not looked at the source code to see the overall design.
But as a user, it seems like each module has been created and coded
independently with no common ground.

The same would apply for the common general functions like print, sort,
Query, et.....

I started this thread because I had no way to delete bad entries in the Calc
Quick Entry.  I am dyslexic do I have things I need to fix. OFTEN.

On a side note: Until it is possible to import all Microsoft file types
into this product, it will  never become a 100% alternative.

I don't want to work in the Microsoft cloud. So I want to be able to import my
Access .MDB databases and move forward. Instead of having to try to get Access
2000 to work with Windows 10. Which I did achieve after several hiccups. 

Is Libre going to become Great? Or will it just remain slightly better than
Open Office.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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.