[comp.sys.mac] MacApp Browser

ranson@crcge1.UUCP (D. Ranson CNET) (03/16/88)

I am having difficulties using the MacApp Browser distributed by the MacApp
Developpers Association. I have parsed successfully all the source files of
MacApp v1.1.1, but the browser is unable to find the source code for most of
the methods (especially those in UMacApp). Other units, e.g. UObject or
UList, give correct results. Am I missing something, such as a specific
order to parse the files?

A totally unrelated question: what is the status of the new Mac newsgroups
(programmer, hypercard)? The news sites I have access to in Europe have not
received the creation messages. Are these groups "US only"?

    Daniel Ranson
    ...!mcvax!inria!cnetlu!ranson

dtw@F.GP.CS.CMU.EDU (Duane Williams) (03/19/88)

Re:
| I am having difficulties using the MacApp Browser ...
| the browser is unable to find the source code for most of the methods
| (especially those in UMacApp). Other units, e.g. UObject or UList, give
| correct results.

I presume that you mean that the Browser is finding the source files, but
not accurately locating the methods.  This will happen if you edit the
source files after you run the Parser, which seems to just save the offset
for each of the methods.  Each time you edit one of the source files you
have to reparse it.  You should select the names of the files that need
reparsing, select the reparse menu item (which marks the files for
reparsing), and then select the parse files menu item.

(You really shouldn't be editing UMacApp at all, if that's what you're
doing.)
-- 
uucp: ...!seismo!cmucspt!me.ri.cmu.edu!dtw
arpa: dtw@cs.cmu.edu

ws0n+@andrew.cmu.edu (Walter Ray Smith) (03/24/88)

| I am having difficulties using the MacApp Browser ...
| the browser is unable to find the source code for most of the methods
| (especially those in UMacApp). Other units, e.g. UObject or UList, give
| correct results.

Do you mean it gets the method names, but when you click on them the window
just blanks out?  I had this problem a while back.  If I remember correctly,
the solution is to run the Parser without MultiFinder.

- Walt