Closing as fixed due to not being reproducable in Intrepid and later.
Please re-open if this bug re-occurs.
** Changed in: gcalctool (Ubuntu)
Status: Incomplete = Fix Released
--
512000 in Decimal, convert to hex is wrong
https://bugs.launchpad.net/bugs/254740
You received this bug
What locale are you using? This looks similar to bug 324451
--
512000 in Decimal, convert to hex is wrong
https://bugs.launchpad.net/bugs/254740
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gcalctool in ubuntu.
--
desktop-bugs
I cannot reproduce using the current latest available version on
intrepid (5.24.1).
--
512000 in Decimal, convert to hex is wrong
https://bugs.launchpad.net/bugs/254740
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gcalctool in ubuntu.
Is this issue still reproducible in the latest version?
--
512000 in Decimal, convert to hex is wrong
https://bugs.launchpad.net/bugs/254740
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gcalctool in ubuntu.
--
desktop-bugs mailing
When I convert from HEX to BIN it tends to drop the trailing zeros. For
exampel D4 should be something like 11010100 but it returns 110101. The
fun part is that converting it back* it returns D4 again. So internally
the result is stored correctly i guess.
*) Switching to and from using the
Thanks Mark. But even with bit editor turned on it is giving correct
results. I even tried changing the Precedence and other options. But
always gcalc gives me correct value. Have you turned on some other
option?
--
512000 in Decimal, convert to hex is wrong
Thanks for helping us make Ubuntu better. I tried reproducing this issue
but never really got the result you have mentioned. Its always been the
correct one. Tried meddling around with Fix, Eng and Sci modes also to
see whether there is any difference. Is it always reproducible at your
end? Were
For me this is reproducible every time I have tried. It is a bit
annoying. It is like the calculator removes the trailing 0's in hex mode..
Using the scientific calculator mode, I entered 512000 in decimal, then
switched the result to Hex. I got 7D, instead of the correct result
7D000.
Just noticed something else. I usually have the bit editor turned
on. I just tried it with the bit editor off, and I got the correct
result. Perhaps that will be a clue?
Aanjhan Ranganathan wrote:
Thanks for helping us make Ubuntu better. I tried reproducing this issue
but never really got
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/16531442/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/16531443/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/16531444/ProcStatus.txt
--
512000 in
10 matches
Mail list logo
