HDTenEightyP/NetNews huggingface dataset:
From: D6431@AppleLink.Apple.COM (OptImage Interactive Svcs,PRT)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Resources and XCMDs in MacApp
Date: 18 Dec 92 17:22:00 GMT
Organization: AppleLink Gateway

Help, I need help with a MacApp Problem:
 
Earlier this year I developed a series of XCMDs for Hypercard that did digital
audio conversions, ie sample rate converters and so forth.  We built a
Hypercard stack as a front end and shipped the product.  Now I'm developing an
application in MacApp that launches these XCMDs as well as a few others.
Moving these XCMDs to MacApp wasn't entirely painless, but I have eventually
gotton all of them to work exept one.  This particular XCMD consists of posing
a Custom SFGetFile dialog, very similar to the one in THINK C 5.0 that lets the
user "Get" multiple files in one "Get".  Keep in mind this XCMD works
beautifully in Hypercard.  From my MacApp application however it launches fine
the first time it is fired off, but if you fire it off again within the same
run of the application it causes a bus error in "MDEF + 014". The Custom
SFGetFile dialog my XCMD poses does have a pop-up menu in it the allows the
user to filter the type of files they are looking at.  The DITL for the
SFGetFile has a control for the Pop-up.  I have used both a Public domain
Pop-up CDEF and Apple's System 7 Pop-up CDEF and got the same problem.  On
entry to the XCMD the cntl resource associates an empty menu resources of ID
128 with the CDEF.  On exit, I call release resource on the MenuHandle, because
the next time the XCMD is launched I might put different Items into the Pop-up
menu.  Again this works fine in hypercard.  What is MacApp doing to what seems
to be my resources during execution of my app that hypercard wasn't doing???
I've tried many senarios of the above trying to isolate the problem, but have
had no luck.  Any help would be most appreciated.
 
Jay Bartot @Optimage interactive services
From: D5087@AppleLink.Apple.COM (KR Software, Ken Ryall,PAS)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: Hiding the Menubar?
Date: 12 Dec 92 16:26:00 GMT
Organization: AppleLink Gateway

On the latest developer CD there is a snippet called "HideMenuBar" that has
example code for this. It's short and easy and should do what you need.
 
Ken Ryall
From: D4887@AppleLink.Apple.COM (Advanced Comm Eng, G G Apple,PRT)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: Stack size in MacApp
Date: 16 Dec 92 00:42:00 GMT
Organization: AppleLink Gateway


 
----------------------------------------------------------------------------
>I need a Large stack in my MacApp Application.  Is there any way I can
>increase my stack size on application start up??
 
    This is set in Memory.r.  Or, if you are careful, after looking at Memory.r
you could probably change Mem! with ResEdit.  On the other hand, it gets
totaled with some other stuff.  I think I would stick with Memory.r.
 
G. Gordon Apple   D4887
Advanced Communications Engineering, Inc.
Redondo Beach, CA
From: CDA1051@AppleLink.Apple.COM (ACR Vinko Enterprises, V Tsui,ILA)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: Bedrock News
Date: 16 Dec 92 23:46:00 GMT
Organization: AppleLink Gateway

Hi Rob, Ramon:
 
It is always good to hear info. on upcomming "advancements".  I just have a few
comments that may stir up some discussion.
 
>The big problem there is that every app you create carries this Framework
>around as luggage....
>
>...why do we need to have "includes" or "USES" clauses in an OOP environment?
>There should be a big object database behind the scenes -- we just call up
>whatever objects we want, and the extra ones are stripped out at compile time.
>All files could go away......
>
>Furthermore, we should be able to edit and incrementally compile any
>particular part of the program, and test it out right away. This is
>obviously feasible (check out MCL or some if its offspring).
 
From the above comments extracted from Ramon M. Felciano's EMail, it sounds
like Component Workshop by Component Software Corp. is what Ramon wants.  Has
anyone else looked into this alternative, that is available today or at least
sometime in Jan '93, who like to comment?
 
