Eric House ce26696a37 assert refcount never climbs after reaching 0 ... Looking for a common but not-yet-reproducible situation where the gamelock gets stuck preventing a game from being opened, usually related to a move arriving. One thing that looked wrong is it seemed possible to have the refcount drop to 0 then get increased again, causing somebody to thing he has a lock when it's actually unlocked. So assert to try to catch that case (and synchronize to make it much harder.)		2019-06-23 10:20:16 -07:00
..
app	assert refcount never climbs after reaching 0	2019-06-23 10:20:16 -07:00
gradle/wrapper	upgrade AS and gradle and with luck travis will work	2018-05-06 14:33:10 -07:00
img_src	tweak icons; make and add untrade	2017-12-30 15:07:11 -08:00
jni	replace oft-firing assertion with logging	2019-06-23 10:20:16 -07:00
res_src	Translated using Weblate (Japanese)	2019-06-23 10:19:00 -07:00
scripts	fix build script for new Play Store variant name	2019-06-23 10:20:16 -07:00
website	update web page (esp. fix style for device display)	2019-06-23 10:17:55 -07:00
.gitignore	ignore generated files	2017-08-22 07:52:15 -07:00
Application.mk	initial checkin of jni source and build scripts for android port	2010-01-02 19:10:08 +00:00
build.gradle	Let's test this jitpack stuff on Travis	2019-06-23 10:14:16 -07:00
gradle.properties	move some gradle files	2017-01-18 06:33:00 -08:00
gradlew	move some gradle files	2017-01-18 06:33:00 -08:00
gradlew.bat	more cleanup. Get Crittercism stuff compiling.	2017-01-18 19:03:36 -08:00
id_rsa_uploader.enc	try to fix travis: copy over .enc file	2017-09-11 06:47:59 -07:00
INSTALL.txt	update build instruction	2017-12-29 17:56:50 -08:00
settings.gradle	move some gradle files	2017-01-18 06:33:00 -08:00