Commit Graph
14 Commits
Author SHA1 Message Date
Kyle Geib d9b30f64f2 ISSUE-075 - Switched to using GridSpots for the SelectedCars state.
Chyrons still show out-of-date information, though. Might need to do some refactoring to get this straightened.
2022-03-17 12:16:57 -04:00
Kyle Geib 58da0e4895 ISSUE-053 - Placed Chyrons on video feed.
Adjusted the method that placement is determined. It didn't make much sense to define Placement in state, so I've moved it to the central theme object instead.
I also took the time to support +10 laps and minutes with a special xScale setting for the TimingTowerRows.
2022-03-17 08:56:55 -04:00
Kyle Geib b48579ac54 ISSUE-053 - Placed TimingBoard into the video feed element. But the scaling is messing with the clip path because the clip path values do not follow the scale correctly.
The issue is, say our scale is 50%. A PositionFlag on the TimingBoard is normally 32x32px in size. That means that the size of the actual PositionFlag while scaled is 16x16.

The WipeTransition component takes the effective size of its child element using the  useMeasure() hook. So it sees the size is 16x16, thus, when the wipe is set to visible its clip dimensions on the opposite and adjacent points of the triangle are 16px away from origin.

But because we're scaled at 50% that clip path effectively becomes 8px. The clip path is doubly scaled. As a result I'm seeing white squares in the corner of the PositionFlag component.

I think I might be able to solve this by using simple division to express the values of the clip path in percentages. Or I'll find a way to avoid the double scaling issue.
2022-03-15 13:14:20 -05:00
Kyle Geib d2e4afb975 ISSUE-062 - Expanding status indicator in place.
Moved some dimensions data to the themes object for re-use between components.
2022-03-08 17:03:09 -05:00
Kyle Geib 1cccc7d094 ISSUE-058 - Basic mode switching implemented.
Still need to fade-in/fade-out the interval numbers.
Also need to look into wipe-in fade animations for full names. Will see what I can do...
2022-03-03 18:56:07 -05:00
Kyle Geib 49dd08cc13 ISSUE-057 - Refactor: Switched from buildRow() to a dedicated component named TimingTowerRow.
This is both simply a better way of going about it and will allow me to use hooks to track position changes and allow for new non-CSS animations.
2022-03-02 09:57:07 -05:00
Kyle Geib edeba37c6d ISSUE-057 - Progress on building prototyping tools.
New reducers for event slice that allow increasing of car distances, awarding fastest laps, and changing the statuses of cars.
Updating more types to enums, which are just better in most cases as far as I can tell.
2022-02-22 19:12:29 -05:00
Kyle Geib c9388b86fc ISSUE-054 - Basic animating of the Timing Tower added.
Provided basic controls to switch between.
Still need to properly round the bottom rows of both the running and retired cars.
2022-02-22 11:53:14 -05:00
Kyle Geib 22ebab1101 ISSUE-054 - Initial work of building the Timing Board. Working so far only have work for the Timing Tower.
Timing Board is the combination of all elements on the left side of the screen, including the Status Indicator component (not written yet) that is visible whenever there are cars on track.
2022-02-16 14:36:27 -05:00
Kyle Geib fd18703d1a ISSUE-045 - Chyron Body - Taking a moment to rename some reducers to be more consistant (verb in front). 2022-02-09 13:55:52 -05:00
Kyle Geib 0625361a18 ISSUE-032 - Have Chyron prototyping controls configured and hooked up.
Support for double driver chyrons.
Serious refactoring of the BroadcastGraphics states.
Simplification and improvements to how the chyron states work (I was using interfaces in a way that was incompatible with reality and have fixed it).
2022-01-31 18:24:25 -05:00
Kyle Geib 5e7940a151 ISSUE-032 - Progress checkpoint.
Have a lot of the scaffolding in place. Next step is to make the Chyron controls actually work.
Dramatic re-thinking of the chyron state definitions.
Lots of goofy type following tricks in broadcastGraphics.ts.
2022-01-28 17:53:50 -05:00
Kyle Geib e676c7a95a ISSUE-032 - Progress checkpoint. Have a working "selectedCars" modifying component named GridSelection.
Have a work-in-progress AngledFlag prototype controller that relying on a central state property in the Workspaces portion of the store. It's a bit hacky. But it made me realize that my desire to do silly things with extending interfaces won't work that way I'm going to need to rely on them in the future. I cannot demand more specific data from a state that uses a less specific interface. Rookie mistake.
I am also at the mercy of a design flaw when it comes to using React Hooks: The way I organize Workspaces makes React very angry. When I switch between workspaces that rely on hooks to render correctly the whole thing explodes.

I believe I need to use components directly to correctly unmount - instead of the very hacky switch statement I have in the form of fetchBroadcastGraphic().

I might need to try seeing if ReactRouter can provide my solution.
2022-01-27 17:47:49 -05:00
Kyle Geib 5d009a3d70 ISSUE-032 - Defined a great number of new state types for use with the race event's state, the broadcast director's controls, and the broadcast graphics states.
Taking a second to make a commit to save my progress so far.
2022-01-27 13:39:52 -05:00