The NumWorks calculator evolves quickly.
|
01-23-2019, 09:54 PM
Post: #8
|
|||
|
|||
RE: The NumWorks calculator evolves quickly.
The big number gap between 1.8.1 and (1).9.2.0 is because the NumWorks team decided to drop the leading "1". I wondered too if it was a typo until it was clarified on TI-Planet.
I'm not surprised that the 2DS is way faster than the NumWorks hardware. The 2DS's processor and especially the memory subsystem are a lot faster, but I guess the major bottleneck here is the NumWorks's screen controller, which is optimized for full-screen blitting in one operation and not lots of individual set_pixel() operations, as the framebuffer is not memory-mapped. You can time operations now with the time module as it was introduced in the 9.2.0 version. It's not shown on the toolbox, but time.monotonic() will allow you to keep track of time in your scripts. |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
The NumWorks calculator evolves quickly. - compsystems - 12-06-2017, 12:41 AM
RE: The NumWorks calculator evolves quickly. - grsbanks - 12-06-2017, 08:09 AM
RE: The NumWorks calculator evolves quickly. - pier4r - 12-06-2017, 12:25 PM
RE: The NumWorks calculator evolves quickly. - toml_12953 - 01-23-2019, 03:01 AM
RE: The NumWorks calculator evolves quickly. - berndpr - 01-21-2019, 01:44 AM
RE: The NumWorks calculator evolves quickly. - Stevetuc - 01-23-2019, 05:57 AM
RE: The NumWorks calculator evolves quickly. - berndpr - 01-23-2019, 08:48 PM
RE: The NumWorks calculator evolves quickly. - toml_12953 - 01-24-2019, 09:52 AM
RE: The NumWorks calculator evolves quickly. - Jean-Baptiste Boric - 01-23-2019 09:54 PM
|
User(s) browsing this thread: 2 Guest(s)