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

Developer

Forums

Forums:

Hi,

If I have a application with two parts and this application can be accessed from two points. One way is enter the application part 1, then part2. The other way is enter the application through part2. If I "clear" from the first method, it'll exit gracefully. But for the second method, is there a way to suspend the application and go back to outside app.(like incoming calls, SMS, etc.), and come back in? The reason I want to do this is, I want to minimize the innitiation time. What is the memory issue there? Thank you.

Anybody have any idea? Thank you.

Anybody have any idea? Thank you.

Not sure if I understand your problem. What is "first method"/"second method"? Could you elaborate further.

Not sure if I understand your problem. What is "first method"/"second method"? Could you elaborate further.

Ok, let's say my applet is two parts: web browser and player. Usually, I access the player through browser. But, I can also access the player from local file manager. This particular file format can only be played by my player. If I play the file and return to the local file manager, the common sense is to disconnect, right. But I want to maintain that connection. I want to avoid starting the player again after innitial connection. I want to let the player (hence, the applet) to run on the background, hidden; while I can start playing another file quickly without restarting the player.
Is it possible? If so, what kind of issues (like memory, cache, resource, etc) I have to consider, comparing to exit the applet totally after I go back to the locl file manager?
Thank you.

Ok, let's say my applet is two parts: web browser and player. Usually, I access the player through browser. But, I can also access the player from local file manager. This particular file format can only be played by my player. If I play the file and return to the local file manager, the common sense is to disconnect, right. But I want to maintain that connection. I want to avoid starting the player again after innitial connection. I want to let the player (hence, the applet) to run on the background, hidden; while I can start playing another file quickly without restarting the player.
Is it possible? If so, what kind of issues (like memory, cache, resource, etc) I have to consider, comparing to exit the applet totally after I go back to the locl file manager?
Thank you.

Quote:I want to let the player (hence, the applet) to run on the background, hidden; while I can start playing another file quickly without restarting the player.
You can do so. When your application is hidden, it can not get any key events and you cann't access display.
In your EVT_APP_STOP event handler do the following:
*((boolean*)dwParam) = FALSE;
While going in hidden mode, you may want to release most of the resources.
You can think of subdividing the app into light weight main app and the worker/helper extension which does most of the work.
Be sure to check with TBT requirements.
ruben

Quote:I want to let the player (hence, the applet) to run on the background, hidden; while I can start playing another file quickly without restarting the player.
You can do so. When your application is hidden, it can not get any key events and you cann't access display.
In your EVT_APP_STOP event handler do the following:
*((boolean*)dwParam) = FALSE;
While going in hidden mode, you may want to release most of the resources.
You can think of subdividing the app into light weight main app and the worker/helper extension which does most of the work.
Be sure to check with TBT requirements.
ruben

Quote:Originally posted by ruben
You can do so. When your application is hidden, it can not get any key events and you cann't access display.
In your EVT_APP_STOP event handler do the following:
*((boolean*)dwParam) = FALSE;
While going in hidden mode, you may want to release most of the resources.
You can think of subdividing the app into light weight main app and the worker/helper extension which does most of the work.
Be sure to check with TBT requirements.
ruben
Thank you, Ruben, for quick reply.
So, I just need to maintain a minimized version of player, with all other resources released, right? When user wants to play another file, it'll start quickly and resources are resumed again?
Is there an example of it? I can't find in the sample applications.
Thank you.

Quote:Originally posted by ruben
You can do so. When your application is hidden, it can not get any key events and you cann't access display.
In your EVT_APP_STOP event handler do the following:
*((boolean*)dwParam) = FALSE;
While going in hidden mode, you may want to release most of the resources.
You can think of subdividing the app into light weight main app and the worker/helper extension which does most of the work.
Be sure to check with TBT requirements.
ruben
Thank you, Ruben, for quick reply.
So, I just need to maintain a minimized version of player, with all other resources released, right? When user wants to play another file, it'll start quickly and resources are resumed again?
Is there an example of it? I can't find in the sample applications.
Thank you.

No, there is no sample.

No, there is no sample.

So, I just need to maintain a minimized version of player, with all other resources released, right? When user wants to play another file, it'll start quickly and resources are resumed again?
Did I understand this correctly? A main application and a helper extension (player).
Thank you.

So, I just need to maintain a minimized version of player, with all other resources released, right? When user wants to play another file, it'll start quickly and resources are resumed again?
Did I understand this correctly? A main application and a helper extension (player).
Thank you.