Now you have 10 different options (5 for position flag and 5 for driver portrait) to play with, as well as a slot selector to choose different starting corners.
I have to admit that I didn't want to deal with type juggling with DriverId so I do a pretty hacky job. This is just for prototyping purposes so it really shouldn't be much of a focus for me, right?
Added an overall delay prop for VenetianBlindsTransition so that I don't need to deal with special timing issues for the DriverChyron animation in the future.
Activated with a blink duration. I had to consider a manual delay before starting. The animation delay didn't really work as the number would be visible until the animation started. I'm sure there's a solution but I'm a little lazy to figure it out at the moment.
Otherwise, for future reference: iirc the delay would be 250ms and the duration would be 400ms.
Created a new workspace to test this all out in.
Offering two differing test subjects: A position flag and a driver portrait. This is useful because the images need to be treated differently compared to simple divs.
Figured out a way of tinting both divs and images: Severely offset internal outline styling with semi-opaque colors.
Moved DriverPortrait into its own component. Makes sense as portraits appear in various places. Plan to offer prop between front-facing and 3/4 facing photos (I have a collection of both).
Created a new "Position" type that can be used, with a special function, to place elements through a common prop.
I'll be starting with re-creating this effect on the PositionFlag component. That involves first separating out the PositionFlag into its own common component (it's used on the timing board as well, so it makes sense).
Adding new overlays for prototyping work.
Quite happy with the results. Was far less fiddly than I was expecting.
One interesting thing I had to do was introduce a new BaseContainer div component so that I could let the portraits overflow the BaseBackground component (by being put in a parent component with no overflow rules).
Covered all 2021 drivers. I mocked up portraits for Albon and Zhou in 2022. I also have 2022 Bottas (Alfa) and Russell (Merc) waiting elsewhere.
Added Mazepin portrait overlay image as well to work from.
Went through a lot of trouble to style the team flags to be wider than the country flags. This called for a troubling amount of ternary statements in the angled flag components.
I'm content with the results.
Styling is still to come. Only have Ferrari working.
I've discovered that the team flags are wider than the country flags. So I'll be tackling that necessary change in the next commit before dealing with styling.
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).
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.
As well as just being a little bit better this was necessary to support specifically typed values. We were always going to be selecting between strictly strings. This should allow us to be more flexible.
Also, to avoid a minor bug with switching the Overlay tool with it being invisible SlotSelector now supports being disabled.
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.
Updated the use of "National" to "Country" and renamed some directories.
Added a second larger AngledFlag to the Workspace (because changes that affect the larger size might be hidden by a smaller flag).
Added missing flag for Poland (both original and 2:1 "angled" style).
Added correct 2:1 flags for Mexico and Monaco.
More overlay images (to help with driver number coloring).
It's not 100% complete - I still need to add the second, slightly offset sub flag that goes beneath the main flag, creating a sort of refractive-glass/parallax effect.
Needed to add a new workspace. Thankfully it's pretty easy to add a new workspace. So, kinda nice.
Did a lot of work making 2:1 versions of each flag in vector. Was a bit of a pain in the ass.
Renamed a prop for ProgressSlider, "onBarColor" because prefixing a prop with "on" is special for React and it gets upset and spits out an error.
Added a great new feature: an active outline styling rule. When dragging the overlay image around there's now a red outline to help match edges that are otherwise black-on-black; making them very difficult to align.
A lot of work going on here.
* Moved WorkspaceControls component to a new sub directory
* Renamed overlay images
* Started a static ChyronDriverBasic component (using Hamilton as an example)
* Created a fancy DriverNumber rendering system
* Defined DriverNumber style for Mercedes and no one else yet
* A bunch of new states for the grid: cars, drivers, teams, etc
* Defined a bunch of data for the drivers and teams
* Created another string utility function to generate repeat strings; unit tests included
Okay. I'm content with what I've made. It's not really up to the level of "oh man, package this up as a library and put it out on NPM!" but it works OK for my specific situation.
I ran into too many issues with the percentage value being buggy when the overlay wasn't visible.
I'm still running into issues where useMeasure isn't populating fast enough and the left prop isn't being set correctly.