Core: use an explicit .start event sent by app to begin .tick events
Signed-off-by: Stephen Gutekanst <stephen@hexops.com>
This commit is contained in:
parent
8089d3356e
commit
15fd2c3a64
8 changed files with 67 additions and 25 deletions
|
|
@ -36,7 +36,7 @@ pub const components = .{
|
|||
|
||||
ghost_key_mode: bool = false,
|
||||
|
||||
fn init(audio: *mach.Audio.Mod, app: *Mod) void {
|
||||
fn init(core: *mach.Core.Mod, audio: *mach.Audio.Mod, app: *Mod) void {
|
||||
// Initialize audio module, telling it to send our module's .audio_state_change event when an
|
||||
// entity's sound stops playing
|
||||
audio.send(.init, .{app.event(.audio_state_change)});
|
||||
|
|
@ -49,6 +49,8 @@ fn init(audio: *mach.Audio.Mod, app: *Mod) void {
|
|||
std.debug.print("[spacebar] enable ghost-key mode (demonstrate seamless back-to-back sound playback)\n", .{});
|
||||
std.debug.print("[arrow up] increase volume 10%\n", .{});
|
||||
std.debug.print("[arrow down] decrease volume 10%\n", .{});
|
||||
|
||||
core.send(.start, .{});
|
||||
}
|
||||
|
||||
fn deinit(core: *mach.Core.Mod, audio: *mach.Audio.Mod) void {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue