[01:30] <SketchCow> We're swapped over!!
[01:36] <balrog> SketchCow: let me know if there are any issues with that google video data
[01:42] <SketchCow> Also, we have an issue, and maybe db48x balrog Vito` DFJustin can weigh in.
[01:42] <SketchCow> Basically, it appears the javascript keyboard stops working in the new version.
[01:42] <SketchCow> https://archive.org/details/arcade_hero - keyboard doesn't work.
[01:42] <SketchCow> (Running newly compiled)
[01:43] <SketchCow> https://archive.org/details/arcade_bagman - keyboard works (running old version)
[01:54] <SketchCow> https://archive.org/details/arcade_bounty (Running MAMEZODIACK and the keyboard not working)
[01:54] <SketchCow> https://archive.org/details/arcade_dogfight (Running MAMEDOGFIGHT and the keyboard not working)
[01:54] <SketchCow> https://archive.org/details/arcade_dogfight (Running MAMEDOGFIGHT and the keyboard working I mean)
[01:56] <SketchCow> https://ia802608.us.archive.org/8/items/jsmess_keyboard_v2/arcade.js is the javascript.
[01:56] <SketchCow> Probably something SDL
[01:59] <db48x> yes, it appears that the keyboard is sending key events
[01:59] <db48x> the emulator just doesn't react
[01:59] <SketchCow> https://www.libsdl.org/release/SDL-1.2.15/docs/html/guideinputkeyboard.html
[02:00] <db48x> well
[02:00] <db48x> that's the API that mame uses to listen for keyboard events
[02:01] <db48x> (or actually a similar one from SDL2)
[02:01] <db48x> the js keyboard is using the DOM KeyEvent API
[02:01] <db48x> emscripten's SDL port is supposed to translate
[02:01] <SketchCow> https://github.com/Mottie/Keyboard
[02:01] <SketchCow> LOTS of changes since we grabbed it.
[02:21] <db48x> lots of changes in mame too
[02:37] <SketchCow> Agreed
[02:38] <SketchCow> Well, I'm going to compile all the mame*.js.gz versions and shove them in, but I won't swap over the json files.
[03:36] <SketchCow> The building of those is happening, so that's good on a pure "this crap gets uploaded" way
[03:36] <SketchCow> But it is a problem (the keyboard thing) so I hope we can fix it.
[05:16] <SketchCow> Trivia, while we work this out: There are roughly 427 drivers in the Emularity ecosystem on Internet Archive.
[05:17] <SketchCow> 52 have been built over the last... couple hours or so.
[05:22] <SketchCow> So that'll happen, but we still have broken keyboard.js.
[05:47] *** wdna has joined #jsmess
[07:15] <SketchCow> 111 now.
[07:15] <SketchCow> So there's a good sign that the recompilation-per-month will be less than a day. Probably less than 5 hours.
[08:08] *** wdna has quit IRC (Quit: bye)
[09:27] <bai> I'm back home now, if you guys haven't figured out the keyboard stuff by the time I wake up I'll have a look at it
[14:58] <SketchCow> We have not and would love your input. The links I did up there showing two versions of the same driver
[14:58] <SketchCow> https://archive.org/details/arcade_bounty (Running MAMEZODIACK and the keyboard not working)                           
[14:59] <SketchCow> So, the compiling is now down to 343
[14:59] <SketchCow> So looks like at least 12 hours to swap up.
[15:06] <balrog> SketchCow: what's going on? JS keyboard issues, or something else too?
[15:06] <balrog> I'll leave the JS stuff to people more experienced with that side of things.
[15:38] <DFJustin> in related news debian has finally updated to 0.173 as well
[15:43] <balrog> yes :)
[16:02] <SketchCow> Getting on the road to drive south, but it looks like 13 hours is more like what compiling will be.
[16:03] <SketchCow> That said, I can frontload "the list" with the drivers that affect the most things, like all the consoles and computers, and then the rest is just drip-drapping in all the individual arcade games, so we "update" for 99% of what people care about in about 30 minutes after release.
[16:03] <SketchCow> So that's a notable improvement.