I've been using Salive from before version 1.. It use to be able to fit on
a floppy disk. Dirk has done wonders adding to the program. You see almost
very day someone asking for this little program to do something new. It
seems (to me) that we want Salive to do everything and more. We have
forgotten to do something ourselves. I'm not picking on your idea, it's
just that I'd hate to see the program get out of hand with new things being
added. If your adding new checks, why not add all you checks and then save
them before you do a test of each check. That way if something should
happen you'll have all your newly added checks and maybe just have to edit
a few that are not giving the correct response.
At 04:32 PM 8/7/03 -0500, you wrote:
>I have had this happen after adding 45 monitors (application crash that is).
>This product however stable under normal production conditions seems to be
>susceptible to crashes every now and then (particularly when adding or
>editing entries). I think it would be wise to have some sort of disaster
>recovery (like an autosave). Either after clicking update on the entry or
>at an interval specified in the setup. I think a little feedback form the
>group would be helpful.
>
>PS It used to be in the days of windows 3.1 and Windows 95 we were
>accustomed to automatically saving our work every few minutes. In the midst
>of automation we (including myself) have lost sight of this little gem and
>tend to blame others for our problems. SAVE MORE OFTEN. However in theses
>days of automation and bigger, better, more robust applications I see no
>reason the application cannot do some of the work for us (isn't that the
>point?).
Regards,
Gene
[EMAIL PROTECTED]
http://www.eclipse.net/~njkat
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
unsubscribe SAlive
