mirror of
https://github.com/DarkFlippers/unleashed-firmware.git
synced 2026-11-14 12:27:33 +00:00
Mykhailo ShevchukandClaude Opus 5
e611e31583
* RFID: review follow-ups to the T5577 dumps in the Saved list What #1188 left behind, found by reviewing it again after it was open. The missing-app dialog told the user to install the T5577 app from the apps catalogue. It is not there: the .fap ships in the firmware's own SD resources, which is what the message says now, and the comment on T5577_APP_PATH said the same wrong thing. A dump that will not open now says whether it is no longer on the card or is not a dump this version reads - one message covered four causes, and the likeliest one on a handoff, the file being gone, was not even logged. Long names are cut to fit, as the file menu's header already did; that clipping is one helper now rather than two copies. The T5577 app's Saved no longer counts the dumps before opening the browser. The browser draws "<Empty>" for an empty folder by itself, so the scan only chose the cursor row - and since dumps moved in beside the keys it read past every key in the folder first, then the browser read the same folder twice more. The legacy folder is still listed, being a subfolder, and is now made only when a block test writes its backup rather than at every launch. In the lfrfid app, a launch argument naming a dump no longer needs a verb of its own: the extension already says what it is, which removes the browse branch and its custom event, and the start scene goes back to plain menu dispatch. A dump renamed in the T5577 app reopens the list in the folder it was in rather than at the root. The path check asks the storage service whether the file is under the app folder instead of comparing bytes, since /ext is case-insensitive. Archive: "Show" asks a predicate rather than comparing a file type against ArchiveFileTypeBadUsb in three places, so where a type sits in the enum stops deciding whether it can be shown as text. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * T5577: keep the test backup out of the open-dump path A block test borrowed app->path to build its backup's filename. That string is the dump the user has open, and the saved browser opens where it points - so after a test, Saved went to the backup's folder instead of the dumps folder. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>