> I'm a little bit disturbed by a "feature" of fdesign. It gladly
> overwrites anything that happens to have any of the names *c, *h
> etc. as the *fd file you ask it to save. Don't you think that an
> "xxxx exists. Overwrite?" would be a good idea? In combination with
> a "Save as" option. I just lost a few days worth of code because I
> accidently named a fdesign form the same as a source.
The current version of fdesign (0.86.1) saves any existing *.[ch]
files as *.[ch].bak, which at least gives you the chance to recover
from your error.
Personally, I think a "xxxx exists. Overwrite?" message would be quite
annoying since most of the time it will be something you wish to
overwrite, not keep. If this really is a problem (and I've been
bitten by it once early on myself) then a possible fix might be for
XForms to "sniff" the file first to see if it's header line is there
and complain if it isn't.
The best recommendation I can make is to establish a file naming
convention of some sort and stick with it. This eliminates a lot of
screwups. I like to always call my .fd file `project_forms.fd' where
`project,' of course, is the name of the program I'm developing. That
way I don't get namespace collisions.
spl
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
Xforms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/