New Win32 File API Implementation ⚠ Click here to regain focus ⚠
?
?

Keyboard Navigation

Global Keys

W, A, P / S, D, N Jump to previous / next marker
t / T Toggle theatre / SUPERtheatre mode
z Toggle filter mode V Revert filter to original state

Menu toggling

q Quotes r References f Filter c Credits

Movement

a
w
s
d
h j k l


Quotes and References Menus

Enter Jump to timecode

Quotes, References and Credits Menus

o Open URL (in new tab)

Filter Menu

x, Space Toggle category and focus next
X, ShiftSpace Toggle category and focus previous
v Invert topics / media as per focus

Credits Menu

Enter Open URL (in new tab)
00:00:27Recap
00:00:27Recap
00:00:27Recap
00:01:10Plan for today
00:01:10Plan for today
00:01:10Plan for today
00:02:23Asset metadata is already loaded, so LoadBitmap and LoadSound reduce to just fetching the data
00:02:23Asset metadata is already loaded, so LoadBitmap and LoadSound reduce to just fetching the data
00:02:23Asset metadata is already loaded, so LoadBitmap and LoadSound reduce to just fetching the data
00:03:58Getting rid of LoadSound
00:03:58Getting rid of LoadSound
00:03:58Getting rid of LoadSound
00:06:22(intermission) Forcing order of reads between checking if an asset is loaded and accessing it
00:06:22(intermission) Forcing order of reads between checking if an asset is loaded and accessing it
00:06:22(intermission) Forcing order of reads between checking if an asset is loaded and accessing it
00:07:57(intermission) Implementing CompletePreviousReadsBeforeFutureReads
00:07:57(intermission) Implementing CompletePreviousReadsBeforeFutureReads
00:07:57(intermission) Implementing CompletePreviousReadsBeforeFutureReads
00:09:55Back to removing LoadSound
00:09:55Back to removing LoadSound
00:09:55Back to removing LoadSound
00:13:34Copying the contents of assets into the right place in memory
00:13:34Copying the contents of assets into the right place in memory
00:13:34Copying the contents of assets into the right place in memory
00:14:21General-purpose memory copy function
00:14:21General-purpose memory copy function
00:14:21General-purpose memory copy function
00:16:21Setting the channel sample pointers
00:16:21Setting the channel sample pointers
00:16:21Setting the channel sample pointers
00:17:57Testing the changes. There's some strange clicking bug going on, probably not related to today's changes. We'll do the debugging later
00:17:57Testing the changes. There's some strange clicking bug going on, probably not related to today's changes. We'll do the debugging later
00:17:57Testing the changes. There's some strange clicking bug going on, probably not related to today's changes. We'll do the debugging later
00:19:41Asset background loader with tag matching in 430 lines of code!
00:19:41Asset background loader with tag matching in 430 lines of code!
00:19:41Asset background loader with tag matching in 430 lines of code!
00:22:58Avoiding loading the entire asset file into memory
00:22:58Avoiding loading the entire asset file into memory
00:22:58Avoiding loading the entire asset file into memory
00:23:24Assets need to be rebased and pointed to the appropriate file through a file index
00:23:24Assets need to be rebased and pointed to the appropriate file through a file index
00:23:24Assets need to be rebased and pointed to the appropriate file through a file index
00:25:16Finding a good place in the code for the asset struct
00:25:16Finding a good place in the code for the asset struct
00:25:16Finding a good place in the code for the asset struct
00:27:34Filling in the asset struct
00:27:34Filling in the asset struct
00:27:34Filling in the asset struct
00:33:36The asset struct is just an hha_asset augmented with a file index
00:33:36The asset struct is just an hha_asset augmented with a file index
00:33:36The asset struct is just an hha_asset augmented with a file index
00:35:09Don't design architecture up-front
00:35:09Don't design architecture up-front
00:35:09Don't design architecture up-front
00:36:50Implementing GetFileHandleFor
00:36:50Implementing GetFileHandleFor
00:36:50Implementing GetFileHandleFor
00:39:08File I/O code is simple. Assuming we don't get it wrong, we'll save time by writing it now and testing it together with the code we just wrote. The alternative would involve writing some extra test code
00:39:08File I/O code is simple. Assuming we don't get it wrong, we'll save time by writing it now and testing it together with the code we just wrote. The alternative would involve writing some extra test code
00:39:08File I/O code is simple. Assuming we don't get it wrong, we'll save time by writing it now and testing it together with the code we just wrote. The alternative would involve writing some extra test code
00:41:36Implementing the platform functions
00:41:36Implementing the platform functions
00:41:36Implementing the platform functions
00:43:23We don't close files, so there's no need for a Win32CloseFile function
00:43:23We don't close files, so there's no need for a Win32CloseFile function
00:43:23We don't close files, so there's no need for a Win32CloseFile function
00:44:05Win32OpenFile
00:44:05Win32OpenFile
00:44:05Win32OpenFile
00:49:13Win32ReadDataFromFile
00:49:13Win32ReadDataFromFile
00:49:13Win32ReadDataFromFile
00:50:21Overlapped I/O
00:50:21Overlapped I/O
00:50:21Overlapped I/O
00:53:45Windows can't do reads bigger than 4GB. We don't plan on reading assets of that size, but let's assert against that situation, just in case
00:53:45Windows can't do reads bigger than 4GB. We don't plan on reading assets of that size, but let's assert against that situation, just in case
00:53:45Windows can't do reads bigger than 4GB. We don't plan on reading assets of that size, but let's assert against that situation, just in case
00:55:23Win32FileError
00:55:23Win32FileError
00:55:23Win32FileError
00:56:47Ignoring file operations on bad handles
00:56:47Ignoring file operations on bad handles
00:56:47Ignoring file operations on bad handles
00:58:08Testing today's code
00:58:08Testing today's code
00:58:08Testing today's code
00:59:09Quick step-through
00:59:09Quick step-through
00:59:09Quick step-through
01:00:00We hadn't read the header yet!
01:00:00We hadn't read the header yet!
01:00:00We hadn't read the header yet!
01:02:14Visual Studio fails to show size information on symbols outside the current running executable
01:02:14Visual Studio fails to show size information on symbols outside the current running executable
01:02:14Visual Studio fails to show size information on symbols outside the current running executable
01:05:00The null asset triggers an assertion. We ignore it for the moment
01:05:00The null asset triggers an assertion. We ignore it for the moment
01:05:00The null asset triggers an assertion. We ignore it for the moment
01:05:46It (mostly) works!
01:05:46It (mostly) works!
01:05:46It (mostly) works!
01:06:25Q&A
01:06:25Q&A
01:06:25Q&A
01:07:25bigmonachus What do you use when you need something more dynamic than arenas? Default to VirtualAlloc/malloc? Something completely different?
🗪
01:07:25bigmonachus What do you use when you need something more dynamic than arenas? Default to VirtualAlloc/malloc? Something completely different?
🗪
01:07:25bigmonachus What do you use when you need something more dynamic than arenas? Default to VirtualAlloc/malloc? Something completely different?
🗪
01:09:33insofaras How "handmade" are you going to go on the Linux version?
🗪
01:09:33insofaras How "handmade" are you going to go on the Linux version?
🗪
01:09:33insofaras How "handmade" are you going to go on the Linux version?
🗪
01:10:50quatzequatel Kind of off-topic do you usually have that much luck not getting bugs?
🗪
01:10:50quatzequatel Kind of off-topic do you usually have that much luck not getting bugs?
🗪
01:10:50quatzequatel Kind of off-topic do you usually have that much luck not getting bugs?
🗪
01:13:02plain_flavored Do you usually design an API by just implementing it, or do you try to define the interface first?
🗪
01:13:02plain_flavored Do you usually design an API by just implementing it, or do you try to define the interface first?
🗪
01:13:02plain_flavored Do you usually design an API by just implementing it, or do you try to define the interface first?
🗪
01:15:49kknewkles What is "usage code"? Basically everything down the line that awaits to be fed data?
🗪
01:15:49kknewkles What is "usage code"? Basically everything down the line that awaits to be fed data?
🗪
01:15:49kknewkles What is "usage code"? Basically everything down the line that awaits to be fed data?
🗪
01:27:22general_tach Do you feel that a lot of the common programs today have "bloated" code (much unnecessary code or something along those lines), and/or that coders need to learn to simplify/barebone their code?
🗪
01:27:22general_tach Do you feel that a lot of the common programs today have "bloated" code (much unnecessary code or something along those lines), and/or that coders need to learn to simplify/barebone their code?
🗪
01:27:22general_tach Do you feel that a lot of the common programs today have "bloated" code (much unnecessary code or something along those lines), and/or that coders need to learn to simplify/barebone their code?
🗪
01:27:42gasto5 Doesn't anticipating the usage of the API require decades of work?
🗪
01:27:42gasto5 Doesn't anticipating the usage of the API require decades of work?
🗪
01:27:42gasto5 Doesn't anticipating the usage of the API require decades of work?
🗪
01:33:14kknewkles So basically when you're about to make shoes for a monster, you don't assume how many legs or toes it has, let it stomp around and then use the footprints to make the shoes
🗪
01:33:14kknewkles So basically when you're about to make shoes for a monster, you don't assume how many legs or toes it has, let it stomp around and then use the footprints to make the shoes
🗪
01:33:14kknewkles So basically when you're about to make shoes for a monster, you don't assume how many legs or toes it has, let it stomp around and then use the footprints to make the shoes
🗪
01:33:44jameswidman Suggestion: call this "Snuffy-oriented programming"
🗪
01:33:44jameswidman Suggestion: call this "Snuffy-oriented programming"
🗪
01:33:44jameswidman Suggestion: call this "Snuffy-oriented programming"
🗪