forked from thijooree/android
update docs
This commit is contained in:
@@ -33,6 +33,20 @@ Each profile entry shows:
|
||||
- Profile image (circular avatar)
|
||||
- Visibility toggle switch
|
||||
|
||||
### Login Order
|
||||
|
||||
All logins are shown as one list, across banks. When there is more than one login, each row gets a three-line handle (`ic_reorder_lines`) on the right; press and drag it to move the login up or down (`SettingsLoginsFragment.attachDragHandle()`). Tapping the rest of the row still opens the login details.
|
||||
|
||||
On drop the order is saved with `CredentialStore.setLoginOrder()`, which:
|
||||
- writes the combined order to the `login_order` pref as a JSON array of login tags (`mib_<id>`, `bml_<id>`, `fahipay_<id>`, `mfaisa_<id>` — the same format as `BankAccount.loginTag`)
|
||||
- rewrites each bank's own list (`mib_login_ids`, `bml_login_ids`, …) in the same relative order, so code that walks one bank's logins stays consistent
|
||||
|
||||
It then calls `HomeViewModel.resortByLoginOrder()` so already-open screens re-sort immediately.
|
||||
|
||||
`CredentialStore.getLoginOrder()` returns the effective order: saved tags that still exist, followed by any logins not yet ordered (e.g. newly added) in the default MIB → BML → Fahipay → M-Faisa order. `loginRank()` turns that into a sort key; unknown tags sort last.
|
||||
|
||||
See [Login Order](00-app-overview.md#login-order) for where the order is applied.
|
||||
|
||||
### Visibility Toggle
|
||||
|
||||
Toggling a profile off hides it from the accounts list and excludes it from API refresh cycles. The session is kept alive — the profile can be re-enabled without re-logging in.
|
||||
|
||||
Reference in New Issue
Block a user