HDTenEightyP/NetNews huggingface dataset:
From: LEIGH@AppleLink.Apple.COM (Daniels, Leigh,APD)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Where's my decoder ring?
Date: 20 Nov 92 03:27:00 GMT
Organization: AppleLink Gateway

Attn: MacApp3Tech$
SentBy: Leigh Daniels
 
                       Subject:                               Time:10:06 PM
  OFFICE MEMO          Where's my decoder ring?               Date:11/19/92
Dear Apple (and MacAppers),
 
I have a debug version of my app that seems to work fine and has some major
components in place and I thought I'd build a non-debug version to see how
much disk space it would use. I compiled with  -NoDebug -NoSym -NoNeedsSystem7
and got a successful complilation. However, when I ran it I got the following
dialog when I tried to create a new document: "Could not create a new document
because an internal component is missing. Please contact the developer."
 
Checking the ErrMgr.r file shows that the debug version of this message is
"Call Apple for a secret decoder ring" -- not the most helpful information.
 
Well, Apple, I'd like my secret decoder ring. What does it mean? What causes
it to be generated? Why isn't it triggered in the debug version of my app?
 
**Leigh
From: ksand@apple.com (Kent Sandvik )
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: Apple support for cfront 3.0 ??
Date: 21 Nov 92 19:41:21 GMT
Followup-To: comp.sys.mac.oop.macapp3
Organization: Apple

In article <1ejmcfINNfs4@network.ucsd.edu>, frost@sdsc.edu (Richard Frost)
wrote:
> Since MacApp is a C++ class library, it is pertinent to ask when
> Apple will support AT&T cfront (C++) v3.0.  The current supported
> version (2.1) is lacking several key features.

Templates is indeed a nice feature, I would just like to know what
other key features Cfront 3.0 provided.

Kent
-------------------
Kent Sandvik (UUCP: ....!apple!ksand; INTERNET: ksand@apple.com)
DISCLAIMER: Private activities on the Net.
Newsgroups: comp.sys.mac.oop.macapp3
From: jjamison@bellahs.com (John Jamison RD AC)
Subject: Future of MacApp
Followup-To: jjamison@bellahs.com
Organization: Bell Atlantic Healthcare Systems
Date: Tue, 17 Nov 1992 17:25:54 GMT

hi,
I understand that Apple has publicly announced the end of
development of MacApp. Can a kind soul please fill me
in on the details of the announcement?  What are they
saying to all of the early converts who now have a dead
programming environment?

-- 
-----------------
John Jamison
Bell Atlantic Healthcare Systems
jjamison@bellahs.com
Newsgroups: comp.sys.mac.oop.macapp3
From: koppi@aplcenmp.apl.jhu.edu (Jeffrey Alan Koppi)
Subject: ViewEdit vs. AdLib
Organization: Johns Hopkins Continuing Professional Programs
Date: Thu, 19 Nov 1992 02:15:51 GMT



There are several tools available to create View resources for use with MacApp.
I am using Apple's ViewEdit program and have been successful,
however I have heard that it has bugs.

Is the AdLib product any better? Does it offer any features not found 
in ViewEdit?

AdLib is available from MADA, and I've read the ad, but I was wondering if 
anyone is actually using it...




Jeff Koppi
koppi@aplcenmp.apl.jhu.edu
From: malcolm@apple.com
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Turning on AppleLink
Date: 19 Nov 92 02:20:18 GMT
Organization: AppleLink Gateway

OK, this is a test....if this message makes it into the 
comp.sys.mac.oop.macapp3 newsgroup then I'm going to turn on the bits from 
AppleLink.

Sorry for the wasted bits.....

For now traffic is only gatewayed in one direction (AppleLink->Usenet).  
If you want to reply to a note that is posted then you should probably 
send an email message to the person.  If their message came from AppleLink 
then they won't get your Usenet reply.

Enjoy.

								Malcolm
From: SOFTARCH@AppleLink.Apple.COM (SW Architects, Carl Nelson,PRT)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: MacApp and Macintosh oppo
Date: 23 Nov 92 08:54:00 GMT
Organization: AppleLink Gateway

