ActualHorse/CarmenSandiego
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

Round 1 videos fail to load or play after restart, until a map is shown first #64

New Issue
Open
opened 2025-12-21 02:33:46 -05:00 by ActualHorse · 3 comments
ActualHorse commented 2025-12-21 02:33:46 -05:00
Owner
Copy Link

Early round 1 videos don't load or play if round 1 is restarted after having been started once before, but eventually corrects itself after displaying a map and loading the video for the following clue.

Early round 1 videos don't load or play if round 1 is restarted after having been started once before, but eventually corrects itself after displaying a map and loading the video for the following clue.
ActualHorse added this to the v0.5 milestone 2025-12-21 02:33:46 -05:00
ActualHorse added the
Type
Bug
Priority
B
 labels 2025-12-21 02:33:46 -05:00
ActualHorse self-assigned this 2025-12-21 02:33:46 -05:00
ActualHorse commented 2025-12-21 17:01:19 -05:00
Author
Owner
Copy Link

This bug has been fixed, but a new and probably related bug prevents the early round 1 videos from loading if round 1 is restarted after a video plays in round 2 or 3, but eventually corrects itself after displaying a map and loading the next video. Curious. Changing the opening post to reflect this.

This bug has been fixed, but a new and probably related bug prevents the early round 1 videos from loading if round 1 is restarted after a video plays in round 2 or 3, but eventually corrects itself after displaying a map and loading the next video. Curious. Changing the opening post to reflect this.
ActualHorse changed title from RandomVideoPlayer can't load videos until CaseVideoSyncPlayer does first to Round 1 videos fail to load or play after restart, until a map is shown first 2025-12-21 17:03:10 -05:00
ActualHorse pinned this 2026-03-05 23:01:43 -05:00
ActualHorse commented 2026-03-12 02:53:14 -04:00
Author
Owner
Copy Link

This may have been fixed, but a new problem emerges. Closing this until bigger issues are resolved.

This may have been fixed, but a new problem emerges. Closing this until bigger issues are resolved.
ActualHorse commented 2026-03-12 04:22:54 -04:00
Author
Owner
Copy Link

That bigger issue has been resolved, but until this can be verified, I will assume this needs to be reopened. I'll check later whether this still needs a fix.

That bigger issue has been resolved, but until this can be verified, I will assume this needs to be reopened. I'll check later whether this still needs a fix.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Priority
A
The priority is critical
Priority
B
The priority is high
Priority
C
The priority is medium
Priority
D
The priority is low
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Type
Breaking
Breaking change that won't be backward compatible
Type
Bug
Something is not working
Type
Documentation
Documentation changes
Type
Enhancement
Improve existing functionality
Type
Feature
New functionality
Type
Security
This is security issue
Type
Testing
Issue or pull request related to testing
No Label
Priority
B
Type
Bug
Milestone
No items
No Milestone v0.5
Projects
Clear projects
No project
Assignees
Clear assignees
ActualHorse
No Assignees ActualHorse
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ActualHorse/CarmenSandiego#64
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?