Author

Topic: Sorry for the mass amounts of requests, but, another request (Read 1003 times)

full member
Activity: 238
Merit: 109
Just so you know, the main ledger does use address comments.

You mean the main transaction list you get when you first start the client? I know it does, and, because of how useful it is, I find it hard to work without it. Memorizing a bunch of BTC addresses is a lot harder than reading English that you wrote earlier. Tongue

I can look at adding it to the tx viewer, as well.  Though, that table is already cramped enough.  I guess you'd ideally be able to customize which columns you want.

That would be the best, most 'flushed out' applications allow you to simply right click the columns and add/remove them, also drag them around, etc..., but, it could be as simple as a check box in the settings.
legendary
Activity: 1428
Merit: 1093
Core Armory Developer
Just so you know, the main ledger does use address comments.  It first looks for a comment associated with the tx ID.  If there isn't one, it looks for the comments associated with any of the output addresses and displays that. 

I can look at adding it to the tx viewer, as well.  Though, that table is already cramped enough.  I guess you'd ideally be able to customize which columns you want.
full member
Activity: 238
Merit: 109
Two requests, one larger, one smaller.

Request #1 (larger) is to have a column for 'address comment' (Which would be imported from the comments on addresses in the wallet) when sending payments:-


Request #2 (A lot smaller) is to have the output appear before the input on the transaction log when sending bitcoins to yourself between wallets (I have an online and an offline wallet, online = spending money, offline = long-term):-


It's only logical you send the money, then you receive it. You don't receive it, then send it. I know it's ordered in the of which the backend of the software is aware of said transactions, but, it really needs an override for this scenario (Which I can only assume isn't just mine).
Jump to: