I'd like to report a minor bug.
When I set a buy order by clicking on the balance button to enter the max amount it enters a long decimal number which appears to be either too long for the system to handle, or which pushes the amount above the available balance. I get around this by clicking on the balance button to fill the amount field automatically & then deleting just the very last decimal in the amount to purchase.
ie, If the amount is entered as 10,000.123456 then by deleting the final 6 the transaction will go through.
Obviously this is not a huge thing, but seems like it would be easily fixed. Could you look into it sometime? I have only experienced it with the Digibyte market but I assume it is probably a system wide thing.
Cheers.
Yeah its an issue with precision on the client side.When I set a buy order by clicking on the balance button to enter the max amount it enters a long decimal number which appears to be either too long for the system to handle, or which pushes the amount above the available balance. I get around this by clicking on the balance button to fill the amount field automatically & then deleting just the very last decimal in the amount to purchase.
ie, If the amount is entered as 10,000.123456 then by deleting the final 6 the transaction will go through.
Obviously this is not a huge thing, but seems like it would be easily fixed. Could you look into it sometime? I have only experienced it with the Digibyte market but I assume it is probably a system wide thing.
Cheers.
Good news is that we dont use floating-point numbers on the database at all, everything is integers (max precision).
UI issue will be fixed in the near future.
great! look forward to it..
