× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks Steven, Adam, Dave and anyone else who responds. I know have
different ways in which to accomplish what I want and I can try each and
find which I find easiest.

Rob

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Adam Glauser
Sent: November 29, 2007 11:05 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] WDSCi vs SEU F15=Browse options

Robert Rogerson wrote:
When using SEU to read code many times I would have the screen split with
two version of the source open. When I came to an Exsr I would switch to
my
second view to see the code for the subroutine. When finished I would
switch back to the original member which was still positioned at the Exsr
statement.

I'm wondering how others do this in WDSCi

Steven's suggestion works well, but just for the sake of interest there
is also a way to do something similar without splitting the view.

1. On (or near) the EXSR line, hit Ctrl+Q to make a quickmark.
2. Click the subroutine name in the outline view to get to the BEGSR line.
3. Read through the subroutine.
4. Hit Alt+Q to go back to your quickmarked location.

I use both methods in practise, depending on whether I need to see the
EXSR context while reading the subroutine contents.

HTH,
Adam

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.