Ok, I found something that's broken. When I try to sign a message with a key that's in a watching only wallet, it crashes hard with this in the debug log:
Well then, don't do that!
To be fair, it sounds like I need to put some more protections on some of the dialogs when the user is using a watching-only wallet. I thought I had caught a lot... but I guess not yet. Getting people to test has been hard, so I keep finding stupid stuff like this that has been in there months. Perhaps I need to start offering 0.1 BTC bounties for finding bugs in the software -- I bet I'd get a lot of people digging in hard! Or I might go broke...
What about killerstorm's changes to support colored coins? Might those be a starting point?
He actually already contacted me and I suggested that there will be room in the new wallet format for including "extra attributes" with the addresses. I don't plan to mess with colored coins myself, but it might make it easily extensible by others.
Armory does not support coin-control, but I think it will not be terribly difficult to support. I just have some other priorities. I *do* plan to add it when I'm feeling stuck with some major other feature upgrade
damnit, im looking for such a client :S and i really like armorys design.
You're not the first person, by far, who has asked for this. I suppose I could bump it on the priority list for after beta -- because not only is it in high demand, I don't think it will be that hard. I think I already know how to do it, I just need to devote a day or two to implementing and testing. Luckily, the underlying libraries already have all the hooks I need (I just create a new wallet in RAM with only the specified addresses, and retrieving its balance and creating transactions with it is trivial). And I think I already know how to create the window to let you select the set of addresses from which you want to spend coins...
Maybe I'll do it this weekend! I am already kinda stuck with the new wallet format, while I wait for feedback about
my design ideas...