As I understand it, Component Workshop' Extruder suppose to solve the problem
of unwanted luggage.  It "extruds" the combination of standard objects provided
by the Component Workshop frameworks and subclasses that the "programer"
creates, and produce a double-clickable application with only the objects and
methods used.  It also included a AT&T C++ subclasss interpreter that support
incremental builds.
 
>It seems to me that there should be a default application framework that is
>always active and is part of the system software.
 
Pen based systems currently have taken this approach.
 
Just thought I start a discussion to clear the air.
 
Sincerly,
 
:-)
 
Vinko Tsui
Vinko Enterprises
1193 Lindsay Drive
Oakville, Ontario
Canada
L6M 3B8
Tel.: (416) 338-7836
Fax.: (416) 338-7836 (automatic Fax Modem attached)
From: YOSEMITE@AppleLink.Apple.COM (Yosemite SW, Nikhil Bhatt,APD)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: 7.0 Color -> windoid WDEF?
Date: 16 Dec 92 02:12:00 GMT
Organization: AppleLink Gateway

I noticed that the MacApp windoid WDEF does not draw its title bar in color. As
a result, the windoid looks a little out of place next to colorized document
windows. Has anyone had added System 7 color window management to the windoid
WDEF? If it's free, great, but we're also willing to purchase rights to it.
 
--Nik
From: D4978@AppleLink.Apple.COM (Third Point Sys, Thomas Collins,PAS)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: SLM & Dinker
Date: 14 Dec 92 19:19:00 GMT
Organization: AppleLink Gateway

Is there a difference between SLM and Dinker or could one consider SLM a
superset of Dinker?
From: CHRIS_KNEPPER@TALIGENT.COM
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: TPopup problem..
Date: 18 Dec 92 09:04:00 GMT
Organization: AppleLink Gateway

From: "Chris Knepper" <Chris_Knepper@taligent.com>
To: "DATEC A/S, STORAS, NO, IVC" <NOR0154@AppleLink.Apple.COM>,
     "MacApp 3 Technical Discussion" <MACAPP3TECH$@AppleLink.Apple.COM>
 
        Reply to:   RE>TPopup problem..
Hi Bjorn,
 
Here are a couple of tips that might help get your popups working:
 
1. For all your popups, make sure that the popups' CMNU ids are contained in
the kMbarHierarchical MBAR resource.
 
2. Due to a bug, make sure that the menu id and the CMNU resource id are the
same. The menu id is contained in the CMNU resource. Frequently, if when usin
g copy and paste to create a new CMNU, one forgets to change the menu id cont
ained in the CMNU resource to match the CMNU resource id.
 
Hope this helps,
 
-Chris
From: BROSNAHAN.R@AppleLink.Apple.COM (Richard Brosnahan,GEIS)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: RE3: Memory Leaks
Date: 14 Dec 92 13:07:00 GMT
Organization: AppleLink Gateway

From: Richard Brosnahan on Mon, Dec 14, 1992 8:05 AM
Subject: RE3: Memory Leaks
To: MacApp 3 teck
 
MacApp dudes,
 
Let's not forget ZoneRanger! I find it more useful than Swatch. It has a few
more features and doesn't need to be loaded as an INIT. Not only can you watch
memory get eaten up "live" but you can click on the memory and see what's in
there! Very useful!
 
RCB
_______________________________________________________________________________
From: INTERNET#    on Mon, Dec 14, 1992 4:35 AM
Subject: Re: Memory Leaks
To: Richard Brosnahan
 
INTERNET# Document Id: <9212131953.AA24329@apple.com>
 
Item    6415898                 92/12/12        15:28
 
From:@INTERNET#                         Gateway to Internet/BITNET/UUCP
 
To:     MACAPP3TECH$                    MacApp 3 Technical Discussion
 
Sub:    Re: Memory Leaks
 
From:
Organization: (Evil Eye Creature from Mars, Inc.)
To: MacApp3Tech$@Applelink.apple.com
 
