|
Well, the program is smart enough to put an * next to changed source. So an autosave could just check for the changed members and save those.... Ron Power Programmer Information Services City Of St. John's, NL P.O. Box 908 St. John's, NL A1C 5M2 709-576-8132 rpower@xxxxxxxxxx http://www.stjohns.ca/ ___________________________________________________________________________ Success is going from failure to failure without a loss of enthusiasm. - Sir Winston Churchill "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 2005/08/26 10:47 PM Please respond to Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx> To "'Websphere Development Studio Client for iSeries'" <wdsci-l@xxxxxxxxxxxx> cc Subject RE: [WDSCI-L] V 6.0 - Lost all my changes > From: Dave Murvin > > > My question is that since I am working off line in a workspace, why can't > WDSC figure this out and recover the changes from the workspace? Is there > some setting I have overlooked? Nope. If enough people ask for an auto-save feature, maybe they'll add one. I think the biggest problem with that is that people tend to open dozens of members. The auto-save will have to be pretty smart. But still, it's not that big a deal; if Microsoft can do it, anyone can do it. > Another question is why did the entire WDSC end when I tried to interrupt > the long running job by closing the window for the About Screen? Seems > kind of harsh to me. The problem is Windows was doing the killing, and it kills the whole damn JVM. Frankly, I'm not too certain how you would go about killing a single view of the IDE, but I'm pretty comfortable you can't do it from Windows. Rule of thumb: killing things is always a risky business. > Thanks. Just kind of venting here. Yup. It sucks. Got the T-shirt.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.