do not reset the new transaction model in the constructor

1) reset() requires that there is a current profile in Data and that may
   not be true because the new transaction activity may be started by a
   shortcut referencing a profile that was removed and that may have
   been the last profile, i.e. there may be no profiles at that moment
2) reset is later called by the new transaction fragment anyway, when it
   has ensured that there is an active profile

diff --git a/app/src/main/java/net/ktnx/mobileledger/ui/new_transaction/NewTransactionModel.java b/app/src/main/java/net/ktnx/mobileledger/ui/new_transaction/NewTransactionModel.java
index 35bb3c82889c700efbc6e62e2bf91c7110157778..8b96f365fca9ce415d79ff0b1f8a86ba6f478c7e 100644 (file)
--- a/app/src/main/java/net/ktnx/mobileledger/ui/new_transaction/NewTransactionModel.java
+++ b/app/src/main/java/net/ktnx/mobileledger/ui/new_transaction/NewTransactionModel.java
@@ -80,7 +80,6 @@ public class NewTransactionModel extends ViewModel {
     private final MutableLiveData<FocusInfo> focusInfo = new MutableLiveData<>();
     private boolean observingDataProfile;
     public NewTransactionModel() {
-        reset();
     }
     public LiveData<Boolean> getShowCurrency() {
         return showCurrency;