oh yeah, totally. it can be extremely frustrating when the new stuff is underdocumented and of questionable quality and everyone is relying on you to get it working
If this weren't all so new to me, I might be more sure about whether or not it's my fault. But I'm floundering. Darn thing works fine in the emulator but not on the actual handset, and everywhere I look for answers, the people who have had similar problems have not been answered by any of the experts. (A couple of people had obvious goofs and did get answers. I don't have those particular goofs; I already checked.) The phone's firmware might be buggy. It wouldn't be the first time. Or I could have a really simple, stupid, obvious goof. I simply don't know.
seeing as how you're developing for a proprietary os, don't you get paid support along with the sdk? if it turns out to be buggy firmware you can take great pleasure in hitting the phone with a baseball bat :)
Nah, support is a joke developers are reluctant even to bring up until they've had a few stiff drinks. *sigh* Sleep soon. Sleep makes everything better, right? ...right? :-/
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
no subject
If this weren't all so new to me, I might be more sure about whether or not it's my fault. But I'm floundering. Darn thing works fine in the emulator but not on the actual handset, and everywhere I look for answers, the people who have had similar problems have not been answered by any of the experts. (A couple of people had obvious goofs and did get answers. I don't have those particular goofs; I already checked.) The phone's firmware might be buggy. It wouldn't be the first time. Or I could have a really simple, stupid, obvious goof. I simply don't know.
no subject
no subject
no subject