Screen Pops but lose control
I am trying to pop screens (per the API example) and am getting mixed results. Can someone please help me out. This seems to be the last issue I need to overcome with the player. Function popAnd...
Forum Discussion
I'm freakin tired so I don't know if I posted or not - I showed an example of how to use my factory, one thread (home) and what the considerations therein are. I must have killed it though. But, basically, I figured all this out.
If I had used normal software practices, I could have fixed this in 15 minutes. Unfortunately, my code was a hodge podge of futility so I've no one to blame but me. It's all good though. And, now that I get the SDK, I sincerely can't believe how easy it is and how I could have had ANY problem with it whatever. I could teach a kid to do this now.
BTW, it would be nice if someone opened up an open source project on the SDK. An eclipse plug in or perhaps a java API that outputs members as BrightScript or xml instantiation or anything with an IDE. About 90 percent of my problems were mispellings that are not caught until compile (as well as type declarations ";" at the ends of my calls... lol). Plus, writing in Emacs (better than nothin') is miserable for me.
I have a perfect channel coming together now. 🙂 I use roAssociative arrays to hold my screens BTW. Given that I'm tracking the user in one place, it should be impossible to navigate away from my focus unless you navigate all the way out of the app. I take it from your reply that you don't agree with that?
BTW, the reason I used the same message port in all threads was due to the API ("You can create a port per screen... but you should use just one"). Perhaps a little discussion of the consequences of doing that would be good at that point in the doc.
Thanks for your help.
Cheers,
Al
If I had used normal software practices, I could have fixed this in 15 minutes. Unfortunately, my code was a hodge podge of futility so I've no one to blame but me. It's all good though. And, now that I get the SDK, I sincerely can't believe how easy it is and how I could have had ANY problem with it whatever. I could teach a kid to do this now.
BTW, it would be nice if someone opened up an open source project on the SDK. An eclipse plug in or perhaps a java API that outputs members as BrightScript or xml instantiation or anything with an IDE. About 90 percent of my problems were mispellings that are not caught until compile (as well as type declarations ";" at the ends of my calls... lol). Plus, writing in Emacs (better than nothin') is miserable for me.
I have a perfect channel coming together now. 🙂 I use roAssociative arrays to hold my screens BTW. Given that I'm tracking the user in one place, it should be impossible to navigate away from my focus unless you navigate all the way out of the app. I take it from your reply that you don't agree with that?
BTW, the reason I used the same message port in all threads was due to the API ("You can create a port per screen... but you should use just one"). Perhaps a little discussion of the consequences of doing that would be good at that point in the doc.
Thanks for your help.
Cheers,
Al
