Movie Tickets v1.18.0

Full Changelog: v1.17.0...v1.18.0

Movie Tickets v1.17.0

The 1.15 tree, numbered above 1.16

Same code as v1.15.2, renumbered. v1.15.2 carried the right tree but the wrong number — BrightMarket and Obtainium compare versionName, so a build numbered below the v1.16.0 it replaces is never offered as an update. If you are on v1.16.0, this is the one that reaches you.

v1.16.0's burst capture and error chip were meant for Roll, not for this app, and are backed out in full: burst capture, the serial ingest queue, the buffer indicator, the camera lifecycle change, the burst grouping fallback and the ported ReportChip. The tree is byte-identical to v1.15.1 apart from the version.

Kept from v1.15.0 / v1.15.1: swiping between ticket codes on the enlarged screen, the TICKET n OF m · SEAT row, and the code at full width.

Known issue this restores (it predates v1.16.0 and is not new): tapping Capture three times quickly runs three full-resolution JPEG encodes on the main thread and starts three concurrent ingests. That can run the app out of memory, and an OOM inside CameraX unbinds the camera — the preview goes black and does not come back until the app is force-stopped. The fix is in commits 12a0586 and 90c2502 if it is wanted here on its own.

Full Changelog: v1.16.0...v1.17.0

Movie Tickets v1.16.0

Burst capture

Shoot the whole stack, then leave. The camera used to take one photograph and navigate away, so four tickets to one game meant four trips through ADD. It now stays up until you press DONE, and every shot in the visit lands on one stack.

A Sony-style buffer. A thin vertical bar exactly as tall as the numeral beside it, filling from the bottom as the queue drains, with the count going down rather than up. Past 8 unread shots the shutter says BUFFER FULL until it drains.

Fixes

The lag, and the black screen after about the third shot. Three quick taps did three full-resolution JPEG encodes on the main thread and started three ingests at once — an OutOfMemoryError on this phone, and an OOM inside CameraX unbinds the camera, which is a preview that never comes back.

• Encoding runs off the main thread on its own single-parallelism dispatcher, so one frame is resident instead of all of them.
• Reading is serialised too: four shots no longer mean four model calls, four ZXing decodes and four full-size bitmaps competing with the preview.
• The frame grab and the encode are both guarded — a shot that cannot be taken costs that shot, not the camera.
• The camera binds in a DisposableEffect and unbinds on the way out, so leaving the screen releases it.

Grouping. A burst shot falls back to the burst's first pass only when the title match found nothing and the dates do not disagree — so a badly read photo joins the three it was taken with instead of landing alone as Ticket 4f2a, and a genuinely different event still keeps its own group. The movie picker waits for the burst to end rather than opening over the viewfinder.

Error chip

Errors now arrive as a small chip in the corner instead of the full sheet across the screen. Three things raise it — a shake, a crash last run, a failure the app noticed itself — and only a tap opens the sheet. Ignore it and it fades; an unsent crash log stays on disk for the next launch.

Full Changelog: v1.15.1...v1.16.0

Movie Tickets v1.15.2

Back to 1.15

v1.16.0's burst capture and error chip were meant for Roll, not for this app. They are backed out in full — burst capture, the serial ingest queue, the buffer indicator, the camera lifecycle change, the burst grouping fallback and the ported ReportChip. The tree is byte-identical to v1.15.1 apart from the version.

Kept from v1.15.0 / v1.15.1: swiping between ticket codes on the enlarged screen, the TICKET n OF m · SEAT row, and the code at full width.

Known issue this restores (it predates v1.16.0 and is not new): tapping Capture three times quickly runs three full-resolution JPEG encodes on the main thread and starts three concurrent ingests. That can run the app out of memory, and an OOM inside CameraX unbinds the camera — the preview goes black and does not come back until the app is force-stopped. The fix is in commits 12a0586 and 90c2502 if it is wanted here on its own.

Full Changelog: v1.16.0...v1.15.2

Movie Tickets v1.15.1

The enlarged code goes back to full width

v1.15.0 drew it at 90% to make room for the ticket switch. It did not need the room — the switch sits in the strip below a centred code and fits either way — and a code held up to an usher's handheld wants every module it can get. The tenth is back.

Swiping between ticket codes and the TICKET n OF m · SEAT row from v1.15.0 are unchanged.

Full Changelog: v1.15.0...v1.15.1

Movie Tickets v1.15.0

Swipe between ticket codes

Smaller code, switch on the same screen. The enlarged booking code now draws at 90% of the panel width instead of all of it. The freed row holds TICKET n OF m · SEAT, with PREV and NEXT — at a door with three tickets on one phone you no longer close the overlay, step the pager and reopen it for each person.

Swipe to turn the page. A sideways drag on the enlarged code moves to the next ticket. It only fires at 1x; once you have pinched in, the same drag is still a pan.

Fixes

• The overlay walks only tickets that actually carry a code, so a swipe can never land on a blank white screen.
• Turning a page in the overlay moves the detail page underneath too — close it and you are on that ticket.
• The caption under the code told the truth about where the code came from: it said GENERATED FROM THE BOOKING CODE even for one read straight off the ticket.

Full Changelog: v1.14.0...v1.15.0

Movie Tickets v1.14.0

Full Changelog: v1.13.0...v1.14.0

Full Changelog: v1.13.0...v1.14.0

Movie Tickets v1.13.0

Full Changelog: v1.12.0...v1.13.0

Movie Tickets v1.12.0

Full Changelog: v1.11.0...v1.12.0

Movie Tickets v1.11.0

Full Changelog: v1.10.0...v1.11.0