upstream comment "> Lower case 'a' to 'f' characters are misinterpreted as shortcut keys(?) in > Scientific mode instead of hexadecimal values. Uppercase 'A' to 'F' needs to > be > input to have it interpreted as hexadecimal value. If it's not a bug, then > it's > a highly annoying and misleading feature.
Time to get out HCI guy on this to have a final say. See also bug #455889, where a similar topic came up. Adding Calum to the cc: > Also the calculator accepts hex input even in Decimal mode. > The user should at least be warned of this 'feature'. Please describe what you are seeing here. If you enter hex numbers in decimal mode in Operator precedence mode and hit Return, you get: "Invalid number for current base" in the status bar at the bottom of the window. What were you expecting to happen? Note that in left-t-right arithmetic mode in Decimal mode, you can't enter hex numbers at all, so perhaps you were expecting something similar?" -- Hexadecimal input is not intuitive https://bugs.launchpad.net/bugs/133915 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