Attn: JOB SEEKERS
SentBy: Rich Vasse
 
                      MacApp and Macintosh opportunity
For those people looking for a good opportunity or who know an individual who
is actively pursuing a new career, please consider...
 
Software Architects, Inc. has an immediate opening for a software engineer who
has experience in Macintosh programming (MPW or ThinkC).  Knowledge of Device
drivers, DOS, MacApp, C++, and Object oriented programming desired.  Should
have at least 2-3 years development experience.  Software Architects, Inc. is
a growing company situated in the Seattle, WA area and offers profit-sharing
and benefits in a non-smoking environment.  Please send background and
expertise to:
 
     Engineering Dept. Mgr
     Software Architects, Inc.
     19102 N. Creek Pkwy, Suite 101
     Bothell, WA 98011
     AppleLink: SOFTARCH.
     FAX:  (206) 487-0467.
 
Rich Vasse, Engineering Manager Software Architects, Inc.
 
 
Newsgroups: comp.sys.mac.oop.macapp3
From: kinsey@athena.cs.uga.edu (Kevin Kinsey)
Subject: TextEdit under 3.0.1 wigging out
Organization: University of Georgia, Athens
Date: Fri, 20 Nov 1992 02:31:30 GMT


howdy folks,
I've lurked for some time but never had a reason to post...until now.
the problem:
	I've just installed/compiled/etc MacApp 3.0.1 and recompiled
	my app. I thought I had read the bugslist carefully, but maybe
	I missed something. (3.0.1 & bugslist from the new E.T.O. #9)
	All of My TTEViews and TEditTexts are now behaving very strangely,
	i.e. they refuse to display text. I know the text is there.
	In my TTEViews, the scrollbar will activate and the I-beam cursor
	will appear in all the right places but no text. Selection is
	really wigged-out as well. multiple blocks of hilighting nothing is
	possible. I can force a redraw of the view and the text will
	appear in the TEditText, but not TTEView. Using The Debugger,
	the actual object is fine, including the TERecord.

Does anyone have a solution/hint/guess as to what's going on. This sort
of behavior wasn't present under 3.0.

thanks

kevin
-----
kevin kinsey
University of Georgia
athens, ga
kinsey@athena.cs.uga.edu
From: davidp@calvin.usc.edu (David Peterson)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: Apple support for cfront 3.0 ??
Date: 21 Nov 1992 14:43:51 -0800
Organization: University of Southern California, Los Angeles, CA
Distribution: world
Reply-To: davidp@usc.edu
NNTP-Posting-Host: calvin.usc.edu


In article <ksand-211192114134@wintermute.apple.com>, ksand@apple.com (Kent Sandvik ) writes:
|> 
|> Templates is indeed a nice feature, I would just like to know what
|> other key features Cfront 3.0 provided.
|> 

Exception handling would be nice. I don't always use MacApp and being able to
throw and catch errors in my other code would be a plus.

-dave.
From: B.HABLUTZEL@AppleLink.Apple.COM (Hablutzel, Bob,CST)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: TWindow::PoseModally Bug
Date: 22 Nov 92 16:20:00 GMT
Organization: AppleLink Gateway

Ken -
 
  This could be a bug, or just a change in the way the PoseModally sequence
works. I'll leave that to the historians to decide.
  The fix is to make sure you call myWindow->Open() before you call
myWindow->PoseModally(). This will ensure that the proper behaviors, etc are
set up before the call.
 
 
Bob
 
 
Bob Hablutzel
Hablutzel Consulting
ALink: B.HABLUTZEL
Phone: 708 328 0130
From: SCHALK1@AppleLink.Apple.COM (Euro Tech Svcs, OOP Spec)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: CStr31 Array Syntax???
Date: 19 Nov 92 03:54:00 GMT
Organization: AppleLink Gateway

Ken,
 
CStr31 fPeriodNames[3];
is equivalent to
CStr31 fPeriodNames[3] = {CStr31::CStr31(), CStr31::CStr31(),
CStr31::CStr31()};
 
In ARM (C++ Annotated Reference Manual) page 264, it is stated that:
"... it allowed an array of objects to be initialized by a standard function
taking a pointer to function argument specifying what initialization needed to
be done for each element in the array".
 
So, CFront initializes by taking the adress of CStr31::CStr31() and iterating
from 0 to 2.
 
Now, CStr31::CStr31() is declared inline (in PascalString.h), and if you take
the address of an inline function, an explicit (non-inline) copy has to be
created (ARM page 102).
 
This is what the compiler is warning you about. Nothing is wrong. Fix is to go
into PascalString.h and remove the inline specification. (I advise against
doing that, just ignore the warnings).
 
Regards,
 
Jeroen Schalk
Object Programming Specialist
European Technology Services
Apple Computer Europe
Currently in DTS
From: yeung@reed.edu (Woodrow Yeung)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Scope of Newsgroup
Date: 17 Nov 92 03:19:03 GMT
Article-I.D.: reed.1992Nov17.031903.15278
Organization: Reed College, Portland, Oregon

Hello,

Can we change this newsgroup to just comp.sys.mac.oop.macapp?  I assume
MacApp 2.0 will be discussed here too.

Woody Yeung
yeung@reed.edu
Newsgroups: comp.sys.mac.oop.macapp3
From: ksand@apple.com (Kent Sandvik )
Subject: Re: Apple support for cfront 3.0 ??
Date: Sun, 22 Nov 1992 06:11:09 GMT
Organization: Apple
Followup-To: comp.sys.mac.oop.macapp3

In article <1eme37INN84v@calvin.usc.edu>, davidp@calvin.usc.edu (David
Peterson) wrote:
> In article <ksand-211192114134@wintermute.apple.com>, ksand@apple.com (Kent Sandvik ) writes:
> |> 
> |> Templates is indeed a nice feature, I would just like to know what
> |> other key features Cfront 3.0 provided.
> |> 
> 
> Exception handling would be nice. I don't always use MacApp and being able to
> throw and catch errors in my other code would be a plus.

Yeah, I would also like to have exception handling, however Cfront 3.0
*don't* introduce this one. Check out the TRY macros in the DTS sample
folder for temporary use. Also TCL has a set of nice macros, and DTS
are doing some re-work for a future publishing of even more refined
macros (that's why I'm here 10pm a Saturday evening working when decent
folks
are having fun...).


Kent
-------------------
Kent Sandvik (UUCP: ....!apple!ksand; INTERNET: ksand@apple.com)
DISCLAIMER: Private activities on the Net.
From: KVICTOR@AppleLink.Apple.COM (Victor Consulting, Ken Victor,CST)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: TWindow::PoseModally Bug
Date: 21 Nov 92 23:01:00 GMT
Organization: AppleLink Gateway

I believe the following is a bug in MacApp 3.0.1.
    Create a View with ViewEdit 3.0 that has a window, a dialog view, and ...,
    in your program call NewTemplateWindow and then call aWindow->PoseModally.
 
TWindow->PoseModally gets the dialog behavior first, then opens the window
(which will open the dialog view) and then calls itsDialogBehavior->PoseModally
(if itsDialogBehavior was non null at entry to TWindow->PoseModally).  The
problem is that the dialog behavior isn't created until the dialog view is
opened.  In other words, the window should be opened before getting
itsDialogBehavior.
 
Also, nowhere in this sequence is itsDialogBehavior->fModal set to true.  As a
result of this the window that you thought you were modally posing is posed
modeless!!
 
Ken Victor
(415) 964-9870
From: X0591@AppleLink.Apple.COM (MacApp Dev Assoc, Howard Katz,IVC)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: New MADA Group in BC
Date: 24 Nov 92 00:29:00 GMT
Organization: AppleLink Gateway


 
MadaBC (strictly a working title at this point) is pleased to announce its
second meeting, scheduled for the evening of Thursday, December 3. Anybody's
who's interested in MacApp, Bedrock, Component Workshop, C++, Smalltalk, or any
other OOP language or class library on the Mac is more than welcome to attend.
(That even goes for our American neighbors to the south.) (Canadians are
nothing if not big-hearted!)
 
We had our first meeting on November 5 on very short notice, with a turnout of
eleven, representing six different companies in the Vancouver area who are
either doing or proposing to do OOP work on the Mac in the near future. Three
of the companies in attendance are currently working on MacApp 3.0 projects,
with an eye to Bedrock conversion in the near future.
 
The upcoming meeting will be held at the Burnaby offices of Electronic Arts,
Canada at #400 - 4400 Dominion Street. Electronic Arts is in the old Dominion
Directory building, just across the road from the Sheraton Inn Hotel.
 
Dominion Street is a bit tricky to find. It's just off TransCanada Highway 1, a
block from the intersection of Canada Way and Willingdon. Go one block east of
Willingdon on Canada Way, heading toward Vancouver, and turn north onto Sumner.
Travel two blocks toward the Sheraton Inn, turn right on Dominion, and go to
the end of the block. Try to avoid parking too close to the hotel pub so that
your car doesn't get puked on during the meeting.
 
We meet at 7:30 sharp. Somebody will be at the main door between 7:00 and 7:30
to let you in. Please be prompt: if you're late, you won't be able to get into
the building. (And you'll have to spend your evening alone in the pub.)
 
Andrew Brownsword of Electronic Arts, Canada will be showing a demo of Parc
Place's ObjectWorks package and Acius's Object Master. I'll be demoing
Component Workshop.
 
Howard Katz
 
P.S. No pets, please.
From: KVICTOR@AppleLink.Apple.COM (Victor Consulting, Ken Victor,CST)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: CStr31 Array Syntax???
Date: 19 Nov 92 02:22:00 GMT
Organization: AppleLink Gateway

Could someone please tell me what i'm doing wrong.
 
i have the following definition in one of my header files:
 
class TAccountsDocument : public TFileBasedDocument {
       public:
          ...
        CStr31 fPeriodNames[knPNames]; // period names
       ...
 
this gives the following warning message:
 
Compiling:     UAccountsDocument.cp
warning: -d or -u option(s) will not affect code saved in dump file
File "UAccountsDocument.h"; line 55 # warning: can't take address of inline
                    function  CStr31::CStr31(),  CStr31::CStr31() not inlined
File "Data:Accounts:UAccountsDocument.cp"; line 220 # warning: out-of-line
                    copy of  CStr31::CStr31() created
 
line 55 in the header file is the closing brace (}) of the class definition.
line 220 of the .cp file is after the last statement.
 
i am trying to declare a class variable to be an array of CStr31s.  If I am
using the wrong syntax, could someone please tell me the right syntax.  if i am
using the right syntax, could someone give me an idea of where to look for what
i am doing wrong to generate these warning messages.
 
thanx,
Ken Victor
(415) 964-9870
From: malcolm@Apple.COM (Malcolm Slaney)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: MacApp3 from AppleLink
Keywords: MacApp3, Hello, AppleLink, Starting
Date: 17 Nov 92 05:14:54 GMT
Organization: Apple Computer Inc., Cupertino, CA

This is just a short note to welcome you to the new MacApp3 newsgroup.

This newsgroup should only be used for MacApp (version 3.0) discussions.
It will be gatewayed to a similar (very active) mailing list on AppleLink
which has a similarly narrow focus.  If you wish to discuss other object-
oriented programming paridigms for the Macintosh then the right place to
do this is in the comp.sys.mac.oop.misc newsgroup.  If traffic warrants
then other subgroups can be created.  But that's up to you readers.

Thanks to John Werner (at Berkeley) for organizing this.

I have the gateway software compiled, tested, and ready to run.  There is 
already an active discussion on AppleLink with over 300 developers (both
inside and outside of Apple).

Unfortunately, the Call-For-Votes ended at the same time as a new person
took over our (apple's) main news feed.  This is good news, but it does
mean that turning on the MacApp3 newsfeed is delayed.  Anyway, I've given
them a list of commands to install so it should happen any day now.

The plan is to first gateway all traffic from the AppleLink mailing list
Macapp3tech$ to Usenet.  There is a potential problem with MessageIDs that
come out of AppleLink which I had to program around.   I would like to
watch this for a couple of days (with real traffic) before I turn on the
gateway in the other direction (Usenet to AppleLink).  

If I screw up then there is a chance that some messages from Usenet will go 
to AppleLink and then get dumped back into the newsgroup (duplicate messages).

You should be seeing lots of bits any day now....I'm sorry for the delay.

Happy MacApping....


						Malcolm Slaney
						Apple ATG Perception Group
						Part-time MacApp-er
From: MADA.LIB@AppleLink.Apple.COM (MADA Librarian, Arvid Jedlicka,PRT)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: Where's my decoder ring?
Date: 20 Nov 92 04:00:00 GMT
Organization: AppleLink Gateway

Leigh,
 
Shot in the dark:
 
Could your secret decoder ring be right next to the page of the project plan
that says "Implemented code that does dead strip supression for my views."?
 
Arvid
From: sls16@po.CWRU.Edu (Samuel L. Shank)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: What is MacApp?
Date: 17 Nov 1992 22:29:08 GMT
Organization: Case Western Reserve University, Cleveland, Ohio (USA)
NNTP-Posting-Host: slc5.ins.cwru.edu


The subject heading says it all.

-- 
Sam Shank
sls16@po.cwru.edu
Newsgroups: comp.sys.mac.oop.macapp3
From: jepaul@news.weeg.uiowa.edu (Darth Jason)
Subject: Hp Paint Jet printer driver
Organization: University of Iowa, Iowa City, IA, USA
Date: Fri, 20 Nov 1992 15:37:38 GMT



I
I am looking for the Hewlett Packard Paint
Jet printer driver.  If anyone can help 
me with this it would be greatly appreciated.
From: WERNER@SOE.BERKELEY.EDU
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: SourceBug "step in" proble
Date: 19 Nov 92 02:23:00 GMT
Organization: AppleLink Gateway

From: werner@SOE.Berkeley.Edu (John Werner)
Subject: Re: SourceBug "step in" problem
To: GILLAM.R@AppleLink.Apple.COM (Richard Gillam, GEIS),
     MACAPP3TECH$@AppleLink.Apple.COM (MacApp 3 Technical Discussion)
 
>I'm having a problem with SourceBug.  Right now, it seems any time I use the
>"step into" command on a method call, I bomb.
>One change since
>then that might matter is the addition of a bunch of pure C++ classes I'm
>importing from another team member here.
 
I had some SourceBug problems recently when I used some
non-TObject-descended classes.  In my case, I had a class descended from
PascalObject, and SourceBug crashed on startup, not while debugging.
Still, it sounds a bit similar.  I ended up "fixing" it by just making my
class descend from TObject.  It sounds like you might not have that option,
so I'm not sure what you should do.
 
John
From: frost@sdsc.edu (Richard Frost)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Apple support for cfront 3.0 ??
Date: 20 Nov 1992 21:46:55 GMT
Organization: San Diego Supercomputer Center @UCSD.
Distribution: world
Reply-To: frost@sdsc.edu
NNTP-Posting-Host: stimpy.sdsc.edu
Keywords: C++


Since MacApp is a C++ class library, it is pertinent to ask when
Apple will support AT&T cfront (C++) v3.0.  The current supported
version (2.1) is lacking several key features.


---
Richard Frost
San Diego Supercomputer Center		619-534-5179 (voice)
P.O. Box 85608				619-534-5113 (fax)
San Diego, CA 92186-9784		frost@sdsc.edu

Newsgroups: comp.sys.mac.oop.macapp3
From: jwo@gallant.apple.com (Jamie Osborne)
Subject: Re: ViewEdit vs. AdLib
Date: Fri, 20 Nov 1992 18:04:06 GMT
Reply-To: jwo@apple.com
Organization: Apple Computer, Inc.

koppi@aplcenmp.apl.jhu.edu (Jeffrey Alan Koppi) writes:



>There are several tools available to create View resources for use with MacApp.
>I am using Apple's ViewEdit program and have been successful,
>however I have heard that it has bugs.

>Is the AdLib product any better? Does it offer any features not found 
>in ViewEdit?

>AdLib is available from MADA, and I've read the ad, but I was wondering if 
>anyone is actually using it...

	I have been using AdLib for a few weeks, and View Edit for a
few months.  View Edit has many problems, not the least of which is
occasional crashing.  Its implementation of grids is awful.
Manipulation of objects in the view is difficult.
	Ad Lib is much more refined and has great potential.  However,
the current version is nowhere near the panacea that people claimed it
would be.  All object attributes are set within modal dialogs.  So if
you want to make an Edit Text, you place the Edit Text object, then you
bring up the modal dialog for Edit Text attribs.  Then you close that
and bring up the dialog for Static Text attribs.  Then you close that and
bring up the dialog for TControl.  Then you close that and etc...
	Ad Lib has three convenient windoids- Objects, Attributes, and
Information.  These windoids make it easy to place objects and edit a
few of their essential attributes.  However, Ad Lib does not remember
which ones of these you had open when you quit the program, so the
first thing you have to do when you launch the program is select the
three windoids from the Windows menu.  Annoying.
	Ad Lib allows you to align items very conveniently- something
ViewEdit can't do.  However, there is a bug in the program that
prevents you from aligning some objects.  I have selected two objects
and found that the Align menu item was still disabled.  So I tried
selecting a third object and suddenly the item was enabled.
	I would strongly advise against using AdLib and ViewEdit
together.  Because AdLib controls the creation and numbering of STR#
resources, you'll find that merely opening a rsrc file with Views in
Ad Lib can severely mess up your STR# resources, if you created them
in View Edit.

	My bottom line- Ad Lib 1.1 or 2.0 will be a fantastic product
and worth the $200.  Ad Lib 1.0 simply has too many problems.  It
solves some of the problems that View Edit has, but it creates other
problems for itself.  Is Ad Lib a good program?  Yes.  Is it $200
worth of good program?  Not for me.


My Disclaimer:  My opinions are solely my own and not those of Apple
Computer.  Comments in this post should not be construed as an
endorsement or criticism on the part of Apple.


Jamie Osborne                                            jwo@apple.com
Enterprise Systems Division               "Just take me as far as the
Apple Computer, Inc.                         Basingstoke roundabout."

Klingon: "Better to live on our feet than to die at our knees!"
--Klingon, "Star Trek VI: The Undiscovered Country", Stardate 9523.8
From: werner@dewey.soe.berkeley.edu (John Werner)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: Scope of Newsgroup
Date: 17 Nov 1992 04:53:53 GMT
Organization: School of Education, U.C. Berkeley
NNTP-Posting-Host: dewey.soe.berkeley.edu

In article <1992Nov17.031903.15278@reed.edu> yeung@reed.edu (Woodrow Yeung) writes:
>Can we change this newsgroup to just comp.sys.mac.oop.macapp?

No.  There was a lot of discussion about this before the newsgroup was
voted on.  This group is going to be gatewayed with the MacApp3Tech$
mailing list, which is for MacApp 3.0 only.  So this newsgroup is for
MacApp 3 discussion.

There is a MacApp 2.0 mailing list you can subscribe to, although
there isn't much traffic on it these days.  If you want to, send mail
to macapp.admin@applelink.apple.com asking to subscibe to
MacApp2Tech$.



-- 
John Werner                        werner@soe.berkeley.edu
UC Berkeley School of Education    510-642-9651
From: DEWAELE.W@AppleLink.Apple.COM (De Waele Willy - Gent,BE,IHD)
Newsgroups: comp.sys.mac.oop.macapp3
Subject: Re: TWindow::PoseModally Bug
Date: 23 Nov 92 00:57:00 GMT
Organization: AppleLink Gateway

Hi Ken,
 
Just in time ... I have written today an Alert Class, which handles movable
dialogs with "OK" (the Cancel button is freed) or "OK/Cancel" buttons.
 
I added following statement
    "aWindow->SetModality(true);"
after the
    "gViewServer->NewTemplateWindow"
A default TDialogBehavior, if there is none.
If there is a behavior, then the modal-switch is set to true.
 
Also i modified in ViewEdit the "Default Choice" of the buttons to mDismiss.
 
Regards
Willy