Open Office Writer UTTER , UTTER Rubbish
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 fundamental function Even when installing 4.1.2 it says its selected , however NO, it just doesn't work.. I will be pulling my donations and putting money into Microsoft, where things DO work!! albeit I will have to pay.
Re: Open Office Writer UTTER , UTTER Rubbish (or not)
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 way. (and I've been a computer user for 28 years and I can't count how many times I've seen users blaming the software for their own mistake when something didn't work as desired) Max Am 13.03.2016 um 14:14 schrieb Darren Myers: 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 fundamental function Even when installing 4.1.2 it says its selected , however NO, it just doesn't work.. I will be pulling my donations and putting money into Microsoft, where things DO work!! albeit I will have to pay. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Open Office Writer UTTER , UTTER Rubbish
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! > > Seriously I ask you this, what IDIOT created a doc writer without the most > fundamental function > > Even when installing 4.1.2 it says its selected , however NO, it just doesn't > work.. > > I will be pulling my donations and putting money into Microsoft, where things > DO work!! albeit I will have to pay. > If you set it up correctly you would find that spellcheck works. If you are interested in getting spellcheck to work, this method cures most problems with an inactive spellcheck. Delete or rename your OpenOffice user profile. As you are using Windows do this by: Close OpenOffice and the Quickstarter. Open File Explorer. Copy and paste %appdata%\OpenOffice\4 in the File Explorer Address Bar (not the search engine) and press Enter. Delete or Rename the "user" folder. Start OpenOffice. This cures most spellcheck problems. If it's not working, the document language settings may need to be changed. OO must have access to a spelling dictionary for the language as specified in the document settings (look in the status bar below the main text area). This tutorial takes you through all that step by step: https://forum.openoffice.org/en/forum/viewtopic.php?f=74&t=16512 If you wish to migrate to MS Word that is your decision. -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: Open Office Writer UTTER , UTTER Rubbish (or not)
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 for users in 4.1.1 and still in 4.1.2 However it really doesn't matter now, I simply opened my MS doc up online and MICROSOFT! allows you to edit and SPELL CHECK. Lets be honest and truthful here, Open office is inferior, and by all accounts the worst freeware I have ever installed or used. > Subject: Re: Open Office Writer UTTER , UTTER Rubbish (or not) > To: dev@openoffice.apache.org; us...@openoffice.apache.org; > myers_dar...@hotmail.com > From: max.merb...@gmx.de > Date: Sun, 13 Mar 2016 14:27:50 +0100 > > 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 way. (and I've been a computer user for 28 years and I can't count > how many times I've seen users blaming the software for their own > mistake when something didn't work as desired) > > Max > > > > Am 13.03.2016 um 14:14 schrieb Darren Myers: > > 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 > > fundamental function > > > > Even when installing 4.1.2 it says its selected , however NO, it just > > doesn't work.. > > > > I will be pulling my donations and putting money into Microsoft, where > > things DO work!! albeit I will have to pay. > > >
Re: Open Office Writer UTTER , UTTER Rubbish (or not)
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't tell me you haven't got 10 seconds to spare! And: You DO NOT need to re-create the profile because it's done automatically when you re-start OpenOffice after you deleted or renamed the old user profile. You know, most people DO try to solve problems with their software (and usually succeed) instead of periodically insulting the developers for, as you allege, "inferior" software. You did this in 2014, you did it again in 2015, and you are doing it once again right now in 2016. I wonder about your actual purpose. Anyway, no one is forcing you to use OpenOffice. Max Am 13.03.2016 um 14:40 schrieb Darren Myers: 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 for users in 4.1.1 and still in 4.1.2 However it really doesn't matter now, I simply opened my MS doc up online and MICROSOFT! allows you to edit and SPELL CHECK. Lets be honest and truthful here, Open office is inferior, and by all accounts the worst freeware I have ever installed or used. Subject: Re: Open Office Writer UTTER , UTTER Rubbish (or not) To: dev@openoffice.apache.org; us...@openoffice.apache.org; myers_dar...@hotmail.com From: max.merb...@gmx.de Date: Sun, 13 Mar 2016 14:27:50 +0100 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 way. (and I've been a computer user for 28 years and I can't count how many times I've seen users blaming the software for their own mistake when something didn't work as desired) Max Am 13.03.2016 um 14:14 schrieb Darren Myers: 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 fundamental function Even when installing 4.1.2 it says its selected , however NO, it just doesn't work.. I will be pulling my donations and putting money into Microsoft, where things DO work!! albeit I will have to pay. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Restore the website logo
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 restore the logo in a set timeframe. Done. And yes, keeping a variant online for 2 weeks seems reasonable, but no more than that. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Build without tests?
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 done during "build --all", so that I can build while I am away from the computer and test while I'm there to respond to any dialogs. Patricia - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Build without doing any tests?
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/wiki/Non_Product_Build - in brief Alt+Shift+Ctrl+D, set "Error" to something other than "MessageBox", "OK", exit AOO, back up the .dbgsv.ini somewhere, and from then on start AOO with the environment variable DBGSV_INIT set to the path of that .dbgsv.ini you backed up. On Sun, Mar 13, 2016 at 4:57 PM, Patricia Shanahan wrote: > 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 done > during "build --all", so that I can build while I am away from the computer > and test while I'm there to respond to any dialogs. > > Patricia - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Build without doing any tests?
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 describing all the AOO configure parameters? If so, I should read it. Thanks, Patricia On 3/13/2016 9:11 AM, Damjan Jovanovic wrote: 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/wiki/Non_Product_Build - in brief Alt+Shift+Ctrl+D, set "Error" to something other than "MessageBox", "OK", exit AOO, back up the .dbgsv.ini somewhere, and from then on start AOO with the environment variable DBGSV_INIT set to the path of that .dbgsv.ini you backed up. On Sun, Mar 13, 2016 at 4:57 PM, Patricia Shanahan wrote: 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 done during "build --all", so that I can build while I am away from the computer and test while I'm there to respond to any dialogs. Patricia - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Build without doing any tests?
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 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 describing all the AOO configure parameters? If > so, I should read it. > > Thanks, > > Patricia > > > On 3/13/2016 9:11 AM, Damjan Jovanovic wrote: >> >> 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/wiki/Non_Product_Build - in brief >> Alt+Shift+Ctrl+D, set "Error" to something other than "MessageBox", >> "OK", exit AOO, back up the .dbgsv.ini somewhere, and from then on >> start AOO with the environment variable DBGSV_INIT set to the path of >> that .dbgsv.ini you backed up. >> >> On Sun, Mar 13, 2016 at 4:57 PM, Patricia Shanahan wrote: >>> >>> 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 done >>> during "build --all", so that I can build while I am away from the >>> computer >>> and test while I'm there to respond to any dialogs. >>> >>> Patricia >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Build without doing any tests?
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. "./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 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 describing all the AOO configure parameters? If so, I should read it. Thanks, Patricia On 3/13/2016 9:11 AM, Damjan Jovanovic wrote: 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/wiki/Non_Product_Build - in brief Alt+Shift+Ctrl+D, set "Error" to something other than "MessageBox", "OK", exit AOO, back up the .dbgsv.ini somewhere, and from then on start AOO with the environment variable DBGSV_INIT set to the path of that .dbgsv.ini you backed up. On Sun, Mar 13, 2016 at 4:57 PM, Patricia Shanahan wrote: 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 done during "build --all", so that I can build while I am away from the computer and test while I'm there to respond to any dialogs. Patricia - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Build without doing any tests?
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:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/LinkTarget/Library/ivbaswobj.lib and object c:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/LinkTarget/Library/ivbaswobj.exp [ build CMP ] sw/util/vbaswobj [ build PKG ] sw_misc [ build PKG ] sw_uiconfig [ build PKG ] sw_xml [ build MOD ] sw [ build ALL ] top level modules: sw [ build ALL ] loaded modules: sw [ build CXX ] sw/qa/core/Test-BigPtrArray Test-BigPtrArray.cxx c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(86) : warning C4100: 'bparr' : unreferenced formal parameter c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(98) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(102) : warning C4100: 'name' : unreferenced formal parameter c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(111) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(113) : warning C4389: '!=' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(121) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(222) : warning C4389: '==' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(224) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(275) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(305) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(337) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(363) : warning C4018: '<' : signed/unsigned mismatch [ build LNK ] GoogleTest/sw_bigpointerarray.exe Microsoft (R) Incremental Linker Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. c:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/CxxObject/sw/qa/core/Test-BigPtrArray.o [ build CUT ] sw_bigpointerarray 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. "./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 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 describing all the AOO configure parameters? If so, I should read it. Thanks, Patricia On 3/13/2016 9:11 AM, Damjan Jovanovic wrote: 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/wiki/Non_Product_Build - in brief Alt+Shift+Ctrl+D, set "Error" to something other than "MessageBox", "OK", exit AOO, back up the .dbgsv.ini somewhere, and from then on start AOO with the environment variable DBGSV_INIT set to the path of that .dbgsv.ini you backed up. On Sun, Mar 13, 2016 at 4:57 PM, Patricia Shanahan wrote: 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 done during "build --all", so that I can build while I am away from the computer and test while I'm there to respond to any dialogs. Patricia - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Build without doing any tests?
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 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:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/LinkTarget/Library/ivbaswobj.lib and object c:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/LinkTarget/Library/ivbaswobj.exp [ build CMP ] sw/util/vbaswobj [ build PKG ] sw_misc [ build PKG ] sw_uiconfig [ build PKG ] sw_xml [ build MOD ] sw [ build ALL ] top level modules: sw [ build ALL ] loaded modules: sw [ build CXX ] sw/qa/core/Test-BigPtrArray Test-BigPtrArray.cxx c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(86) : warning C4100: 'bparr' : unreferenced formal parameter c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(98) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(102) : warning C4100: 'name' : unreferenced formal parameter c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(111) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(113) : warning C4389: '!=' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(121) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(222) : warning C4389: '==' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(224) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(275) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(305) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(337) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(363) : warning C4018: '<' : signed/unsigned mismatch [ build LNK ] GoogleTest/sw_bigpointerarray.exe Microsoft (R) Incremental Linker Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. c:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/CxxObject/sw/qa/core/Test-BigPtrArray.o [ build CUT ] sw_bigpointerarray 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. "./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 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 describing all the AOO configure parameters? If so, I should read it. Thanks, Patricia On 3/13/2016 9:11 AM, Damjan Jovanovic wrote: 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/wiki/Non_Product_Build - in brief Alt+Shift+Ctrl+D, set "Error" to something other than "MessageBox", "OK", exit AOO, back up the .dbgsv.ini somewhere, and from then on start AOO with the environment variable DBGSV_INIT set to the path of that .dbgsv.ini you backed up. On Sun, Mar 13, 2016 at 4:57 PM, Patricia Shanahan wrote: 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 done during "build --all", so that I can build while I am away from the computer and test while I'm there to respond to any dialogs. Patricia - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional co
Re: Open Office Writer UTTER , UTTER Rubbish (or not)
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 are available. Patches welcome! Regards, Dave Sent from my iPhone > On Mar 13, 2016, at 6:40 AM, Darren Myers wrote: > > 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 for users in > 4.1.1 and still in 4.1.2 > > However it really doesn't matter now, I simply opened my MS doc up online and > MICROSOFT! allows you to edit and SPELL CHECK. > Lets be honest and truthful here, Open office is inferior, and by all > accounts the worst freeware I have ever installed or used. > > > >> Subject: Re: Open Office Writer UTTER , UTTER Rubbish (or not) >> To: dev@openoffice.apache.org; us...@openoffice.apache.org; >> myers_dar...@hotmail.com >> From: max.merb...@gmx.de >> Date: Sun, 13 Mar 2016 14:27:50 +0100 >> >> 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 way. (and I've been a computer user for 28 years and I can't count >> how many times I've seen users blaming the software for their own >> mistake when something didn't work as desired) >> >> Max >> >> >> >>> Am 13.03.2016 um 14:14 schrieb Darren Myers: >>> 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 >>> fundamental function >>> >>> Even when installing 4.1.2 it says its selected , however NO, it just >>> doesn't work.. >>> >>> I will be pulling my donations and putting money into Microsoft, where >>> things DO work!! albeit I will have to pay. > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Build without doing any tests?
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 like when AOO is running... If that's the case, you can disable the tests for now with --disable-unit-tests, but we should really fix that somehow: OSL_ASSERT failures in compile-time unit tests should not interact with the user. On Sun, Mar 13, 2016 at 7:49 PM, Patricia Shanahan wrote: > 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 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:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/LinkTarget/Library/ivbaswobj.lib >> and object >> >> c:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/LinkTarget/Library/ivbaswobj.exp >> >> [ build CMP ] sw/util/vbaswobj >> [ build PKG ] sw_misc >> [ build PKG ] sw_uiconfig >> [ build PKG ] sw_xml >> [ build MOD ] sw >> [ build ALL ] top level modules: sw >> [ build ALL ] loaded modules: sw >> [ build CXX ] sw/qa/core/Test-BigPtrArray >> Test-BigPtrArray.cxx >> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(86) : >> warning C4100: 'bparr' : unreferenced formal parameter >> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(98) : >> warning C4018: '<' : signed/unsigned mismatch >> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(102) : >> warning C4100: 'name' : unreferenced formal parameter >> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(111) : >> warning C4018: '<' : signed/unsigned mismatch >> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(113) : >> warning C4389: '!=' : signed/unsigned mismatch >> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(121) : >> warning C4018: '<' : signed/unsigned mismatch >> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(222) : >> warning C4389: '==' : signed/unsigned mismatch >> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(224) : >> warning C4018: '<' : signed/unsigned mismatch >> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(275) : >> warning C4018: '<' : signed/unsigned mismatch >> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(305) : >> warning C4018: '<' : signed/unsigned mismatch >> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(337) : >> warning C4018: '<' : signed/unsigned mismatch >> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(363) : >> warning C4018: '<' : signed/unsigned mismatch >> [ build LNK ] GoogleTest/sw_bigpointerarray.exe >> Microsoft (R) Incremental Linker Version 9.00.30729.01 >> Copyright (C) Microsoft Corporation. All rights reserved. >> >> >> c:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/CxxObject/sw/qa/core/Test-BigPtrArray.o >> >> [ build CUT ] sw_bigpointerarray >> >> >> 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. >>> >>> "./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 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 describing all the AOO configure parameters? If so, I should read it. Thanks, Patricia On 3/13/2016 9:11 AM, Damjan Jovanovic wrote: > > > 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/wiki/Non_Product_Build - in brief > Alt+Shift+Ctrl+D, set "Error" to something other than "MessageBox", > "OK", exit AOO, back up the .dbgsv.ini somewhere, and from then on > start AOO with the environment variable DBGSV_INIT set to the path of > that .dbgsv.ini you backed up. > > On Sun, Mar 13, 2016 at 4:57 PM, Patricia Shanahan > wrote: >> >> >> I
Re: Build without doing any tests?
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 on sorting out the assertions, so that they only fail if there is something wrong. On 3/13/2016 11:16 AM, Damjan Jovanovic wrote: 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 like when AOO is running... If that's the case, you can disable the tests for now with --disable-unit-tests, but we should really fix that somehow: OSL_ASSERT failures in compile-time unit tests should not interact with the user. On Sun, Mar 13, 2016 at 7:49 PM, Patricia Shanahan wrote: 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 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:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/LinkTarget/Library/ivbaswobj.lib and object c:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/LinkTarget/Library/ivbaswobj.exp [ build CMP ] sw/util/vbaswobj [ build PKG ] sw_misc [ build PKG ] sw_uiconfig [ build PKG ] sw_xml [ build MOD ] sw [ build ALL ] top level modules: sw [ build ALL ] loaded modules: sw [ build CXX ] sw/qa/core/Test-BigPtrArray Test-BigPtrArray.cxx c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(86) : warning C4100: 'bparr' : unreferenced formal parameter c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(98) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(102) : warning C4100: 'name' : unreferenced formal parameter c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(111) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(113) : warning C4389: '!=' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(121) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(222) : warning C4389: '==' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(224) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(275) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(305) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(337) : warning C4018: '<' : signed/unsigned mismatch c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(363) : warning C4018: '<' : signed/unsigned mismatch [ build LNK ] GoogleTest/sw_bigpointerarray.exe Microsoft (R) Incremental Linker Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. c:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/CxxObject/sw/qa/core/Test-BigPtrArray.o [ build CUT ] sw_bigpointerarray 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. "./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 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 describing all the AOO configure parameters? If so, I should read it. Thanks, Patricia On 3/13/2016 9:11 AM, Damjan Jovanovic wrote: 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/wiki/Non_Product_Build - in brief Alt+Shift+Ctrl+D, set "Error" to something other than "MessageBox", "OK", exit AOO, back up the .dbgsv.ini somewhere, and from then on start AOO with the environment variable DBGSV_INIT set to the path of that .dbgsv.ini you backed up. On Sun, Mar 13, 2016
[DISCUSS] Release Groovy UNO Extension via Maven
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 the Apache Nexus staging area [1]. I attached a test script HelloTextTableShape.groovy to this issue in bugzilla [2] that will test the working of the guno-extension. The test script is a Groovy version of HelloTextTableShape.java that is included in the SDK examples from the Developer Guide. The script will run as a client application and bootstrap the office using the previously released bootstrap-connector and Java UNO jars from Maven. The test script will pull down the guno-extension from the Nexus staging area and get the other dependencies from Maven. Prerequisite: If you had earlier tested the bootstrap-connector.jar by placing it in ~/.groovy/lib or added the Java UNO jar files there, you need to remove them first. You need Groovy to run the script. In HelloTextTableShape.groovy, edit value for oooExeFolder to match the path to the soffice executable if needed. It's near the top. Run with: > groovy HelloTextTableShape.groovy To build from source: You can get the complete guno-extension source including the Gradle build script from our SVN here [3]. You will need Gradle and Groovy to build with: > gradle jar There are additional gradle tasks for building and pgp signing a complete release included also. More info on guno-extension here [4]. [1] https://repository.apache.org/content/repositories/orgapacheopenoffice-1016/org/openoffice/guno-extension/0.1.4/ [2] https://bz.apache.org/ooo/show_bug.cgi?id=126770 [3] https://svn.apache.org/repos/asf/openoffice/devtools/guno-extension/trunk/ [4] https://wiki.openoffice.org/wiki/Groovy_UNO_Extension Please let me know if you have any questions. Thanks, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
