scanner wrote:Are you in contact with TI devs?
Yes, although not directly with the ones who would deal with this issue.
scanner wrote:Maybe I could try to explain what I tried to communicate to the costumer service last year. But beware: My English is rather bad and "Je ne parle pas français" ( really, I just took this from the web
).
Well, they've been provided with an explanation and an animated screenshot showing the program editor and the freeze, so hopefully they'll locate the issue with no further info
scanner wrote:Well, here we go: I'm a teacher and my school decided to use the TI-Nspire last year.
I may tell them that too, it could even more catch their attention...
scanner wrote:I was quite surprised to learn, that the TI-Nspire is missing a certain function which should be used in physics. It's the hyperbolic regression. There are a few quantities which are inversely proportional to another. If you think of Newtons lex secunda F = m * a.
If F is constant a is proportional to 1/m. I don’t get it why TI isn’t offering a regression function for these laws. Our old Sharp EL–9900 was able to do this. I know I might use the “power-Regression” but, it’s not rally the same. And yes, I know there are other ways to show the inverse proportionality. Never the less. Our pupil have to learn and do more that pupil using e.g. the Sharp EL-9900. I programmed some crazy quit powerful regression function for the Nspire, but I soon learn that our pupil are not allowed to use these in their finals (school leaving examination / L'épreuve écrite du baccalauréat) – since these examinations should be comparable – (ha, ha, ha = ah ah ah).
Oh well, indeed I'm sure that if it's not there by default, this can be done by coding a function, as you said.
scanner wrote:Anyway – I discovered that the Nspire has problems with drawing the result of a function directly.
Example:
My function
regpoly(2,xw,yw,0)
returns
9.5*x^(2)-28.3*x+21.25
and I can use
g1:= regpoly(2,xw,yw,0)
and draw g1 than, but if I try to draw regpoly(2,xw,yw,0) directly, the Nspire fails.
Strange, isn’t it?
I don't really have an explanation, but I may have an idea (could be wrong, but some other people can reply
) :
g1 could be calculated once and for all (and it can take a "long" time depending on the calculation) then graphed from the expression, whereas when graphing regpoly(), it's recalculating the whole thing for
each point, which would appear as a freeze depending on the time one calculation takes....