This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - timwessman
61
« on: October 13, 2013, 01:48:59 pm »
Thanks. 10) (Cosmetic issues) There's no key to access semicolons, which is a big problem considering almost every line of code ends with a semicolon. Having to go to the Charmap everytime is annoying.
Alpha +
62
« on: October 13, 2013, 10:56:52 am »
Hey, that 3D grapher isn't orthogonal, even! (Orthogonal rendering is easier, stuff doesn't get smaller as it gets further back. Also has a small advantage when comparing two locations, but generally less intuitive)
Yes, he did a fairly nice job for a few simple lines of code. However, this is nothing yet...  Also, had to give the language an "official" name. Otherwise there is just too much possibility for confusion. http://en.wikipedia.org/wiki/Rocky_Mountain_BASIC HP-BASIC is actually an old programming language from HP systems way back in the day. The guys from the computer history museum were quite concerned about that when I spoke with them during the summer. ha, nice!* Sorunome wants a prime  
That is not supposed to be for customers. HP is a large ship and the downloads on the customer pages are not yet up... :-(
63
« on: October 13, 2013, 10:42:06 am »
Oh ya, DJ I forgot to mention to you that the stretch acts funny sometimes. I've had it do a total of about 5 different things (glitches). Other than that I frigging LOVE my hp prime.
On the first day having it at school (2nd), I convince 3 people to get one, a junior, a senior, and my math teacher.
Glad to hear. :-) Can you please post some code that shows the stretching issues you saw and describe what you expected. I know a minor issue or two was resolved around the grob scaling and I'd like to check that they don't happen anymore. Some might not be fixable as it does a very rough linear scaling with no interpolation, but others probably are/were. Anyone else as well.
64
« on: October 06, 2013, 03:53:56 pm »
Nope, not a huge deal or anything.
Just be aware that like any electrical product, using a 3rd party provided battery may not be supported and potentially have unintended issues.
65
« on: October 05, 2013, 08:47:48 pm »
I didn't exactly reveal this or anything. It has been fairly commonly discussed by others in like Richard Nelsons hhc talk, and at least a few other places for a few months least.
Note that any extended battery will actually not work as the battery actually sits in a reverse position compared to the GS3, so it won't actually fit in the calc.
Very well may void warranty using anything except the stock battery though.
66
« on: October 05, 2013, 12:22:50 pm »
For example they are there with Time units but not with Volume or Distance
Small bug but annoying all the same.
The issue here is basically that the grid chooser shortcuts are supposed to follow a physical layout. However, the keys just run out if you have more then 16 (the grid between the 7 and + keys). Three options we available in my mind: 1. Just do a normal "numbering" like the list choosers where it does 1-9, A-P, and not worry about matching the physical arrangement like seen on the screen. 2. Do the physical layout but be limited to that 4*4 grid. If more, don't have them. 3. Do #2 but then do A-P for others. I chose to implement #2 after investiagating the others and testing. It was the one that most people seemed to agree seemed the best. Would be happy to revisit #3 (or another variant) if enough people seem to think it is a good idea. Comments?
67
« on: October 04, 2013, 03:22:51 pm »
You click in the color box next to "transparent" and pick which one you'd like if I remember.
68
« on: October 04, 2013, 10:50:49 am »
I am guessing the issue was a small problem internally that pure white would not work as a transparent color. *was*
69
« on: September 28, 2013, 12:37:40 pm »
Today's Bug: Doing a numerical expression of the form (1)2 in the CAS results in an error. The CAS does not handle implicit multiplication well.
Nope, using yak/bison does have limitations... Today's Suggestion: I wish there was a | key in the Math palette, as I use that character in assumption statements a lot.
First row, 3 column. Not what you were looking for? Now I'm absolutely disappointed about this HP-Prime (and its CAS), and I'll definitely stay with my good old TI-92+/Voyage 200 with its (modified) Derive CAS which is clearly better and more reliable than this 'hobby project' XCAS. 
Depending on what you are looking for, that is definitely a valid belief. xcas is definitely a much more powerful and capable cas then what is on the nspire if you purely look at what it will integrate/calculate/do, but you are correct it lacks the polish and "user friendliness"* that ti has put into their system. (*provided you want the result like a student would expect) In many cases there are just assumptions about the input, and some funky unexpected syntax. Judging from what many have said, there really have not been any improvements or capability enhancements since the derive time (nspire cas seems basically identical to the 89 machines).
70
« on: September 27, 2013, 05:36:20 pm »
Today's Bug:
Eh? What is wrong with this? You have a 2 item vector with 2 sub vectors (size of 1 and size of 2)? 
Today's Suggestion: the right arrow character should be a synonym for -> in the CAS. Having -> when a perfectly good UTF character exists is quite odd.
Not seeing what this image is supposed to show... :-?
71
« on: September 27, 2013, 05:23:44 pm »
quo(x^7+4x^3+8,x^2+2)
That seems like a lot of steps to get to something that occurs fairly often. Why can't I just do (polynomial 1)/(polynomial 2) for division?
You can. However, your divisor in this case is not a clean piece of your first polynomial and leaves a remainder. Which calculator will directly take that specific input and spit out x^5-2*x+8x? I would call that a bug. Observe: http://www.wolframalpha.com/input/?i=%28x^7%2B4x^3%2B8%29%2F%28x^2%2B2%29Try this one: (21*x^3-35*x^2)/(7*x). That one will cleanly work out (no remainder) and reduce as you are expecting.
72
« on: September 27, 2013, 03:42:35 pm »
I've got another question that may seem simple. How does one do Polynomial division?
...
To do division, I have to go to the on screen menu, select CAS, select Polynomial, Algebra, Quotient,
Nearly there. Put your first poly in the first argument, and the second in position 2. Just like the nspire, it is a 2 argument function. quo(x^7+4x^3+8,x^2+2) Also, one thing I just noticed: If I wanted to find the limit of, say, 1/x as x goes to zero from the positive side, I have to enter "1" instead of just entering "+", likewise if i wanted to find it from the negative side, I would have to enter "-1" instead of just "-".
Yes. It can take either '+' or '-' with tick marks, but not + or - directly as it is interpreted as an operator. This is an item that is in the list of things to improve. It displays correctly on calculation, but the input needs enhancement here.
73
« on: September 26, 2013, 05:04:49 pm »
Today's bug: There's no Help section when pressing the Help button for the Characters menu, any of the coose boxes (templates, the ! menu, etc.) or the Memory Manager.
Thank you. The integrated system-wide help stuff is actually one of the most ambitious parts of the whole system and it is just so darn easy to miss places because of the sheer volume. Today's Suggestion: There's only 10 graphic variables ever?? If we want to use sprites, we can only use the 10; if we want more, we have to hot-swap them out using DIMGROB, which can't possibly be memory/speed efficient.
The G1-G9 are really meant for temporary scratch locations. For example, they aren't saved on a power cycle or sent to the pc. However, it probably would be good to make sure the other commands work with local or exported grobs. Thanks for the reminder.
74
« on: September 26, 2013, 10:56:37 am »
I'm from the good ole US of A (California if you want to be precise). I've only ever learned the d/dx*() syntax.
Yeah, specifically I was referring here to placing the d/dx to the *left* of the expression instead of the expression above the dx part. I didn't realize the derivative symbol itself was unfamiliar!
75
« on: September 26, 2013, 12:04:42 am »
However, in the template, I only see the notation for a partial derivatives, which is not something I was used to.
Out of curiosity, where in the world approximately are you from (USA here)? I personally prefer the d/dx*(expr) syntax myself and used it most frequently, but apparently the majority of the world uses the d()/dx syntax much more frequently (at least from the studies we've done). ∂<box>/∂<box> Yes, that is the right one. Just lazyness on my part to avoid searching out a ∂ character while typing. :-) Trying to type the ' without typing degrees first was challenging. There are two quick places. First, the shift parenthesis key has a '<box>' on it. This is used to quote (not evaluate) arguments. Mainly, it is applicable for RPN use. You can just remove one of those and you have a single tic mark. Second, the quick character key on the shift-9 function has a tic mark there as well.
|
Show Posts