07-26-2012 09:09 AM - edited 07-26-2012 09:13 AM
I dont really know is it receiving events, because my Playbook freeze, and i need to restart it. I will try this with setting z order to -10 before destroying it.
07-26-2012 09:25 AM
Tried with setting z order to -10 before destroy it and its not helping, same behaviour.
07-30-2012 02:46 PM
Are you able to identify which method call causes the crash?
07-30-2012 03:15 PM
Nope, Pb just freeze when that method which call payments is finished, it just stops responding to any user action. I think app is still running, but dont respond to any event anymore.
07-30-2012 03:19 PM
When this happens, are you able to switch between applications by using the system's upward swipe gesture?
07-30-2012 03:46 PM
No, nothing, only solution is to restart PB
07-31-2012 03:41 PM
A good approach would be to shrink your implementation until you figure out what causes the crash - can you try this? Knowing the source of the crash will help us tremendously;
08-01-2012 04:33 AM - edited 08-01-2012 04:40 AM
Well, problem is that line where i set z order of that native window. If i dont set it, app wont freeze, but native window will not be visible at all and payments will not be possible. For now, i will make some workaround for it, will notice user that after payment app will close, and that behaviour should be present until Cascades are out (then i will implement this with foreign window).
Martin, thx on your suggestions, i cant spend anymore time on this, i will do as i said above, and make new version when Cascades are out.
08-01-2012 10:05 AM
Good luck, I will post if I find anything for this.
Martin