Eric House c91865c991 use invite's channelNo for first incoming message ... A rare stall resulted when the invitee on channel 2 responded first. It would get assigned channel 1 and so the invitation on that channel would get deleted. If it hadn't already reached the mqtt server it would never be delivered. My fix is to use an invitation's channel instead IFF its address matches the return address of the incoming message. I'm not sure what happens if there's somehow a mix of invited (via rematch) and invited-some-other-way players. None of this matters for two-device games anyway.		2024-01-04 09:50:24 -08:00
..
android	cleanup -- should be no behavior/code change	2024-01-04 09:50:24 -08:00
common	use invite's channelNo for first incoming message	2024-01-04 09:50:24 -08:00
dawg	tweak xwd header output	2023-05-29 16:55:14 -07:00
debian	ignore debian build files	2012-01-04 18:11:29 -08:00
linux	get rid of ancient ifdef	2024-01-04 09:50:24 -08:00
newrelay	beginnings of new relay: shows persistence	2017-11-05 19:24:41 -08:00
relay	add manual message-send to fcm_loop for testing	2020-12-14 08:57:11 -08:00
scripts	more work on script	2014-02-26 07:52:18 -08:00
tests	allow to run multiple games at once	2005-09-14 05:12:07 +00:00
wasm	add git rev to display	2023-05-29 16:55:14 -07:00
Makefile	include all .xml and .java files, but only if they're not named in a .gitignore file in the same directory	2014-03-01 11:44:20 -08:00