CintaNotes Forum

I place the DB in a TrueCrypt-Folder on e.g. Z: and after dismounting TrueCrypt Z: is not any longer available. Launching CintaNotes fails, cause Z: not accessible. I cannot launch anyhow and I have to force set the drive back and then change manually.

As a workaround I would suggest to test if the drive is present and if not, take the drive from which the app was launched!

WinXP, CintaNotes 1.6

Hi,

yes I confirm this problem.
However it is not quite clear what correct behavior would be. Would it be ok to create a new notebook and load it?
CintaNotes can't have no notebook loaded.

Let me intrude here, as this might impact the portability of CintaNotes: I guess the creation of a new notebook is OK, as long as the user is warned this is happening because his prior location is unavailable and confirmation is given to proceed. With the commercial version ability to open multiple notebooks, this is almost a non-issue; nonetheless, it has the potential to counter wider adoption of the freeware in conditions where you have unsophisticated users mucking about with paths/drive letters...

How about the following behavior:

Display a warning that the notebook is not available and the following options:
- Open one of the recent notebooks (if CN is registered)
- Create a new notebook
- Retry loading current notebook
- Exit the program

You have listed all options i could think of Sounds good to me.

Thomas

My 2Cents:

1st cent: I already mentioned how I would expect a *default* behavior (which would work as well in a portable version)
2nd cent: When I launch CintaNotes and the DB has been moved to some other location then CintaNotes does NOT crash at all. There is already a working behavior. May I suggest to have some kind of *consistent* behavior? i.e. as soon as the DB couldn't be found, either moved, Volume not any longer there, or even complete NEW installation ==> always the same.

My 2 cents for it...

May I give one more?

The option with
- Retry loading current notebook
seems from the user point ridiculous. Why? First of all, I do NOT memory all the time what was my last one. Second, if you wanna display the path, it might get verrrrrrrry long, and last but not least,
there is some kind of reason why the db is missing. Iffff I could fix it, then I would relaunch the app. So, why a retry? Why not simply offer the choice 'Open a Notebook' instead.

Don't know, if you appreciate my 3cents instead of my 2...

Roland, I think you are right.. there's no reason to create a complex GUI for such an edge case - it's simply not
worth it. 3 options to 1) create a new notebook 2) open an existing 3) exit should be quite enough.