My only disappointment so far is learning that my calculator hardware was falsely advertised as having wireless capabilities when the calc came out, that would came out in later OSes, only to now learn that my hardware just doesn't support wireless capabilities at all.
Can you please enumerate where you felt this was advertised?
On a side note, is the missing Send button in the emulator because all transfer abilities were moved to the connectivity kit or is this just a bug?
It was very confusing having the "Send" button when there was nothing you were connected to at the moment. Select which unit you are trying to connect with from the Connect To dropdown, and then it shows up.
Could you add some details on what features are planned?
Unfortunately, no.
HP does not allow any future information of any kind to be given. Any questions around "what is coming", "what has been fixed", "when", etc are forward looking statements and are not allowed. It is extreemly common for companies to work that way. In fact, many companies don't allow *any* communication of any kind except by an autorized communication person and hence it is just a bag of silence.
Excluding all possible legal issues, how would you feel if someone said "<insert thing here> is going to be fixed in the next release" or "We are adding <feature Y>" and then it didn't come out like was stated? Perhaps the issue ended up being more complicated then expected or in testing it was determined the fix wasn't complete. Maybe the people who needed to work on it had to work on something else. Maybe it was decided to roll it into another release with similar things. Etc.
For your emulator, calculator and connkit. Easiest way to get them is to use the check for update mechanism in the emulator or connkit.
The primary focus of this release in terms of new features was improvement of geometry and statistics. The primary focus of the connkit was around the main UI (not the editors for specific object types which were essentially untouched).
Four chapters in the user guide were changed, however they could not be rolled directly into the original document and are instead a "supplement" for now. The emulator has them, but they are attached to the end of the existing manual brought up by selecting Help->User Guide in the emulator windows menu. If you'd like the separate "supplement" file, it should be up on the HP support page shortly.
Spoiler For Release Notes:
Quote
HP Prime – Release Notes -------------------------
Description ----------- This release of the Prime Calculator firmware and associated PC software delivers significant new features and fixes outstanding issues. This document is not a complete list of all changes, but highlights specific items. All users of the HP Prime calculator are encouraged to upgrade for the best possible experience.
Backward Compatibility ---------------------- There is limited backward compatibility between this and earlier releases.
Older Prime hardware (Revision A) does support this release, however the wireless, unit-to-unit, and data streamer functionality is not supported on earlier models. In the Help->About HP Prime screen the hardware revision will be displayed along with software version information. Mixing and matching software revisions is not encouraged and may cause unexpected results. Users are strongly encouraged to first backup their calculators with the older firmware and Connectivity Kit - then upgrade all their calculator software (firmware, Connectivity Kit, and Virtual Calculator). Upgrade the Connectivity kit first, before upgrading your calculator firmware. This order will produce the best experience.
The geometry application and inference have received significant updates and earlier data files will not be compatible. Old data files from earlier revisions will not load and and a new empty data file will overwrite the old one.
Due to some specific issues resolved, certain user programs may not run on the new system without changes first. Specifically, any commands with the Σ character in the name may need to be corrected to use the correct sigma character. Function variables will now also error if the function parameter is using a reserved system function name (example: SIN or COLOR). Additionally, the TRIANGLE commands were modified to allow TRIANGLE, LINE and FILLPOLY to share similar data and syntax to enable easier creation of complex 3D drawings
New Functionality (Connectivity Kit) ------------------------------------ 1. Application has had major improvements to the user interface. Please refer to the included connectivity kit User's Guide for instructions and details. 2. Support for the HP Wireless Classroom network has been introduced. Please see http://www.hp.com/calculators/ for details on the Wireless Classroom kit. 3. Greatly enhanced communication speed over USB link to calculator.
New Functionality (Calculator Software) --------------------------------------- 1. Improved touch support throughout system. This includes pinch to zoom support in graphing applications, and kinetic scrolling. 2. Pressing HELP in an open command line will attempt to find the name of a command based on the prior input up to the cursor position to display system help for that command. 3. Includes Edition 2 of the on calculator help files (English only in this release). 4. Greatly enhanced robustness and capability of the Statistics 2Var logistic fit. 5. Wireless support for capable units turned on. Wireless icon will appear in the right top corner menu for units that can support the HP Prime Wireless Kit. 6. Calculator unit-to-unit communications has now been enabled on units that can support it. 7. Numerical values now can be displayed with digit groupings. Examples include: 1,234.567 1 234.567 and 1’234,567 8. Two new numerical display formats have been introduced. These are “floating” which only displays up to a specified number of digits, and “rounded” which is similar to the “fixed” format except trailing zeros are suppressed. 9. Decimal fractions now appear with a zero, as in 0.25. 10. Vectors are now displayed as a single line object until they become a matrix. This aids in distinguishing vectors and matrices. 11. User selectable first day of week setting for use through the system. 12. First boot unlock and settings wizard. User will be asked to confirm language selection and some initial settings. 13. Inference application now can do Chi-Square calculations and Linear Regression T calculations. 14. Geometry application has been completely redone and is much faster, consistent, and capable than before. 15. Enhanced color pickers allow a greater range of color selection. 16. Pressing ENTER will now open chooser in a dialog or toggle checkbox. 17. Enhanced unit object display to ensure a more standard form with complex units. 18. TRIANGLE, FILLPOLY and LINE commands can now draw multiple objects in a consistent way with each other. Useful for very complicated 3D drawing in user programs. 19. INPUT command can now create multi-page dialogs and contain choose boxes, check boxes and grouped check boxes. It can also allow specific item types and gives control of parsing behavior for input. It also supports size and position control.
New Functionality (Virtual Calculator) -------------------------------------- 1. A horizontal skin has been included for use with monitors that are restricted in the vertical pixel range.
Resolved issues and changes excluding CAS ----------------------------------------- 1. Resolved issue with statistics 2 variable trig fit causing poor curve fit. 2. Resolved issue with removing last row or column from a CAS matrix in the matrix editor. 3. Resolved issue with .^ and ./ function calculations. 4. Resolved issue with EDITLIST/EDITMAT commands not working in RPN mode. 5. Resolved issue with BLIT command when specified destination was a zero sized region. 6. Resolved several issues with fraction key in home to make behavior more consistent. 7. Resolved issue in 2D integral template where EEX key would always add a 1 before the E in the evaluation limit locations. 8. Resolved several issues where integer only settings fields would display using the current display setting. 9. Resolved issue where auto power off did not function in graphing applications. 10. Resolved issue with commands EDITLIST and EDITMAT using user defined variables. 11. Resolved issue with key buffer not being cleared when the user aborts a running program. 12. Resolved issue with auto off timer in plot gallery not being reset on user touch. 13. Resolved issue with auto-off timer in plot gallery not being reset on user input. 14. Resolved issue with copy and paste in spreadsheet. 15. Resolved issue with sigma character in command names not being consistent through entire system. 16. Resolved issue with RETURN call inside repeating loop in a user program. 17. Resolved issue with object printing in debugging interface causing unpredictable behavior. 18. Resolved problem with integration calling ABS(F1(X)) 19. Resolved issue with G0-G9 in user programs while spreadsheet was active application. 20. Resolved issue with 10 second periodic wakeup during sleep reducing long term shelf life. 21. Resolved issue with KWh in menu needing to be named kWh to function properly. 22. Resolved issue where storing a number to a vector padded with too many zeros. 23. Resolved issue with clicking EDIT menu after deleting last CAS object from memory manager catalog. 24. Resolved issue with negative and STO conversion shortcut. 25. Resolved issue where tapping an item in Advanced Grapher Symbolic view behaved differently then tapping edit menu key. 26. Resolved issue where calculating integration with boundary at 0 appeared to fail. 27. Resolved issue with case sensitivity in note and program catalog. 28. Resolved issue where changing font size could cause strange artifacts in 2d equation display in Symbolic view. 29. Resolved problem where copying .+ or .- operators would not insert space before commands. 30. Resolved issue with ΣLIST and a vector argument. 31. Resolved some issues with F1 and CAS interaction. 32. Resolved issue with the UNITS -> TOOLS menu commands not evaluating immediately in RPN mode. 33. Resolved issue with eigenvectors of diagonal matrices in home. 34. Resolved issue where DMS toggle on home screen did not work with certain numbers. 35. Resolved issue with RPN stack not being cleared by a clear in memory manager. 36. Resolved issue where changing HEX or other similar settings did not update stack display immediately. 37. Resolved issue where clearing memory from catalog did not clear Ans variables. 38. Resolved issue where pressing BKSP on a CAS variable from chooser did not delete it. 39. Resolved issue where CAS screen would have left/right alignments disrupted after a power cycle. 40. Resolved issue with logb and very tiny values.
Resolved issues and changes in CAS ---------------------------------- 1. Resolved issue with for desolve([y'=sqrt(y),y(1)=1],x,y) 2. Resolved issue with units in approx mode and auto simplification on units 3. Added check for real matrix in SVD 4. Resolved issue with tlin(cos(a)*cos(b)) and with plot(exp(-x^2)) 5. Resolved issue with odesolve in reverse time direction 6. Desolve now handles linear system with constant coefficients; for example, desolve([y'=[[1,2],[2,1]]*y+[x,x+1],y(0)=[1,2]]); 7. Resolved issue with int(surd(2x,3),x,0,4), and with simplify(sin^2+cos^2) 8. Improved display for some sqrt results like sqrt(2+sqrt(3)) as sqrt(2)/2+sqrt(6)/2 9. Resolved issue with speed of int(x*exp(-x^2),x,0,100) 10. Resolved issue with derivative of composition e.g. (g(x^2))' 11. Resolved issue with desolve([y''-2*y'/x+(9+2/x^2)*y=x*exp(x),y(pi/6)=0,y(pi/3)=0],y) 12. Make SVD (SVL) work on rectangular matrices. 13. Change interpretation of A/B where B is a square matrix to inv(B)*A with a warning 14. Resolved issue with integer factorization. 15. Make limit(1/x^2,x,0) return +infinity instead of unsigned infinity 16. Resolved issue with laplace(exp(a*x),x,t) 17. Resolved issue with ilaplace(exp(-3x)) 18. Resolved issue with sigma notation 19. Resolved issue with sign (-> also fixes laplace(x)) 20. Make ifactor return an error if number too large 21. Resolved issue with recursion issue in geometry objects evaluation 22. Resolved issue with inv((5.+8i)^200) 23. Resolved issue with tan(54) in degree mode 24. Resolved issue with matrix/vector * object, if one arg to * is approx, evalf the other one with current context modes (instead of null context). 25. Extend cholesky to hermitian complex matrices 26. Resolved issue with ifactor(nextprime(alog10(17))*nextprime(alog10(19))); 27. Resolved issue with collect(sqrt(4x^2)) and for solve(-x+1=surd(-x^3+7,3)); 28. Resolved issue with int(int(sqrt(x+y),x,0,1),y,0,1) 29. pa2b2(2) now returns [1,1] 30. legendre_symbol and jacobi_symbol now accept negative first argument 31. Resolved issue with algebraic extension with i inside 32. op added to list of non auto simplified operators + dichotomic search 33. Default interval changed for parabola 34. Make left and right accept an integer represented as a double as 2nd argument 35. Set max list size to 10 000 and compute factorial exactly up to 1000 on hardware 36. Resolved issue with hadamard on numeric matrices 37. Size limit check added for $, Ans support for SCALE/SCALEADD/... 38. Resolved issue with re/im/abs e.g. im(sqrt(x)+1) 39. Size check added for JordanBlock, fix for solve with fractional powers, 40. Resolved issue with iPart with neg argument 41. element added to the list of functions that should not be auto simplified 42. RANDMAT with one argument accepted. 43. Changes for triple matrix norm (l1norm, l2norm, linfnorm) 44. Resolved issue with resultant with num coeffs 45. mat2list sets HP list subtype for the result. 46. Resolved issue with plotfunc(normald(x)) 47. area now accepts a function plot as first argument, 2nd argument a..b, or 2nd argument a, 3rd argument b, returns area under curve. For a parametric plot, a and b are the parameter range. 48. ifactor check added for qsieve failure 49. Resolved issue with ARG in degree 50. Resolved issue with fPart/iPart for negative/complex arguments 51. Resolved issue with asin(sin(pi))) and acos(cos(pi)) in degree 52. Change for [] in CAS: start at 1 53. Resolved issue with definite integral with inf boundary in degree mode 54. Replace warning by error for recursive definition except for when/ifte/program 55. Improve non-directional limit, e.g. limit(1/abs(x),x,0) 56. Enable for and if as lowercase synonyms for FOR and IF in the CAS. 57. Make REDIM and REPLACE (CAS version) accept a matrix instead of a variable name as 1st arg. 58. Resolved issue with regroup(inf) and for FP 59. Resolved issue with poisson_cdf with 3 arguments 60. Resolved issue with circle tangent, using relative error instead of absolute error. 61. Handling of inequalities with approximate coefficients using an exact conversion 62. jordan for numeric matrix with exact coefficients but no exact eigenvalue converting to approx. 63. Resolved issue with assume(s<0); sign(s) 64. Tangent for conics now use rational parametric equation 65. Resolved issue with a%%b if b is not an integer 66. Resolved issue with locus, fix for table print/parse 67. Resolved issue with l2norm 68. Re-set angle mode in isopolygon. 69. Leave propfrac unsimplified 70. Make sum eval approx if exact mode is not checked 71. Boolean operators now return 1/0 72. Resolved issue with col, suppress and makemat (indices starting at 1) 73. Better handling for some 4th order equations. 74. Set complex_variables to false in arcLen so that arcLen(x^2,x,0,1) works if Complex is checked. 75. Additional check for duplicate argument name in CAS program exit.
Important Note: If you updated your hardware unit before Thurs, May 29, GMT-6 please redownload and update your Prime firmware.
1. Delete the "My Documents\HP Connectivity Kit\Temp" directory, and "HP Connectivity Kit\Firmware" directory. 2. Run the check for update again. It will re-download the firmware zip file from today. 3. Reinstall on your unit using the new files.
What would be cool as well is if images could be rotated.
The problem with this is how you you then use the rotated image? The coordinates used are always in the upper left corner, so to keep the grob consistent we'd have to change the size in order to not lose information and it seems to me you'd then have difficulty using it since it would be hard to know where to place it..
Btw, what's the stance about the idea of adding a new type of variable that is preserved even if you accidentally open the program code in the editor on-calc? For example, for game highscores or Zelda/Final Fantasy save files? I suggested it a few times before and that issue was brought up a while ago too, but it seemed pretty much ignored.
Its not so much that its been ignored, rather there have just been higher priority items to look at. Another item to consider is that when we make a change we'd rather make a complete change rather then just patching one instance of a hole in capability. In my mind at least, this ties directly in with the whole underlying variable management, apps vs folders vs archived data, where are variables created, how they are created and similar.
There are many different ways to address the issues of "keeping a variable around long term". Your idea of a special variable is one. Another would be direct access to create and store variables into the flash memory. Another would be to have folders in the system. Another would be to put in something like sqlite and give an actual database that could be used or created at will. Another would be the concept of "projects" that had multiple source files, binary blobs, non-modifiyable data, etc.
In short, there are lots of ways to look at the issue and potentially certain of them are more in the long term direction of how we'd like the platform to move.
A suggestion! I've also have been having trouble when coding recently with aligning my text on screen. I want ti centered, but I can't figure out how big a string will be on the screen! A function to give me the width of a given string of a given font would be nice for my GUI-using programs.
I have to say, though, with the new firmware, I'm going great guns on programming! It's actually sorta nice to work in.
Well, I am glad you are liking it more. Here is something to ponder on for you though.
The reality is this - there were simply much higher priority items in the initial development and releases needing focused attention and polish. This means there are definitely some holes in the language (to name a few - getting the width of a string, being able to print something as a user in a 2d formula format, or a much nicer terminal) yet you already have what I think is the fastest user language on any calculator (excluding assembly and things that need a computer to do), easy to learn, and yet extremely capable programming language. There are TONS of things that I would personally like to do in the editor, UI, language, and so on to really make it shine.
Well if you put it that way... NDA's are maybe fine for beta testing. In the case of companies forcing this onto say open source driver devs though, it's bad (kinda defeats the purpose of open source).
Agreed.
This NDA basically says the terms of disclosure are "information regarding future HP calculator products" with the stated intent of "to provide feedback on future or upcoming products, including reports of issues or new features" or something like that.
Well that sounds nice, but I don't feel comfortable with NDA's for some reason.
Its just the way companies work. You get private information and in return you sign something that says not to disclose that information. Kind of unavoidable in modern business. I understand though and there are plenty of people who agree with you.
Is there any obligation to this? Like you have to test this and this?
We invite people for specific products, and will often encourage testing of specific things within that product, but the only obligations are ones around confidentiality.
Note that I assume the applicant must be of legal age, else there is no way to enter a confidentiality agreement.
Periodically, the HP calculator group will ask for applications from individuals interested in beta testing projects. We ask for some information in order to generate the best cross section of users to hopefully catch as many issues as possible before a release. I can't select everyone, and not everyone is interested in each type of product.
Even though this is posted in the HP Prime forum, that does not mean there will not be other types of products (basic scientific, financial, mobile apps, etc) that need testing. This is just an application for general interest and you can indicate which types of products you might be interested in testing.
If you are interested in any however, please download a form and send it to me. Email is probably best. timwessman is my name, and I am at hp.com (this is your entrance exam - you must figure out the correct email address... )
While we don’t expect anyone to devote an unreasonable amount of your time, those that consistently find issues, perform tasks and generally contribute quite a bit are usually asked to continue as beta testers long term.
Sometimes, there are things you may not find extremely enjoyable to work on (for example, a non RPN machine or similar), but we may ask you to assist. Again, those that are willing to focus on specific areas or tasks are usually asked to continue testing in the future when the more exciting projects are around.
You are allowed to focus on specific areas of interest, but we ask that you don’t exclusively focus on areas of interest. There are always “boring” areas of products that need thorough testing as well.
In short, those that have positive attitudes and contribute get to continue for as long as you are willing to share some of your time. If you are fun to work with, we want to continue working with you!
As a beta tester, you will be required to sign a confidentiality agreement/non-disclosure agreement before any paticipation. We ask that you do not discuss in outside locations, post images or hints anywhere or discuss with people not involved in the testing. As far as I can tell, there has never been unauthorized leaks which means we can continue to trust the community as a whole.
If you are sent materials/units, we are also required to have you sign a form that basically states “HP is not responsible if this device destroys the universe and HP may request the units back at any time.”
Beta testing is a lot of fun! It is always exciting to have behind-the-scenes knowledge about what is ongoing, and to have a part in shaping the way products are formed, and to be involved in something for which we all feel passion. Often those involved in beta testing come up with new ideas that later appear in products, have keyboard layouts or product ideas discussed for feedback, and generally get to be involved with the calculators we love.
The download at the top of the list is a PDF form allowing you to type directly and is the easiest format. If you'd prefer the odt or docx version however, they can be downloaded as well.
Today's suggestion: I can't find any functions to alter system settings. Are they in predefined variables, or functions, or what? I'd like to be able to, for example, switch angle modes to the correct one in a program.
VARS->HOME is where most items of interest will reside. Yes, they are in variables. Note however that some can be overridden by application variables (AAngle takes priority over HAngle) and so to do things properly you need to handle those.
What I am curious about is if it will be as overpriced too. The costs to implement this in classes can pile up very fast with 30 calcs and wireless kits.
I doubt it - organizations are less sensitive to price than individuals.
It will not be ridiculously priced. I can't announce final pricing because I'd hate to step on anyone's toes, but it will be nowhere like the nspire wireless link costs. It will be quite reasonable.
Yeah, there are some silly errors in the video (like the battery, or that poor kid in the corner that didn't get connected apparently, or the dual sliding cases...) :-D
When you have people that normally make things for laptops, they tend to mess up things like "small battery".
>Enjoy, and I challenge you to try building this project as well!
Challenge accepted! (nice work btw)
Mine can stream <1cm resolution survey grade GPS data at up to 60-120 readings a second from 3 separate devices, has up to two internal 1km range Bluetooth radios, runs off 4 external AA batteries, can be run over by a truck without damage, has a screen that withstood the impact from a .22cal hollowpoint without damage, and is waterproof for 30 minutes at a 3 meter depth. :-)
Show Posts
I was wondering where did all the HP users go in the past month or so
