Hello
Can someone please pass this comment on to the relevant incompetent developer
who created openoffice writer..
It has the a really obvious problem with the program...
IT HAS NO BLOODY SPELL CHECK!
Seriously I ask you this, what IDIOT created a doc writer without the most
fundam
Hello Darren,
of course it's got a spell check. And the spell check works. I've been
using OpenOffice for years and I never had that problem. If something on
OpenOffice doesn't work, delete the folder "OpenOffice" in
[user]/appdata/roaming and restart OpenOffice. No need to be rude, by
the wa
On Sun, 13 Mar 2016 13:14:43 +
Darren Myers wrote:
> Hello
>
> Can someone please pass this comment on to the relevant incompetent developer
> who created openoffice writer..
>
> It has the a really obvious problem with the program...
>
> IT HAS NO BLOODY SPELL CHECK!
>
> Serio
Max
I am a developer in BMC / People soft applications, 32 years and 4 months
overall experience..
I shouldn't have to delete a profile and re-create it and go through that pain
in order to get the most basic function working.
Open office need to fix this MAJOR problem. It was an issue fo
Darren,
even a software developer (which you claim to be) may occasionally have
to repair a software installation, and that can happen with MS products
too. not just with OpenOffice. Deleting the Openoffice folder in AppData
doesn't take long and isn't a pain. It's done in 10 seconds. And don'
On 12/03/2016 JZA wrote:
Hello, I want to congratulate the project for 160M download. However I
would want to discuss how long should this logo be up there.
I agree. The change was done long ago, and we are maybe (I didn't check)
closer to 200M than to 160M now...
I also think we should re
I am currently building a debug version of AOO, including using
--enable-dbgutil. I lost a few hours overnight because it did a test
that triggered an assertion dialog, and waited for me to wake up and
click "No" to continue.
I would prefer to separate building and the tests that are normally
I am not sure which tests you are talking about and at what stage of
the build process they occur. The Google Test unit tests don't bring
up dialogs AFAIK, but can be disabled by passing --disable-unit-tests
to ./configure. If this happens after starting AOO then see
https://wiki.openoffice.org/wik
I also have no idea which tests - I just know I was greeted this morning
by an incomplete build and the form of AOO dialog I only see from a
debug build. The build resumed as soon as I answered the dialog.
I'll try --disable-unit-tests next time I start a build.
Is there a general document des
It is highly unusual to get a dialog during build. Please send a
screenshot next time.
"./configure --help" is probably the best - I couldn't find anything
better so far.
On Sun, Mar 13, 2016 at 6:19 PM, Patricia Shanahan wrote:
> I also have no idea which tests - I just know I was greeted this
Will do. It will help if I am fully awake when dealing with it, not
first thing on daylight savings time morning. I need to do an svn-update
and rebuild soon.
On 3/13/2016 10:01 AM, Damjan Jovanovic wrote:
It is highly unusual to get a dialog during build. Please send a
screenshot next time.
Hi Damjan,
I got another one. This is a cygwin build on Windows 8.1.
I'll leave it alone for a bit in case there is more information I should
capture. It may be possible to attach a debugger to the process.
Here are the last few lines from the build output:
Creating library
c:/OpenOffice
It looks as though the attached .pdf image did not get through. Here is
the data from it:
The error was in main/sal/osl/w32/process.cxx, line 340, null message.
The assertion is "OSL_ASSERT(g_command_args.m_nCount > 0);"
On 3/13/2016 10:44 AM, Patricia Shanahan wrote:
Hi Damjan,
I got anoth
Darren,
OpenOffice has a long, long history. Not as long as you or me or many others
here have been programming. I think you might be surprised at the number of
decades of some of the generous contributors to AOO.
If you have the relevant C++ experience, the source code and build instructions
If it's OSL_ASSERT, it's probably the non product build story, though
I am not sure why that's bringing up dialogs at compile time. Maybe
the Google Tests are working too well: they initialize sal, so
failures in OSL_ASSERT (as opposed to in the Google Test APIs) could
be bringing up dialogs just l
Taking it a stage further, I would like to have assert options for
attended and unattended operation, with builds defaulting to unattended.
It can be useful to run regression tests with assertions enabled, but
logging assertion failures rather than displaying a dialog.
Obviously, that depends
Hi All,
Prior to calling for a release vote I wanted put this information out
here hoping a few people will try the test script and make sure it works
for them and see if there are questions or concerns first.
I have created a Maven bundle including source and javadoc jars and
uploaded it to
17 matches
Mail list logo