In article <724192662.2890464@AppleLink.Apple.COM>,
DEWAELE.W@AppleLink.Apple.COM (De Waele Willy - Gent,BE,IHD) wrote:
>
> Hi Peter,
>
> On the Developer CD's, there is *somewhere* a 'dcmd' 'Leaks' which should be
> copied/pasted into the 'Debugger Prefs' of MacsBug.
> I didn't have time/occasion to experiment with this.
 
The Swatch application is also handy for finding about leaky apps, just let
it
run in a window, and check out if the free heap numbers are mysteriously
ticking down even if you are not doing anything.  Even better, if you could
figure out the size of the chunks that decrease, it might even give an
indication what is really leaking (sometimes).
 
Kent
-------------------
Kent Sandvik (UUCP: ....!apple!ksand; INTERNET: ksand@apple.com)
DISCLAIMER: Private activities on the Net.
From: liran@bimacs.BITNET (Eshel Liran)
Newsgroups: comp.sys.mac.oop.macapp3,comp.sys.mac.programmer
Subject: ViewEdit like sample code
Date: 15 Dec 92 17:41:52 GMT
Organization: Math & CS, BarIlan U, Ramat-Gan, Israel

Is there a sample code somewhere which works like ViewEdit or ResEdit ?

Liran,
liran@bimacs.cs.biu.ac.il
From: SDOBBS@TRIVIA.COGINST.UWF.EDU
Newsgroups: comp.sys.mac.oop.macapp3
Subject: TEditText problems
Date: 19 Dec 92 00:40:00 GMT
Organization: AppleLink Gateway

I have made a subclass of TEditText that doesn't override very much stuff,
and should draw the TEditText fine.  However, when I call the IEditText
method, the TEditText is located in the appropriate place, but is drawn at
(0,0) of the superview.  The TTEText is located in the right place, and I
can type into it, but if I scroll the window around, the text is drawn at
(0,0).  Has anyone ran across this problem before?
 
Steven Dobbs <sdobbs@ai.uwf.edu>
Institute For Human and Machine Cognition
University of West Florida
Pensacola, Florida
 
Man will occasionally stumble upon the truth, but most of the
time he will pick himself up and continue on.
From: USER@WINTERMUTE.APPLE.COM
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: SLM & Dinker
Date: 15 Dec 92 00:45:00 GMT
Organization: AppleLink Gateway

From:
    goofy!mumbo.apple.com!gallant.apple.com!wintermute.apple.com!user@apple.com
Message-Id: <ksand-141292164446@wintermute.apple.com>
Organization: (Evil Eye Creature from Mars, Inc.)
To: MacApp3Tech$@Applelink.apple.com
 
In article <724362445.5470812@AppleLink.Apple.COM>,
D4978@AppleLink.Apple.COM (Third Point Sys, Thomas Collins,PAS) wrote:
> Is there a difference between SLM and Dinker or could one consider SLM a
> superset of Dinker?
 
