Re: Help Locating Base Code

Thanks to both of you. I have tried the gdb method before and honestly, for
a new programmer, our directions aren't the best on the wiki. I am yet to
successfully make progress but I am going to figure it out this time around
since it seems like that's what is needed. Usually I just grep the label
for something I am search for and then backtrack from there, seeing where
it is used and how and sooner or later I find the code that I'm looking
for. In this case Lionel is right, both the "..." and the "pictures" labels
are both so generic that they are useless for tracking down the code. Also
it seems like these dialogs are a bit complex (seems like they could be
simplified but that's probably for another day ;) ). So my next question is
two fold...

1. For getting a bit more in depth instructions, is it best to ask here or
in IRC? I believe (almost positive) that my Libo is installed with symbols
enabled, so I want to try to do the gdb method but need kind of a complete
breakdown of what to do (I believe it's only a few steps).

2. If the best place to ask is here, could someone be kind enough to write
out the few steps?

Again thank you for all of your patience. I feel like I'm starting to get a
grasp on the code :)


Joel

On Wed, Aug 8, 2012 at 6:20 AM, Lionel Elie Mamane <lionel@mamane.lu> wrote:

> On Wed, Aug 08, 2012 at 02:01:28PM +0100, Michael Meeks wrote:
> > On Wed, 2012-08-08 at 07:32 +0200, Lionel Elie Mamane wrote:
> > > On Tue, Aug 07, 2012 at 06:50:22PM -0700, Joel Madero wrote:
>
> > > > I'm trying to locate the code that handles the dialog that appears
> when you
> > > > do the following steps in base:
>
> > > To answer this kind of questions, I find it useful to run a build with
> > > symbols (debug build) under gdb. Then, when the dialog is open, just
> > > press CTRL-C in gdb
>
> >       So - that is one way :-) another way is to grep for the UI strings,
> > which usually come from a .src file; so
>
> > git --no-pager grep -2 "Create Report in Design View"
>
> In general, you are right, this is a useful technique that needs less
> tooling, and I didn't think of mentioning it.
>
> In this case, however, Joel was looking for a _different_ thing than
> what you show in the example. He wanted to see what creates the dialog
> titled "Picture" when one presses the button labelled "...".
>
> As these are quite generic labels, in this case, the gdb technique is
> faster / more accurate, assuming you already have a build with
> symbols.
>
> --
> Lionel