Hot corner application resume

Question

Hi, 

I have just encountered in strange behavior when I resumed my application (which I am developing) from the hot corner (top left).

This issue happens in 8.1, since my application is calling another application using URI scheme, and the new OS allows 2 applications or more to run side by side. 

Scenario:

1. Running my application, called it A. 

2. The second application is being called, B. 

3. Application A performing several actions. At the end it is being killed (hard coded).

4. At the top left corner the A|B tile is being displayed.

 

5. Pressing the application on the top left corner.

Now the problem begins: 

I want to call application A. It is being called, but then it is going to suspend and B is being called. 

How can I fix this? 

Thanks in advance!!

Answer 1

Don't crash your app. "At the end it is being killed (hard coded)." is your bug.

Apps shouldn't exit on their own. Leave that to the user and the process lifetime manager.

Answer 2

Well, 

That's not helping at all. 

As a developer, I would like to decide whether or not the application should continue its lifetime and not leave it to the user to decide(calculation issues inside my application for example).

As I see it, Windows 8.1 has a bug there since the user is trying to launch an application and he doesn't know which application will be launched, the left or the right.
Moreover, when it is launching it is performing back and forth, which doesn't contribute to the UI. 

Is there any other way to prevent this from happening?  

Answer 3

No, there isn't another way to prevent this. The app terminating itself is unexpected and won't necessarily be noticed by the shell until the it tries to get back to the app again later.

Apps are intended to be self-contained and there is no way provided for them to launch or communicate with specific other apps (outside of contracts). They can launch URIs, but have no control over the launched app and there is no two-way communication.

The expectation is that the launching app remains live and viable even after the URI has been launched.

--Rob