GRAPH 3D v2.425 (20-FEB-2017)

[Han]

(12-16-2014 08:54 PM)Trickfisch Wrote:  The problem in your code Han is the very slow reaction, when you touch the screen. Even the scroll renders in real time. This is not possible with the prime. You must take a screenshot, zoom the screenshot and at the end you can render it new.

I'm not sure what you mean here. As for zooming, the zooming action uses real-time rendering because I didn't want the pixelation and the image appearing cropped (when zoom out).

Quote:So I've make more with my code. The single touch command is supported and the trace mode is even better with touch.
I know that it is slow with complex functions or the trace mode. But with little functions you can have your fun and in trace mode it is a good option, to change the view without go out of it.

I'll check it out. The code I posted, however, does have real-time trace mode rendering with rotations and zooming.

Quote:I hope Han, that you can accept this code. I don't use the wait(-1) cmd. No if a finger is on screen I crap the coordinates directly with "MOUSE".
When nothing is moved, then a old variable (who is defined with the coordinates, before I analyse the touch data) must have the same value. I think it is acceptable for the HP Prime Touch Screen with his very rough touch grid.

I'll test it out. The problem with MOUSE() is that it once you start waiting for MOUSE() events, there is now way to handle any other events.

Quote:Even I've changed the g3D_drawtrace and g3D_draw function. So every time, when I'm in trace mode, I wrote the picture from g3D_draw not to G0. I write it to G2 and then render the g3D_drawtrace raster over it.

Yes, this is old code that isn't optimized (in fact, I don't think G2 is needed anymore). I used G2 in older versions to to avoid having to call draw commands, but I think it's no longer needed. An IF THEN ELSE END is not necessary; you can simply just not draw if tmode is on.

Quote:TO HAN:
Isn't it possible to have a faster rendering? Only because you add some lines with line_p in trace mode, the function runs semi slow. I think that can't be normal.

I am pretty sure this is due to the comments above about G2.

Quote:But you are the brain here and you have created the script, so I think you know more about the speed and how fast it runs then I.

I would be so happy, when this code will be used in your code.

If it's faster and does what I need it to do, I'll include it in my code branch. If not, I won't -- but anyone is of course free to modify the source for their own use.