4 Commits

Include renames

Author	SHA1	Message	Date
sneak	e0ccb1c8de	fix: a double click on a Top tokens button tracks the token once (closes #729) ... A "Top tokens:" button had no already-tracked check and stays enabled until its save ends, so a fast double click tracked the token twice in memory. Its handler now checks first. A second click shows "Already tracked." and tracks nothing. The top 100 dropdown already has this check, so it is unchanged. Model: opus-5-5	2026-11-03 05:28:24 +00:00
clawbot	267b69382e	fix: a second click on Add while the lookup waits tracks the token once (closes #727) ... The "already tracked" check ran only before the contract lookup, so a second click while the first lookup waited tracked the token twice. AddToken and SettingsAddToken now check again when the lookup answers. An answer for a token tracked meanwhile shows the "already tracked" flash message and tracks nothing. Model: opus-5-5	2026-11-03 06:24:14 +01:00
clawbot	d89099d90a	fix: the address screen shows a token just added at its fetched balance, not 0.0000 (closes #516) ... A balance refresh that returns now draws the balances on AddressDetail or AddressToken again when that screen is up, not only the wallet list. Their transaction lists are left alone. Every add path on AddToken and SettingsAddToken tracks a token through trackToken(), which gives the tracked record `balanceNotFetched: true`. While the field is set, the token's line reads `quantity unknown` instead of 0.0000, and Send reads its balance as unknown. refreshBalances() now resolves with the tracked tokens whose balance it read at every address. The popup's refresh deletes the field from those tokens in the stored record and leaves the rest of the stored list as it is. Removing the token removes the field, and each network keeps its own records. Model: opus-5-5	2026-11-03 02:25:25 +01:00
clawbot	41842b197e	fix: a token lookup that answers after the user left AddToken no longer changes the screen (closes #603) ... When the contract lookup on AddToken answered, the popup went to AddressDetail even after the user had opened another screen. It now goes there only while AddToken shows and has not been opened again since Add was pressed; AddToken counts its openings as Send does. The token is still added as before unless the network changed. An answer, found or failed, from an earlier opening leaves the screen and the status line alone, so a later lookup's "Looking up token..." stays. Judgement call: a user who went Back to AddressDetail during the lookup sees the new token once that screen is drawn again. Model: opus-5-5	2026-10-27 23:16:10 +01:00