Fatal software bug? - Printable Version +- HP Forums (https://www.hpmuseum.org/forum) +-- Forum: HP Calculators (and very old HP Computers) (/forum-3.html) +--- Forum: HP Prime (/forum-5.html) +--- Thread: Fatal software bug? (/thread-17776.html) |
Fatal software bug? - Lakeboard - 12-01-2021 11:50 AM Hello, everyone If I copy a result from an earlier calculation on my HP Prime calculator, it will be copied incorrectly. Is that my fault? RE: Fatal software bug? - KeithB - 12-01-2021 03:00 PM Can you show us a screenshot? RE: Fatal software bug? - Lakeboard - 12-01-2021 07:43 PM Hello KeithB Many thanks for your response. In my main post I have included a "gif" in which the problem can be seen. Since this might not be displayed correctly, I added a picture here: https://i.ibb.co/16jbvvz/HP-Prime.png RE: Fatal software bug? - StephanP - 12-01-2021 08:19 PM In what sense would this be fatal? Okay, the parentheses got moved. But that did't break the value or the consecutive calculation, did it? I don't see anything going fatally wrong here. RE: Fatal software bug? - Lakeboard - 12-01-2021 08:44 PM Hello Stephan P. Thank you, too, for your answer. It really doesn't look too bad at first look. But the position of the parentheses is important. Let me show you: RE: Fatal software bug? - ijabbott - 12-01-2021 09:20 PM It seems the "Intelligent Math" option isn't very intelligent. :-) The strange thing is that with "Entry: Algebraic", Textbook Display: [ ]", "Intelligent Math: [x]": (10^(1/4))^3 => 10^(1/4)^3 which is incorrect, but with "Textbook Display: [x]" it gets displayed as: \(\left(10^\frac{1}{4}\right)^3 => \left(10^\frac{1}{4}\right)^3\) which doesn't match the incorrect non-textbook display, even though the incorrect non-textbook display is what gets copied when selected. RE: Fatal software bug? - StephanP - 12-02-2021 07:03 AM (12-01-2021 08:44 PM)Lakeboard Wrote: Let me show you: Ah, my bad. I overlooked the exponent 1/64. Probably a bit fuzzy in the early morning, I was. I cannot reproduce this on my Prime, though. Which firmware version are you using and particularly what settings do you use in Settings page 1 and 2? RE: Fatal software bug? - StephanP - 12-02-2021 07:16 AM Ah, got it. It's the option Intelligent Math on Settings page 2. (I've not used this before) Well, that's definitely something the team wil have to look into. RE: Fatal software bug? - Lakeboard - 12-02-2021 02:21 PM Many thanks for your help. Especially for checking @ ijabbott and Stephan. Apparently, it is really a software bug. So what can we do to report this issue and receive a new firmware update? I tried to contact my local HP office. But they didn't respond. RE: Fatal software bug? - StephanP - 12-02-2021 03:49 PM I've reported the issue with the product manager. As to the release of a solution it's wait and see. RE: Fatal software bug? - Lakeboard - 12-03-2021 06:00 PM Thank you, Stephan, for reporting. That’s really great! Let's hope that there will be a new firmware soon and that the problem will be resolved. Stephan, I may have discovered another little thing. In CAS mode, if the imaginary number is a floating point, the angle is output as radians. Can you also report this? Unless it is intended. But it doesn't seem that to me. Here is a picture: RE: Fatal software bug? - ijabbott - 12-04-2021 04:53 PM That arg() bug seems to be in the Giac/Xcas code, so one for Bernard Parisse to look at. Here is a giac session running in a Linux terminal. The angle_radian variable seems to have changed from 0 to 1 by itself after arg(5+6.001i) Code: // Using locale /usr/share/locale/ RE: Fatal software bug? - KlaasKuperus - 12-06-2021 08:20 AM (12-02-2021 02:21 PM)Lakeboard Wrote: Many thanks for your help. Especially for checking @ ijabbott and Stephan.Thank you for noticing. We will add it to the bug tracker and work on a solution asap! RE: Fatal software bug? - parisse - 12-06-2021 11:28 AM There is indeed a bug, now fixed in giac source, thanks! RE: Fatal software bug? - Lakeboard - 12-06-2021 07:30 PM Many thanks to KlaasKuperus and parisse. It is incredibly nice that such bugs are fixed and that the product is actively developed and supported. It's a great service to the community. Thank you very much! =) Together for a great product. Also thanks to ijabbott for specifying the complex number problem. |