|
|
Post by janek on Jan 11, 2013 2:48:22 GMT -5
it's very minor bug, but I'll going to report it anyway.
My captain had 2XP to spend and I clicked "evasion" rapidly several times - evasion went up by 3 points and label at top of the screen said something like "you have -1 XP to spend".
After next level captain had only 1XP to spend, so it seems that this glitch can't give additional XP.
|
|
|
|
Post by Cory Trese on Jan 11, 2013 11:07:39 GMT -5
What device and Android OS version we can try to issue a device or version specific patch.
|
|
|
|
Post by Lt. Hathaway on Jan 11, 2013 18:15:28 GMT -5
I saw this as well, newest version, Play, Samsung Precedent.
|
|
|
|
Post by Cory Trese on Jan 11, 2013 20:57:31 GMT -5
What Android OS -- all of these different touchscreen behaviors depend on device, Android OS version and even sometimes device edition (1A, 1B, 2A, etc.)
|
|
|
|
Post by Lt. Hathaway on Jan 11, 2013 21:02:51 GMT -5
Android 2.2.2, the phone model is SCH - M828C.
|
|
|
|
Post by Cory Trese on Jan 11, 2013 22:16:28 GMT -5
I'll try to fix in the next release. The only option we know will fix it on all Androids for sure is to change the UI to be as follows.
1. Press the Button
2. Pop Up a confirmation "Are you sure?" [Yes] [No]
3. If yes, put up a spinning graphic, clear all state and wait about 1.2 seconds
4. If no interruptions in 1.2 seconds, update database, save state and close back to previous screen
I've added that to TA but it is kinda annoying to use.
I'll try an interim solution but it probably won't fix all versions of all phones (for example, we know StarFixer has a device with a touchscreen that breaks Google's documented rules of touch interface hardware.)
|
|
|
|
Post by janek on Jan 12, 2013 4:50:01 GMT -5
I have windfire S with android 2.3.5 and WildChild custom ROM. anyway this bug is very minor and I thought that adding some mutex/lock in code would fix it. If fixing this requires that much work I opt, that you better spend this time doing more importat things
Best regards
|
|
|
|
Post by Cory Trese on Jan 12, 2013 13:14:32 GMT -5
I have windfire S with android 2.3.5 and WildChild custom ROM. anyway this bug is very minor and I thought that adding some mutex/lock in code would fix it. If fixing this requires that much work I opt, that you better spend this time doing more importat things Best regards There are two locking mutex around the DB code and a third around the touchscreen interface. All coded to Google's recommended standards, just don't work across all devices and ROM. |
|
|
|
Post by janek on Jan 12, 2013 15:21:25 GMT -5
wow, what can I say... I'm just glad that I'm not an android programmer...
|
|
|
|
Post by Cory Trese on Jan 12, 2013 15:36:01 GMT -5
wow, what can I say... I'm just glad that I'm not an android programmer... Andrew and I went back over the code. We've got some ideas |
|
|
|
Post by Lt. Hathaway on Jan 14, 2013 10:27:38 GMT -5
Possibly due to Narvidian radiation or coding error, the top limit to strength and quickness seems to have been dropped. My strength 6 quickness 5 captain has meetings planed with his chaplain and armorer this afternoon.
|
|
|
|
Post by slayernz on Jan 14, 2013 18:30:56 GMT -5
Try as I might, my finger mashing technique just isn't fast enough to replicate this result  |
|
|
|
Post by Lt. Hathaway on Jan 14, 2013 21:01:41 GMT -5
Just for clarity, I'm reporting a new bug, not the negative XP bug. I went to spend my XP, and saw the strength and quickness buttons were no longer greyed out, so I spent several XP on them, and I have a squad with superhuman stats, like the str 6 qui 5 captain mentioned above.
|
|
|
|
Post by Cory Trese on Jan 15, 2013 0:23:29 GMT -5
Just for clarity, I'm reporting a new bug, not the negative XP bug. I went to spend my XP, and saw the strength and quickness buttons were no longer greyed out, so I spent several XP on them, and I have a squad with superhuman stats, like the str 6 qui 5 captain mentioned above. I'll look into it, probably introduced trying to chase the button mashing issues on some random devices. It helps us keep track of bugs if new bugs get new threads. |
|
