Mel, agree. Greg, you may not call it a bug, because it is somewhat intentional, but it is a improper way to implement a protection schema. I am from the software industry and I would have endless problems with customers if my application would lead them to loose data.
My 2 cents Fred PY2XB On Mon, 19 Oct 2009 13:36:37 -0400, Mel <ve...@videotron.ca> wrote: > No... it is the programmer's responsibility to protect you from this. > Paul made the decision to protect his software by the Draconian measure > of disallowing saves. It should be absolutely IMPOSSIBLE for a > registered user to find themselves in this situation where the loss of > data is inevitable! > > Gregory Brown wrote: >> Hi Mel, >> >> I can understand your frustration, but if the "demo mode" problem I had >> actually was caused by my inadvertently opening two sessions of the >> program simultaneously, I wouldn't be so quick to call it a DX4WIN >> bug...it's probably more of an operator-error, Windows system-error >> issue, which I intend to avoid assiduously in the future! If, on the >> other hand, the same thing happens spontaneously without any apparent >> provocation, then perhaps it would be (was?) something Paul could fix. >> Personally, this is the first time I've ever experienced this in many, >> many years of using DX4WIN...so I've never seen it happen without the >> double-open, operator-goof that I just performed. And the loss of data >> was my own fault. A simple hit of the "Print Screen" key would have >> saved an image of my displayed log which I could have re-entered. >> >> DX4WIN is still at the top of my list of logging programs, no question. >> >> Greg KTØK >> >> >> >> >>> -----Original Message----- >>> From: Mel [mailto:ve...@videotron.ca] >>> Sent: Monday, October 19, 2009 10:01 AM >>> To: Gregory Brown >>> Cc: dx4win@mailman.qth.net >>> Subject: Re: [Dx4win] Unexpected "Unlicensed Demo Version, >>> Can't Save" problem >>> >>> >>> If that's the bug that plagued ver 7... you could not have >>> "saved" your >>> log... once in "demo mode" DX4Win will not allow you to save or even >>> export your log which only resides in memory. I am truly >>> sorry to hear >>> this bug still exists. In ver 7 this bug would rarely manifest itself >>> without any operator error. It may not happen often (twice in about 5 >>> years for me) but it results in lost data which is intolerable. I had >>> suggested that Paul create a transaction log to recover from such >>> problems, but it wasn't implemented in ver 8. Personally... if I lose >>> data one more time with DX4Win... I'm done with it... nonetheless I >>> remain hopeful. >>> >>> Mel, VE2DC >>> >>> Gregory Brown wrote: >>>> This likely isn't a bug, but is something to be aware of. >>>> >>>> Yesterday upon exiting DX4WIN 8.02 and answering "yes" to the "Log >>>> Modified, Do You Want to Save" dialog box, I received the error >>>> message that I was using an unlicensed demo version and the log >>>> couldn't be saved. Very stupidly thinking it meant nothing >>> because I >>>> knew it was licensed, my finger reflex hit the exit button and >>>> zap...the day's QSO's were gone. >>>> >>>> The only thing odd about this logging session was that it >>> began with >>>> me double-clicking a DX4WIN shortcut icon in my quick-start >>> bar (which >>>> should have been single-clicked) and two DX4WIN sessions >>> tried to open >>>> at the same time. One failed (giving an error message) and >>> I exited. >>>> The other one started successfully so I simply left that >>> one running >>>> and used it. >>>> >>>> Assuming this was the cause of the "unlicensed demo >>> version" warning, >>>> I have some suggestions: 1. If you are a habitual double-clicker, >>>> eliminate your quick-start single-click shortcuts. >>>> 2. If you accidently start two sessions simultaneously, >>> exit BOTH and >>>> start again. Then test the session you are using to make sure it >>>> recognizes your license. >>>> 3. If your computer tells you something, LISTEN! Just >>> because YOU know >>>> something doesn't mean your computer does! >>>> 4. If you get the "demo version, can't save log" message, >>> don't ignore >>>> it...make a hard copy of your changes before exiting, either by >>>> capturing a screen dump or by printing the modified portion >>> of your log >>>> (if the program lets you). >>>> >>>> >>>> 5. If you contacted KTØK on late 18 October thru early 19 October >>>> UTC, drop me an email with the QSO info!! >>>> >>>> Greg KTØK >>>> >>>> >>>> ______________________________________________________________ >>>> Dx4win mailing list >>>> Home: http://mailman.qth.net/mailman/listinfo/dx4win >>>> Help: http://mailman.qth.net/mmfaq.htm >>>> Post: mailto:Dx4win@mailman.qth.net >>>> >>>> This list hosted by: http://www.qsl.net >>>> Please help support this email list: http://www.qsl.net/donate.html >>>> >> >> > ______________________________________________________________ > Dx4win mailing list > Home: http://mailman.qth.net/mailman/listinfo/dx4win > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:Dx4win@mailman.qth.net > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html ______________________________________________________________ Dx4win mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Dx4win@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html
