Quote: "There's no phones involved - just Windows."
Then maybe next time don't offer up a link stating this is the same issue when the link you gave was specific to a device that was not Windows and in fact clearly states several posts down it works fine on Windows!
It is very misleading, also another good reason to provide a working code snippet that reproduces your issue. This also applies to your most recent post detailing Text 0, you stated in your first post;
Quote: "It was reported here, but nothing has been fixed"
This is now debunked given you NEVER once stated(until after 2 responses) that it was Windows specific...in fact it was your code using commands no longer in use, had you provided a working snippet with correct information this would have been dealt with effectively much sooner.
Now you are saying;
Quote: "There's something a bit busted here...."
So how do we know if it is AppGameKit or once again your code? I therefore once again suggest you provide a working snippet that reproduces this error so as not to waste anybody else's time. We literally have no clue what is in your code. Is there a line in your code where the characters Text 0 exists for example? Don't get me wrong, you might get lucky, maybe an experienced user of AppGameKit knows exactly what this is about, but for the rest of us it is just stab in the dark style guess work!
Win 7 Pro 64 bit SP1, AMD A4-5300 APU 3.4GHz, 8GB DDR3, NVidia GeForce GTX 750 1GB GDDR5, ASUS A55BM-E
