Re: [dev] Re: operator delete mismatch

2010-04-10 Thread Terrence Enger
On Fri, 2010-04-09 at 21:19 +0200, Björn Michaelsen wrote:
 Am Fri, 09 Apr 2010 15:12:00 -0400
 schrieb Terrence Enger ten...@iseries-guru.com:
 
  Is there anything that will capture a record of what I did to get into
  an interesting situation?  It has happened more than once that I
  have been trying to reproduced an assertion--but writing down the
  steps as I go along, so as to produce a good bug report--when I
  fat-finger something (but I am not sure exactly what) which sends me
  to a different assertion.
 
 This:
 
  http://wiki.services.openoffice.org/wiki/User_Experience/OpenOffice.org_User_Feedback_Program
 
 could be of some help to figure out what you fat-fingered. ;)
 However, I fear it is still a bit to high-level to be useful in
 general. But it might give you a hint on what just happened in some
 situations.
 

I have never seen the help optimize the quality ... window
presented, and my Tools  Options  OpenOffice.org lacks category
Improvement Program.  Output from configure --help does not contain
the string improve.  Is there something else I need to do to get
this?

I suspect the the testautomation project has something that would help
me.  However, I am already feeling overwhelmed by new knowledge.

Actually, I find many things that tend to spread out my attention: new
assertions, new techniques, new (to me) parts of OO.  But I think that
I will only be able to contribute usefully if I can get deeper
instead of wider, if you know what I mean.  I am in need of general
guidance.


Cheers,
Terry.



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org



[dev] Re: operator delete mismatch

2010-04-10 Thread Björn Michaelsen
Am Sat, 10 Apr 2010 14:24:49 -0400
schrieb Terrence Enger ten...@iseries-guru.com:

 On Fri, 2010-04-09 at 21:19 +0200, Björn Michaelsen wrote:
  Am Fri, 09 Apr 2010 15:12:00 -0400
  schrieb Terrence Enger ten...@iseries-guru.com:
  
   Is there anything that will capture a record of what I did to get
   into an interesting situation?  It has happened more than once
   that I have been trying to reproduced an assertion--but writing
   down the steps as I go along, so as to produce a good bug
   report--when I fat-finger something (but I am not sure exactly
   what) which sends me to a different assertion.
  
  This:
  
   http://wiki.services.openoffice.org/wiki/User_Experience/OpenOffice.org_User_Feedback_Program
  
  could be of some help to figure out what you fat-fingered. ;)
  However, I fear it is still a bit to high-level to be useful in
  general. But it might give you a hint on what just happened in some
  situations.
  
 
 I have never seen the help optimize the quality ... window
 presented, and my Tools  Options  OpenOffice.org lacks category
 Improvement Program.  Output from configure --help does not contain
 the string improve.  Is there something else I need to do to get
 this?

Oh, I am so sorry. Yes, there is something that needs to be done to
activate it. The feedback program is only activated in official sun
builds. Only there there are the files:

 ./basis3.2/share/registry/modules/org/openoffice/Office/Jobs/Jobs-oooimprovement.xcu
 ./basis3.2/share/registry/modules/org/openoffice/Office/Logging/Logging-oooimprovement.xcu

in the installation. In the source tree you will find the files at:

 ./extensions/source/oooimprovement/Jobs.xcu
 ./extensions/source/oooimprovement/Logging.xcu

Im sorry, if I caused confusion.

 Actually, I find many things that tend to spread out my attention: new
 assertions, new techniques, new (to me) parts of OO.  But I think that
 I will only be able to contribute usefully if I can get deeper
 instead of wider, if you know what I mean.  I am in need of general
 guidance.
Yes, OOo is huge and assertions take you all over the place. It might
be useful to just concentrate on set of modules (from one application)
and ignore everything else in the beginning. And even then it helps to
limit oneself to the lowhanging fruits for starters.


BR,


Bjoern



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org



Re: [dev] Re: operator delete mismatch

2010-04-09 Thread Terrence Enger
On Tue, 2010-03-30 at 15:11 +0200, Michael Stahl wrote:
 On 30/03/2010 13:31, Terrence Enger wrote:
  ( I think, though, that I am giving up on trying to use a
non-product
  build when I actually want to get work done grin /. )
 
 before resorting to such extreme measures as not using non-product
builds,
 try the debug dialog (Control-Shift-Alt-D).
 it lets you change assertion reporting from a dialog box to output on
 stderr (the option is called shell), or to a window.
 you can also increase your level of annoyance by enabling warnings
as
 well  :)

Ah, yes that debug dialog.  I tried a non-product build with the
intention of learning about that dialog.  But before getting there, I
got caught up in the assertions, and I have yet to get out of the
trap.

Is there anything that will capture a record of what I did to get into
an interesting situation?  It has happened more than once that I
have been trying to reproduced an assertion--but writing down the
steps as I go along, so as to produce a good bug report--when I
fat-finger something (but I am not sure exactly what) which sends me
to a different assertion.

Speaking of bug reports ... I have been attaching a backtrace captured
while the Debug Output window is open.  And I do that with debugging
symbols loaded (which *really* loads down my poor little computer).
Are these helpful things to do?  Does a backtrace compensate for
skimpiness in the steps to reproduce?

Thanks,
Terry.

 
 regards,
  michael
 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org



[dev] Re: operator delete mismatch

2010-04-09 Thread Björn Michaelsen
Am Fri, 09 Apr 2010 15:12:00 -0400
schrieb Terrence Enger ten...@iseries-guru.com:

 Is there anything that will capture a record of what I did to get into
 an interesting situation?  It has happened more than once that I
 have been trying to reproduced an assertion--but writing down the
 steps as I go along, so as to produce a good bug report--when I
 fat-finger something (but I am not sure exactly what) which sends me
 to a different assertion.

This:

 http://wiki.services.openoffice.org/wiki/User_Experience/OpenOffice.org_User_Feedback_Program

could be of some help to figure out what you fat-fingered. ;)
However, I fear it is still a bit to high-level to be useful in
general. But it might give you a hint on what just happened in some
situations.

Best Regards,

Bjoern


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org



[dev] Re: operator delete mismatch

2010-03-30 Thread Michael Stahl
On 30/03/2010 13:31, Terrence Enger wrote:
 ( I think, though, that I am giving up on trying to use a non-product
 build when I actually want to get work done grin /. )

before resorting to such extreme measures as not using non-product builds,
try the debug dialog (Control-Shift-Alt-D).
it lets you change assertion reporting from a dialog box to output on
stderr (the option is called shell), or to a window.
you can also increase your level of annoyance by enabling warnings as
well  :)

regards,
 michael

-- 
Although many software patents have unfortunately already been granted
 in the past, I hope that this practice will not continue in future.
 If Europe leads the way in this, I expect many Americans would want to
 emigrate so that they could continue to innovate in peace.
 -- Donald E Knuth


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org