RE: Code Extras

Reeve

Every VB developer with any experience knows that you can tell how your app
exits, whether via the X or an End command or whatever. Same for when you
use MFC. I mean, Windows is sending the message out, for pity's sake! Not
to save the settings when the X is used, must be a conscious decision,
along the lines of F12 is CA12 and F3 is CF03. I understand that the
pathway through IBm changes is long, but this is NOT hard. The code to save
the stuff is already there, just change your IF statement and connect to
the code. Yikes!

Lose the MRU list? EVERY other Windows app can preserve these things. Come
on, IBM, get with the progam!

Vern

At 10:35 AM 10/18/02 -0400, you wrote:

Andy, this is a known deficiency of CODE; it's remained unaddressed through
several service packs.  I have an e-mail (dated June 19, 2001) from a CODE
team IBM'er confirming the problem and saying, "I am pursuing at this moment
whether or not they can change this behavior."

Other manifestations of this problem include loss of the recently-used list
entries.

Regards,
Reeve

-----Original Message-----
From: code400-l-admin@midrange.com [mailto:code400-l-admin@midrange.com]On
Behalf Of Andy Youens
Sent: Friday, October 18, 2002 10:00 AM
To: code400-l@midrange.com
Subject: RE: Code Extras

Thanks Scott - yes you're right.

I was hitting the big X button on the top right of windows, but if I use
File -> Exit it saves the settings.

First windows applications I know that uses this method!

Thanks for your help.

Regards

Andy


|
|Do you use File-Exit to close Code.  I don't know about these options
but
|some other things aren't saved and retained if you don't exit this way.
|
|Scott Mildenberger
FormaServe Systems Ltd
5 Milecastle
Bancroft
Milton Keynes
T: 01908 319566
W:www.formaserve.co.uk <http://www.formaserve.co.uk/>
E: Info@FormaServe.Co.Uk