public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Mike_D_Davies@fmo.com
To: sourcenav@sourceware.cygnus.com
Subject: Alt keys and local variables problems
Date: Tue, 17 Jul 2001 01:08:00 -0000	[thread overview]
Message-ID: <85256A8C.002C6712.00@sfldmint11.na.fmo.com> (raw)

Hi,

I didn't get a response to the question I posted earlier  so I've appended it to
this.  My new question/problem is that the ALT-key shortcuts don't seem to bring
down the menus (SN5 / Windows).  The shortcuts for the tabbed pane (eg ALT-c for
the class pane,  ALT-v for the retriever) seem to work fine though.  Is this a
known bug ?  Also does anyone have any ideas where I should start to look to fix
this ?   I am a bit stymied when it comes to bug fixing since I don't have
access to VC++ 5 or 6 at work - has anyone tried to use the Borland compiler to
build SourceNav ? (I think this is available as a free download for
non-commercial use).  If not then what changes would I need to make to the build
system to get that to work ?


Thanks for any advice,  sorry about all the questions,

Mike


_previous_question_starts_

Hi,

I am running SN 5 under Windows and I have tried to enable "Generate references
to local variables" in the project preferences/xref tab but I still cannot
generate an xref for a local variable.

I have generated a simple project based on the single c++ file below and I can
only see an xref for the variable x,  not the variable y.  I have tried saving
local variable parsing enabled as the default and re-running the project build
but that does not help.

Is this a bug or am I missing something ?

Thanks,

Mike


#include <iostream>

int action();

int x = 0;

int main()
{
     int retval = action();

     int y = 3;

     return 0;
}



int action()
{
     cout << "hello world  !";

     return 0;
}

_previous_question_ends_


                 reply	other threads:[~2001-07-17  1:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85256A8C.002C6712.00@sfldmint11.na.fmo.com \
    --to=mike_d_davies@fmo.com \
    --cc=sourcenav@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).