Has slider real time speed decreased over time?

rfv shared this question 11 months ago

Answered

Using GeoGebra Classic 5.0.627.0-d, I've noticed that it now takes roughly 15 seconds for an animated slider to cover its range at speed 1. Earlier constructions from 3 years go were based on a timing of 10 seconds to cover the same range at speed 1. What is the current intended time?

In constructions modeling simple Newtonian systems it is a "nice touch" to have the approximate time in the model correspond to a physical experiment.

The same question

Comments (14)

Simona Riva ● 11 months ago

Confirmed. :)

Let's ask the to the developers.

Reply URL

mathmagic ● 11 months ago

https://help.geogebra.org/t...

12s?????

Reply URL

rfv ● 11 months ago

I've posted TimeSlider.ggb (also shown below and attached) that collects statistics on timer performance with slider min 0 max 1 inc 0.1 speed 1 which should nominally generate time update interrupts every second. Hit start, stop, wait a while, stats for results.

0a6b08b9159aab90a5fd604421df75db

With Classic 5 I get average dt about 1.4, with Classic 6 about 1.04 and with the online app about 1.03.

What's different about Classic 5?

Files: TimeSlider.ggb

Reply URL

Michael Borcherds ● 11 months ago

It should be around 10s (so online behaviour is correct)

Reply URL

mathmagic ● 11 months ago

windows 7 version 5.0.627 funciona exacto

/wPpJjHGuUPGDAAAAABJRU5ErkJggg==

Reply URL

rfv ● 11 months ago

Windows 10 gives the results shown above: 1.4 sec. Windows 7 is no longer supported. Can anyone shed some light on WHY performance is different with Classic 5 on Win 10?

URL

rfv ● 11 months ago

2 different Win 10 pro systems (with I7 processor and 16GB memory, so no system limitations) give 1.4. An Apple MacBookPro with latest macOS 10.15.7 Classic 5 gives 1.05. Can anyone at least point me to the code used by Classic 5 for implementing the slider timer interrupts?

URL

Michael Borcherds ● 11 months ago

https://github.com/geogebra...

URL

Michael Borcherds ● 11 months ago

Try changing

   long compTime = System.currentTimeMillis() - startTime;

   double compTime = UtilFactory.getPrototype().getMillisecondTime() - startTime;

URL

rfv ● 11 months ago

Thanks for the suggestion, but I'm not setup to compile. Is there any different between the Classic 5 and 6 timer handling (since the give different Win 10 performance on the same .ggb test file)?

URL

Michael Borcherds ● 11 months ago

No, the problem is that your computer is too fast I think 😆

URL

rfv ● 11 months ago

In that case, how does Classic 6 slow down the computer enough such that the timer runs faster?

URL

Michael Borcherds ● 10 months ago

Please try v634

Reply URL

rfv ● 10 months ago

Thanks. V634 fixed the problem.

URL