Remember the history between sessions

[elementaryBot]

Useful when you're doing the same computations over and over. Or need reminders about that tax rebate you computed last week :)

Launchpad Details: #LP1407046 PerfectCarl - 2015-01-02 08:49:29 +0000

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/44006001-remember-the-history-between-sessions?utm_campaign=plugin&utm_content=tracker%2F59892578&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F59892578&utm_medium=issues&utm_source=github).

[elementaryBot]

I am not really sure if I like that to be honest - the calculation history is not planed to be a place where you "store" values from last week. It's just a quick grab-the-last-values/terms to work with them. Persistent values you need should be saved to a file.

I don't like overpopulating the history with old values because some values might be important (and should be written down / saved elsewhere), but most input is just needed for one time use only.

Launchpad Details: #LPC Marvin Beckers - 2015-01-02 12:44:44 +0000

[elementaryBot]

A persistent history would be very elementary-like. If I close and re-open Scratch I also want to continue working where I left. And storing calculation results in a text file is quite cumbersome.

Launchpad Details: #LPC quassy - 2015-01-02 22:38:57 +0000

[elementaryBot]

Well, you cannot really compare scratch's history of open files and calculus' history because calculus keeps adding numbers to the later one without the user removing anything. You always calculate values for something, maybe a pricing / stock list. It's not like you do complicated calculations with the default calculator and need to continue on that task the next week. There are more suited applications for that task. But I tend to agree on the "elementary-like" part, you should be able to close and reopen calculus and have your history.

If persistent history gets implemented I'd say it has to have a limit of numbers - But how many calculations should be saved? 10? 20? 50? 100? more?

Launchpad Details: #LPC Marvin Beckers - 2015-01-03 18:36:25 +0000

[elementaryBot]

You could have long and short memory. Short memory would be cleared at the end of a session (closed, log off, something along those lines), while long term memory logs everything and saves to a file.

Short memory would be the type that would be displayed by default, but a "show more" option would display long term history.

Launchpad Details: #LPC Shawn McTear - 2015-01-14 16:24:48 +0000

[cassidyjames]

The way Android handles this at least is persisting history in perpetuity (afaict), but then just having a "clear" item. I think this sounds sane and would feel pretty elementary.

[cassidyjames]

Like #110, this should respect the system-wide history setting.