Just to point out about older Armory version still being linked in starting post. You should update link with one posted
here so
that eventual bug hunters who don't check whole thread first don't unneccessarily download and work on outdated version.
I need both versions tested. The stable version is perhaps more important for finding bugs, since a significant bug there will require a re-release. The testing version is expected to have some bugs, and is updated more easily. I added a link in that first post at the bottom (yesterday) that the "testing" version is now fair-game. Bugs reported in either one are valid, but not repeatable (if the same bug is in both, I will only give the bounty for the first report).
@OpenYourEyes -- I'll toss you 0.1 for that. Those are both errors that have been there for a while, and on a high-traffic page. For grammer, send it to me via PM if you think it's warranted. But I'm not going to really focus on the webpage too much, since it's constantly under construction.
@subSTRATA: Okay, so now onto your plethora of reports. This is where it gets fuzzy, because I can't give out 36 bounties for closely-related bugs. And also, some of these are very minor or due to a misunderstanding about the software. I have to use my judgment here, and say that anything that is exceptionally minor, but still warrants changing
something in the code is worth half the bounty. Also, things that are more of a "clarification needed" than a bug will get half a bounty.
(Each star* is a half-bounty)
(8*) It sounds like you have never run bitcoin-qt on this particular computer? Or it's in a non-standard location? Armory most definitely detects when Bitcoin-Qt is started later, but if it's never been started, ever, it can't re-check for blkfiles. Thus it only hits this condition when Bitcoin-Qt has never been started before. Please tell me if this does not match your experience. *But I have to give this to you, because it does warrant adding "...you may have to restart Armory" to catch this condition.
(9) This is not an Armory bug as much as a PyQt bug. And it's not something I can fix.
(10*) That's actually a very intelligent dialog, which gives you only the options available for your current state (the button text and enabled/unabled changes depending on what wallets you have and your online/offline state). Since you are offline, there is no way to create new transactions (hence disabled top button). Additionally, if you were online, the bottom button would say "Sign or Broadcast Transaction". If you actually have an offline/cold wallet, this makes more sense. I will modify the text slightly.
(11**) This is pretty much as-planned, except for the ability to save an empty transaction. I'll modify it. (either transaction type can be saved here, depending on whether what is in the box is signed or unsigned).
(12*) Meh. It's an OS-specific behavior that is sub-optimal. But I'm not quite sure how to fix it, nor do I know how to fix it. I'll give a 0.1 bounty for someone who does figure out how to fix it (it's Windows-only).
(13) That was an explicit decision due to space constraints. In expert usermode there is just no space to add those buttons, and the user can still escape with the X or by hitting ESC.
(14***) I'll count this as 4 half bugs: The red box should be reset after the error goes away. The Send-Bitcoins window should not even be accessible in offline mode (it is disabled in when scanning, but apparently not when simply offline). The -0.00000001 spendable balance obviously is in error. The "Create Unsigned Tx" button should be disabled in offline mode.
(15) This was intentional as the truncated version is all that is needed given the space constraints.
(16*) I suppose the address list could use a refresh here...
(17) "Empty" and "Unused" can only be evaluated when you are online. Armory doesn't know whether the addresses are empty or unused.
(18*) A clarification window may be warranted, but the overall behavior is as-intended.
(19) Does Notepad++ show links? It definitely creates links for me when I copy it into a word processor or email.
(20**) Okay, that's a real bug! I'll look into that
(21**) More-intelligent warning is warranted.
(22) Not all wallets have passwords. Wallet file could be deleted from the user's app directory without the password. I chose to use 31 consecutive warning dialogs instead. That's by design (especially if someone is deleting the wallet
because they forgot their password)
(23) Wallet name standardization is a good idea, but Armory was designed not to care. And the user rarely ever sees the filename or cares... as long as the word "watch" is in there. In my own testing, I don't see any behavior warranting code modification.
I count an extra 14 half-bounties here, for 0.7 BTC in addition to your 0.4 yesterday. If you dispute anything in particular please do so over PM or email and I'll update this post. I don't want to spam this list anymore. This is a lot of tiny things, but all of them together do add up to non-negligible polishing improvement.
This concludes 1.6 BTC worth of bounties. I've got 1.4 more, and I hope we'll find some higher-level bugs, too (although 20 was a good bug that might distract me for a bit...)
Of course I have Bitcoin-Qt on computer, you could see that in log file attached to my first post. Client is installed in default