Quote from: dnotespool on October 18, 2014, 06:27:16 AM

Quote from: DNotes on October 18, 2014, 12:43:27 AM

Quote from: dnotespool on October 17, 2014, 08:16:13 PM

Quote from: DNotes on October 17, 2014, 02:34:38 PM

Quote from: mrbum805 on October 17, 2014, 05:08:55 AM

so i managed to send all my coins to my wallet the day before the shut down successfully. I knew something was wrong when a coin i sold and re-bought in another was back and my btc balance was negative. weird. anyway can you have 2 different wallets within the dnotes wallet. or in other words so i can keep my coins separate? that would be a cool thing to have. i dont know how many people would actually use that feature besides me however.

It is possible but not easy to manage at the moment. Basically you would have to manage two different wallet.dat files.

Is it possible now? I tried using the -datadir=C:\MyWallet2 but it just popped an error that it couldn't put a lock on \AppData\Roaming\DNotes location - "DNotes is probably already running"

So I went searching in case I was just using the command line options incorrectly. Ran across a thread that someone was saying that a "-walletdir" option would be a nice feature. Which, it probably would be.

Even if -datadir= worked correctly (maybe it does and I am just doing it wrong), that would mean a whole second directory for everything, including all the blockchain/db files. Although I don't know if two separate running versions could access the blockchain/db simultaneously...In which case a -walletdir option would only be useful to place wallet.dat somewhere outside the datadir, though still allowing the ability to launch DNotes-qt with the wallet of your choice.

But that could be a nice feature in itself. Still only allow one instance of the interface, still using only one set of blockchain/db files. But a command line option, and preferably like a File menu submenu and/or popup panel, to select from any number of different wallets, maybe with even a feature to label them with the default wallet being like "Main (Default)" and I could label another "Retirement Fund", and another "Vacation Fund", etc....

I would guess, like when I was messing with the source looking into an interface to reset the blockchain files, changing a wallet from with the UI would probably have to make it relaunch itself using the selected wallet in the new -walletdir option.

But yeah, that would be nice, even if logistically it would have to create/use completely separate datadir if specifically only setting a -walletdir wouldn't work. It would just be even nicer only having to keep one set of blockchain data instead of a copy for every individual wallet you wanted to setup.

Just for the sake of testing, I was able to create a batch file that ran the following command:
dnotes-qt.exe -datadir=C:\MyWallet2
I had to create the C:\MyWallet2 directory prior to running the bat file. It did run both instances of the wallet, one with the regular data directory, and one using C:\MyWallet2. However, I can't really recommend running the client that way, as I don't know if that will create any problems. Although it has not created any noticeable problems for me yet.

See, I said I might have just been doing it wrong

But actually, I wasn't. My 2nd data directory did exist. So it wasn't a non-existant directory error. So my -datadir was a real directory that was not the AppData directory, but it still said it couldn't get a lock on the AppData (default) directory.

Maybe running it from a batch file changes something? I just typed the exact same thing you did from a DOS prompt and it still assumed AppData directory, not the -datadir I specified.

However, it that worked for you, I would certainly recommend it. Because that's what you're doing, running two completely different instances. Not just different wallets, but also different blk.dat files. But - that's what the whole "syncing" is. The only difference between your default wallet and your MyWallet2 is ONLY the wallet.dat, the rest is just network stuff.

Which yeah, as is, when you open now default wallet, it has to resync those blk00# data. Then later you open up MyWallet2 and since it's a whole separate datadir, it has to update it's blk00# files too. So you now have two copies of the blockchain data, and two wallets. Rather than two wallets using the same blockchain data, which IS the same data.

So the same suggestion applies. If it HAS to be whole new data directories for each wallet, it would still be a nice feature - just data space * number of wallets. Just saying what would be even nicer... data space * 1, just able to say which wallet you want to work with.

Yeah, I'm sure the issue you are having is different. Your error leads me to believe it is ignoring your datadir switch for some reason.

Your suggestion is spot on though. That eliminates a lot of potential issues.