fix: image addresses
This commit is contained in:
parent
475d2bfdd0
commit
d0dfa96e24
4 changed files with 5 additions and 5 deletions
|
|
@ -47,7 +47,7 @@ The Qt Framework is quite complex and beyond the scope of this post. Big picture
|
|||
|
||||
How do we optimize this? It is necessary to take a step back and observe the structure of the entire application:
|
||||
|
||||

|
||||

|
||||
|
||||
Many flaws are now clear:
|
||||
|
||||
|
|
@ -68,7 +68,7 @@ First, let's pin down what exactly can be parallelized.
|
|||
|
||||
This lead me to the follow structure:
|
||||
|
||||

|
||||

|
||||
|
||||
- Three callback groups are triggered at differing intervals according to their urgency on the GUI node
|
||||
- A thread-safe queue[^2] processes all ingested data for each callback group
|
||||
|
|
|
|||
|
|
@ -101,7 +101,7 @@ Considering each element of the state machine, I simplified it into the followin
|
|||
|
||||
Since we only have $N\ll 32$ vehicle flags and $M\ll 32$ track flags, all of this information (all of the state flags) can be encoded in a `uint32_t`:
|
||||
|
||||

|
||||

|
||||
|
||||
The state must also store a few other relevant details:
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ A user request can be modelled as follows:
|
|||
4. CloudFront checks its edge caches for the requested content. If the content is stale or not cached, CloudFront fetches the content from S3. Otherwise, it uses the cached content from an edge server.
|
||||
5. CloudFront returns the content to the user's browser.
|
||||
|
||||

|
||||

|
||||
|
||||
# difficulties
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ That's it. The `makefile` relies on some scripts that compile code and run the c
|
|||
|
||||
# neovim integration
|
||||
|
||||

|
||||

|
||||
|
||||
Leveraging [LuaSnip](https://github.com/L3MON4D3/LuaSnip), a custom `CP` user command, and some scripting for window management and asynchronous jobs, I'm able to:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue