Hello,
Are you sure the About dialog shown your registration data? (Take a look at de Menu - Help - About)
If so, delete your application's compiled directory manually and try it again edunt.
Hello,
Are you sure the About dialog shown your registration data? (Take a look at de Menu - Help - About)
If so, delete your application's compiled directory manually and try it again edunt.
Hello Donald,
I think you mention above something about the Exit action and I do not answer it. So here is:
The Exit action can be used to exit the current script block, without execute any next possible actions.
That's the point! :)
Hello edunt,
The above is the action's editor dialog. Every app's action, app's function and plugin's actions who have one or more arguments have their own editor dialog. The editor dialog appear when we click an action with arguments from the action's dock panel; the editor dialog also appear if we choose an action with arguments from the code editor autocomplete list; and finally the editor dialog appear when double click an action line from the code editor.
Take a look at this video: https://www.youtube.com/watch?v=ZFWh0GBpD8o
Hello,
I think I get it now. Android actually wants it that way. The app is paused and android needs more memory it will close the least important app, usually the one not used for the longest time. Very interesting. There are a few exceptions, GPS is one.
That's the point! Furthermore an application can be killed by the system but their capture continue appearing into the application's list, so the user can change to that application again. Apparently the application is not terminated but we can only view an image capture of the application, so in fact the system can kill it and leave such capture only.
For this reason the "Pause" and "Resume" events exists: we can always save some application state in the "Pause" event (when our application enters in background) and then use the "Resume" event to restore the previously saved state. No matter if the application is killed or not after the "Pause" event.
A possible scenario can be the below one:
1º We start our application, which consists in a form to send information to our server.
2º We start to fill the form with some data, but, at that moment we receive an incomming call.
3º We go into the telephone application, so our application enters in background mode.
At this step we can use the "Pause" event in order to save the already filled form fields.
4º The phone call is not to large, so we just hangup and go back into our application.
At this point, if our application is not killed by the system, the "Resume" event is executed, so we can restore the state of our form in order to never loss the information previously provided by the user.
Now supose this other way in the same scenario:
4º We need to open others applications while we are answering the phone call.
5º The system are low of resouces, so begin to kill old applications to allow the new ones.
6º The phone call ends and we want to go back into our application to continue to fill the form.
At this point, if our application has been killed by the system before, then the "Resume" event is never executed. However, we save something previously in the "Pause" event, so, in any case, even if our application is restarted by the system or their "Resume" event is fired, we can fill our app's form with the previously saved data.
In fact this is what the user expect: they do not expect to fill the form from scratch again, and they don't understand if the applications has been paused, enters in background or killed by the system. They just expect the entered information is not loss and then no need to be provided again.
If we close our application by ourself we broke the above "circle", and, for example, no matter what the system shown in the applications' list: if we close the application, then the system always need to execute it from scratch, which is something more expensive compared to simply "resume" the application.
Hello,
Of course you can. Double click the action line and fill the appropiate action's editor edit box:
Hello,
I can't reproduce the problem. The CSS rule works for me.
Hello,
We can use the object inspector once select the application:
Also we can use the app's options dialog under the Style tab.
Hello Donald,
It's a bit confusing because we are thinking in Windows applications, and Windows applications have exit buttons, or, at least, have a "cross" in the title bar which allow us to close the applications. But the things rules in a different way in mobile operating systems.
Basically we can control the application life cycle using the "Pause" and "Resume" events. For example, if you want that the data dissapear when the applications is put in background, use the "Pause" event to clean the data you wanted.
When our application enters in background because the user just want to use other application, what the operating system does: close the application, maintain it in memory, is something out of our scope and we no need to worry about.
Hello Donald,
If our application is builded by Cordova, then we can use something like this in Android:
However, the above code do not work in any other platform. And why this piece of code is not added into App Builder like other actions at least to use it for Android? Because in fact we no need to worry about close applications at all, Donald. It's responsible of the system to maintain their memory clean and to close or not this or this other application when they wanted or needed.
What we can do instead is to take care about some application's events like Pause and Resume. This is something called "the application life cycle". If you think a little, Donald, what number of applications have "Close" or "Exit" button in the Android or other mobile world? This is something common in Windows, but not in mobile systems, in which the user simply go from one application to another, without care about how the system manages the resources.
Hello,
Thanks for posting edunt. Please, take a look at this DecSoft's blog post.
Hi to all,
Thanks edunt for your answer. I am not really an Adobe Phonegap lover (I prefer Apache Cordova instead), however, in situations like this Adobe Phonegap may can help us, that is, at least for the "IPA" files generation.
Hello,
Thanks for the explanation edunt.
Hello,
Well. I want to take a look so after downloading and installing the BlueStacks App Player I found we can install APK files inside. The program works well, except that my computer is apparently to old for him, due to the heavy resources the program requires. I am not sure if we can place our applications into some kind of "BlueStacks Store" or something like that.
Hello edunt,
My apologies. Certainly the above CSS code can be used to customize the progress bar of a MediaPlayer control, however, in fact you can't view the progressbar appropiately due to an error, introduced in the latest Videogular update. The problem is not exactly related itself with Videogular, but with their CSS integration into App Builder. So please, update your copy of App Builder edunt and tell me if the MediaPlayer progress bar works for you now.
Everybody can read the DecSoft support forum for learning purposes, however only DecSoft customers can post new threads. Purchase one or more licenses of some DecSoft products in order to give this and other benefits.
This website uses some useful cookies to store your preferences.