Comment 3 for bug 488736
Revision history for this message
| Olivier Dony (Odoo) (odo-openerp) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
I understand the concern here, but I think having two fields editable is too confusing for users. It would even be better if we only needed to display one.
We have changed before between asking users to fill in the rate or fill in the factor, and nothing is satisfying everyone.
Perhaps we should do this differently and have something (wizard or text) more user-friendly that asks in english whether the new unit is supposed to be smaller or larger than the reference one, and by how much (e.g. 2x smaller or 2x larger, it would always be "2" you need to input: the intuitive amount the user is thinking of, and also the one with no rounding issue.)
BTW, a way to mitigate your specific issue without patch is to use an intermediary 70M unit as reference, so then you have 0.1 and 70 as the rates to use for 700M and M respectively. IIRC, the 70M UoM does not even need to be explicitly created if it's never used, it will be virtual.