Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

:rolleyes: Does anybody know for sure which system events are generated when we press "red button" or END KEY?

I discovered that when I have my application running in background which sends requests to server and I press "red button" to leave another application running in foreground, my background application network activity terminates and I got numerous transport errors?

Thanks in advance!

you can't shut down the background application using END key, since background application can't receive key and these application are not part of foreground application stack/history.

you can't shut down the background application using END key, since background application can't receive key and these application are not part of foreground application stack/history.

Sorry if the description posted by me above caused some misunderstanding.
What I wanted to say is that I do not shut down the application. Actually, I can't do that. I mean that pressing END key causes foreground application to terminate its execution and, of course, it's ok. But at the same time pressing the END key somehow affects behaviour of the background application, the network activity is disrupted. I got transport error after that.

Sorry if the description posted by me above caused some misunderstanding.
What I wanted to say is that I do not shut down the application. Actually, I can't do that. I mean that pressing END key causes foreground application to terminate its execution and, of course, it's ok. But at the same time pressing the END key somehow affects behaviour of the background application, the network activity is disrupted. I got transport error after that.

That shouldn't happen, END key can't effect background application. Are you sending somekind of event from foreground to background application, or someother means of communication is happening which is causing this problem.

That shouldn't happen, END key can't effect background application. Are you sending somekind of event from foreground to background application, or someother means of communication is happening which is causing this problem.

Foreground application doesn't send any kind of event to the background application. However, it sends some data via socket to the background application. Could the issue described above be somehow related to this socket communication? Any ideas?
Thanks in advance.

Foreground application doesn't send any kind of event to the background application. However, it sends some data via socket to the background application. Could the issue described above be somehow related to this socket communication? Any ideas?
Thanks in advance.