Dinker and SLM are two very different concepts. They have both overlapping
features and things that the other part does not. Dinker is not supported
by Apple. SLM is.
 
 
Kent
-------------------
Kent Sandvik (UUCP: ....!apple!ksand; INTERNET: ksand@apple.com)
DISCLAIMER: Private activities on the Net.
From: D4887@AppleLink.Apple.COM (Advanced Comm Eng, G G Apple,PRT)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: Bug In TDynamicArray (MA3.
Date: 15 Dec 92 23:43:00 GMT
Organization: AppleLink Gateway


 
----------------------------------------------------------------------------
>The problem arises when a TDynamicArray is cloned while an Iterator which was
>used for the TDynamicArray is stil in scope. TDynamicArray has a field named
>fIteratorPtr, which contains a linked list of Iterators currently in use for
>the TDynamicArray. When a TDynamicArray gets cloned, both (the old and the
>cloned Array's) fIteratorPtrs point to the same Iterator. If the
>CArrayIterator
>is destructed, the fIteratorPtr of the cloned TDynamicArray points to an
>invalid Memory-Address.
 
    By golly, you're right!  How they ever let one this obvious slip through
I'll never know.  TDynamicArray should have a Clone override that sets
fIteratorPtrs = NULL.
 
    What the heck are you doing that creates a clone of the array while you're
iterating it?  It seems to me that the only time that linked list of iterators
get used is when iterations are nested -- unless you are instantiating
iterators as seperate objects and not by the usual method on the stack.
 
    My other comment would be the same that I usually give to people that ask
me about subclassing, cloning, or file-storing TList and other such
TDymamicArray thingies:  "DON'T DO THAT".  Usually, these things are used by
(referenced by) other objects which are what you really want subclassed,
cloned, or stored.  Let their clone methods do the work.  Also, note that
cloning the TDynamicArray does NOT clone the objects refered to in the array.
 
    For example, I usually create my own list classes which encapsulate TList
with my own functionality.  When I want to clone something that has a
referenced TList, I always let the encapsulating object ask for a new list and
then, in the clone method of my object, iterate the cloned list to add all of
the old elements to the clone list.  That process creates a clone of the list,
but not of the contents (elements) of the list (i.e., the new list has
references to all the old elements).  If you really want a deep clone (a
seperate new list with its own new elements) then you must clone each element
and add its clone to the clone list rather than adding the old elements.
 
    I guess that explains why I (and others) never ran into the problem you
found.
 
G. Gordon Apple    D4887
Advanced Communications Engineering, Inc.
Redondo Beach, CA
 
------ Where we are not having any floods, hurricanes, blizzards, freezing,
volcanic eruptions, famines, or tidal waves -- just the usual earthquakes and
riots.  I think I'll go for a walk on the beach (two blocks away) in my shirt
sleeves this afternoon.
From: GOLUB@SGI.SIEMENS.COM
Newsgroups: comp.sys.mac.oop.macapp3
Subject: RE: RE3: Memory Leaks
Date: 14 Dec 92 16:27:00 GMT
Organization: AppleLink Gateway

>Let's not forget ZoneRanger! I find it more useful than Swatch. It has a few
>more features and doesn't need to be loaded as an INIT. Not only can you watc
>memory get eaten up "live" but you can click on the memory and see what's
>there! Very useful!
 
oops. here is the information that i promised.
 
-------------------------------------------------------------------------
 
  ZoneRanger is available from the following sources:
 
  1. applelink
 
     "Software Sampler:Software Collection:Programmer Tools:ZoneRanger 0.9.0B"
 
  2. ftp
 
     aristotle.ils.nwu.edu (129.105.100.1)
     pub/engber/ZoneRanger090.hqx
 
  3. email
 
     if neither ftp nor applelink is available, i can mail it to you.
 
  ---------------------------------------------------------
 
  ZoneRanger 0.9.0
 
  ZoneRanger provides detailed information about each heap zone that is
  currently active on the Macintosh. This information includes both the count
  and total sizes of the free blocks, pointers, handles, locked handles,
  purgeable handles, and resource handles in each heap zone.
 
  ZoneRanger also provides windows in which a heap zone can be displayed
  graphically, with the size, type, and attributes of each block clearly
  defined. The user can control the resolution and zoom factor of this
  display, as well as click on any individual block to view its contents.
 
  please send any bug reports, comments, or suggestions to:
 
    golub@sgi.siemens.com
 
  thankyou.
From: D1950@AppleLink.Apple.COM (STM Systems Corp, Don Phillips,PRT)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Opening Files using MacApp 3.0
Date: 15 Dec 92 16:45:00 GMT
Organization: AppleLink Gateway


 
 
Background :
 
We are currently converting our applications from MacApp 2.0 to 3.0 using
Object Pascal. Our plans are to convert to 3.0 now and then convert to C++ at a
future time.
 
Question:
 
We have notice that MAOpenFile no longer exists in 3.0
What should we replace it with?
Should we use the TFile object?
 
Any guidance would be appreciated.
 
Ett DiNardo
ISM Corp.
AppleLink : D1950
From: SCHALK1@AppleLink.Apple.COM (Euro Tech Svcs, OOP Spec)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: Getting idle time in a vie
Date: 15 Dec 92 19:01:00 GMT
Organization: AppleLink Gateway

Rich,
 
You could attach a IdleBehaviour to the window that contains the view. Give
this behaviour a reference to the view(s) that need idle time and call the
TView.DoIdle() method MANUALLY for each of those views.
 
If you don't want to add a behaviour, implement this in the TWindow.DoIdle()
method and use FindSubViews().
 
By the way, the cohandler chain works as well, but is not the preferred way of
doing things (maybe you get the crash because you forget to remove the
cohandler when you close the window?).
 
Anyone out there with a more elegant suggestion?
 
Regards,
 
Jeroen Schalk
Object Programming Specialist
European Technology Services
Apple Computer Europe
 
Newsgroups: comp.sys.mac.oop.macapp3
From: jtbell@hubcap.clemson.edu (Jon Bell)
Subject: Re: MAC APP 3, pascal programmer
Organization: Presbyterian College, Clinton SC
Date: Sat, 19 Dec 1992 22:10:45 GMT

In article <1992Dec19.161916.9766@mnemosyne.cs.du.edu> gtapolow@nyx.cs.du.edu (Greg Tapolow) writes:
>
>I've recently updated from Macapp 2 to 3. I program primarily in Pascal as
>a hobbyist. Do I still need to purchase MPW C++ to compile my programs?
>
My understanding is that if you do not need to re-compile the MacApp sources,
you do not need C++ in order to use MacApp with Pascal.  If this isn't true,
I hope somebody will correct me, as I'm considering upgrading also.

Jon Bell / Dept. of Physics & C.S. / Presbyterian College / Clinton SC

Newsgroups: comp.sys.mac.oop.macapp3
From: ksand@apple.com (Kent Sandvik )
Subject: Re: TDialogView in Ad Lib
Date: Wed, 16 Dec 1992 02:03:02 GMT
Organization: (Evil Eye Creature from Mars, Inc.)
Followup-To: comp.sys.mac.oop.macapp3

In article <724462717.0501359@AppleLink.Apple.COM>,
BARBOSE@AppleLink.Apple.COM (Amoco Technology, Jeff Barbose,VAR) wrote:
> 
> Ken,
>  
> In the attribs window, make a window a Dialog by clicking the radiobutton
> "Dialog".
>  
> This doesn't make it a TDialogView, but rather adds a TDialogBehavior to the
> window's/view's behavior lists.
>  
> Voila!  Instant dialog.

Are we talking about Ad Lib, or ViewEdit 3.0? Nota bene, MacApp 3.0.1 won't

add in any TDialogBehaviors when creating TDialowViews inside the window.
This is documented in MacApp 3.0.1 Bug Doc (the non Doc Viewer document). 
The workaround is (for the N time):
----
 1. Problem with displaying dialogs, especially if created
  with ViewEdit.
  
  A drawback in ViewEdit 3.0.1 is that it does not provide
  for behaviors and TDialogBehaviors in particular to be
  specified. A work around for TDialogBehaviors is to fix
  the bug in TWindow::PoseModally() that causes what would
  otherwise be the automagic creation of the
  TDialogBehavior not to take effect. If the following
  lines in PoseModally
  
        TDialogBehavior* itsDialogBehavior = this-
  >GetDialogBehavior();
        IDType result = kNoIdentifier;
        this->Open();
        this->Select();
  
  are changed to
  
        TDialogBehavior* itsDialogBehavior;
        IDType result = kNoIdentifier;
        this->Open();
        this->Select();
        itsDialogBehavior = this->GetDialogBehavior();
  
  then the automagically created behavior is correctly
  assigned to the window and functions correctly.
  
  Alternate  ways that you can get a behavior into a view
  resource are to
  - DeRez an existing view or create the view with Rez
  initially; then specify a dialog behavior in the Rez text
  format; then re-Rez, or
  - create your TDialogBehavior or entire dialog
  procedurally.
----


Kent
-------------------
Kent Sandvik (UUCP: ....!apple!ksand; INTERNET: ksand@apple.com)
DISCLAIMER: Private activities on the Net.
Newsgroups: comp.sys.mac.oop.macapp3
From: ASTRO.SPUD@AppleLink.Apple.COM (Lockwood, Mike)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: SLM & Dinker
Date: 14 Dec 92 23:53:00 GMT
Organization: AppleLink Gateway

Hi Thomas,
 
There are a lot of differences between SLM and Dinker (forgive me if I can't
think of all of them).  Neither can be thought of as a superset of the other.
However, as SLM evolves, this may someday be the case.
 
Here are the differences I can think of:
 
SLM is supported by Apple and will continue to grow and develop; Dinker is not
supported.
 
SLM allows you to share libraries of code between several applications; Dinker
does not.
 
Dinker allows you to develop an application that can dynamically load
extensions, either at the start of the application or later on as a result of a
use command.  The extensions can be developed independently of the application,
perhaps by a different person or organization.  I don't believe SLM currently
supports this.
 
Dinker works with modified versions of MacApp 2.0 and 3.0; SLM is not
compatible with MacApp, because SLM does not support PascalObject (maybe
Bedrock will support SLM???)
 
SLM includes support for memory and object allocation at interrupt time, and
other goodies that make it useful for system level programming (it was designed
to support networking protocols).
 
I'm sure I missed somethings, and my details might be a bit sketchy.  Check the
documentation on E.T.O #9 for more information!
 
Mike Lockwood
From: EDS.TECH.DEV@AppleLink.Apple.COM (EDS, Doug McCubbrey,PRT)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Help !!Disappearing Menu Items
Date: 16 Dec 92 21:21:00 GMT
Organization: AppleLink Gateway

I have a strange problem.  In my MacApp application, on some machines,
not any particular model, my application menus do not come up with any items.
The MacApp menus (File and Edit) work correctly.  I have taken an app working
on my Quadra and copied it to a CI or another Quadra and this anamoly will show
up.  I have no idea what is causing it.  I have traced it, on the machine where
it shows up, to the MenuSelect trap and everything looks normal.  I have
disabled all inits and it still doesn't work correctly.  The machines it shows
up on are running sys 7.01 with 32k RAM.  Has anybody ever seen this??
Thanks in advance,
Chip Schoch, EDS
Organization: University of Maine System
Date: Wednesday, 16 Dec 1992 21:16:40 EST
From: <IO92668@MAINE.MAINE.EDU>
Newsgroups: comp.sys.mac.oop.misc
Subject: FTP site for Prograph Librarys or compatible C/PASCAL libraries.

Please mail me if you know of any.

io92668@maine.maine.edu
From: korfhage@weston.poly.edu (Willard Korfhage)
Newsgroups: comp.sys.mac.oop.misc
Subject: Scrolling list class for Think C version 5?
Date: 11 Dec 92 18:22:24 GMT
Organization: Polytechnic University, New York

Is there a scrolling list class available for Think C version 5? Either
free, or one that can be bought. I got Louis King's CListMgrPane,
but that is for version 4 of think C. I did change it to compile
under v5, but it has a problem - an update event in the window
containing the lists somehow causes a cascading series of update
events that never stop. If someone has fixed this, or
knows of another class, please let me know.

Incidentally, is there any elegant class to handle non-modal dialog boxes?

Thanks

   Willard Korfhage
   korfhage@weston.poly.edu
From: yjc@po.cwru.edu (Jerome 'TofuSoft' Chan)
Newsgroups: comp.sys.mac.oop.misc
Subject: Think C Class and The Apple Event Object Model
Followup-To: comp.sys.mac.oop.misc
Date: 15 Dec 1992 20:23:55 GMT
Organization: The Tofu Society of Singapore
Distribution: world
NNTP-Posting-Host: b61539.student.cwru.edu

Is there going to be an upgrade/rewrite to TCL to support AE Object Model?
Curious Minds Want To Know.

---
The Evil Tofu