I did, and didn't come up with specific information related to the error message and specific circumstance that RobbieMor described, just git source code entries. I'm not new to the game here, it's about being frustrated that the only reference to this incrementing fee behavior was still only in this thread, based on my queries. When I googled some other iterations, I did find one other contribution in a thread from over a year ago that I'll have to track down and link to. It was the only instance that gave the practical advice of lowering the number of decimal places in the transaction amount, though that's obviously not a perfect workaround. I'll see what I can piece together to contribute to a more static, on-topic spot than this. The go-to link for most people,
https://en.bitcoin.it/wiki/Transaction_fees#Sending, just isn't helpful regarding this specific behavior of the client.
As far as practical enhancements, is there any possible feature that could be implemented into the client to offer the user a best case alternative, maximizing the best ratio of highest transaction amount possible to lowest transaction fee for the current wallet contents?
