Stephen Morgan 307bd9366d ui: In TransactionScreen, set the current transaction and index in ... tsInit based on the previous RegisterScreen. Use the RegisterScreen logic for selecting the new transaction when we cannot find the existing one. This enables us to get rid of regenerateTransactions. There is now different behaviour in the transaction screen when the journal is reloaded and the transaction being viewed is no longer available, but I have not been able to find an example which exhibits this different behaviour. I think it is better to have consistent behaviour between the register screen and transaction screen when determining which to select. This corrects a bug where you had to reload twice to reset the valuation and cost flags, due to the elimination of regenerateTransactions.		2021-07-02 10:07:03 +10:00
..
UI	ui: In TransactionScreen, set the current transaction and index in	2021-07-02 10:07:03 +10:00
UI.hs	ui, web: fix build after tests cleanup	2018-09-03 08:43:57 -07:00