<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2800.1476" name=GENERATOR></HEAD>
<BODY id=role_body style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: Arial"
bottomMargin=7 leftMargin=7 topMargin=7 rightMargin=7><FONT id=role_document
face=Arial color=#000000 size=2>
<DIV>>>> [ ] Save windows "Version Info" into a custom property of the
stack <BR>>>> to-be-saved...</DIV>
<DIV><BR>>> Well...no. I'd rather see the text file. In general, I don't
like the <BR>>> IDE messing around with my stacks. Chances are good that I
will open <BR>>> up a stack later on, see a property I don't remember
putting there, <BR>>> not know what it is for, and not know what to do
with it. I don't <BR>>> like when that happens. I don't mind loading a
text file though, and <BR>>> I think this would be a handy feature. Right
now I do the same thing, <BR>>> only I keep the settings all together in a
stack I made just for that <BR>>> purpose.</DIV>
<DIV> </DIV>
<DIV>My original suggestion was to store standAlone settings as a customProperty
of the standAlone builder, NOT the target stack. I completely agree with Richard
(and probably everyone else) that the SA should not modify the target stack.
Whether settings are stored as a customproperty or as a series of cards, I don't
mind, so long as I can choose past settings without having to re-type the
all each time!</DIV>
<DIV> </DIV>
<DIV>/H</DIV></FONT></BODY></HTML>