Hello to all,
Here is a new DecSoft HTML Compiler with the below changes, fixes and enhancements:
Hello to all,
Here is a new DecSoft HTML Compiler with the below changes, fixes and enhancements:
Hello to all,
Here is a new NeoPlugin npUtil with the below changes, fixes and enhancements:
Get more information and download individual NeoPlugins and the NeoPlugins Mega Pack from here.
Hello to all,
Here is a new NeoPlugin npEdge with the below changes, fixes and enhancements:
Get more information and download individual NeoPlugins and the NeoPlugins Mega Pack from here.
Hello to all,
Here is a new DecSoft App Builder with the below changes, fixes and enhancements:
Hello to all,
Here is a new DecSoft App Builder with the below changes, fixes and enhancements:
Hello Andrea,
There is no differences between AB1 and AB2 talking about Cordova plugins: we use the same Cordova plugins. I try with the sample included by AB2, and, right now, I also try with the "Camera4" sample of AB1, and, both of them work as expected. Note that the issue that you linked appear as "fixed", so, certainly there is a problem in the past, but, apparently has been fixed now.
Maybe you need to remove the "compiled" folder and compile the app from the scratch. Since the plugin work as expected here in both AB1 and AB2 (in both cases with the API 30 of Android), that must work also for you.
Hello Andrea,
First of all, thanks for share your solution. However, I try with the "CordovaCamera" sample app of AB2 and the sample (and the Camera plugin) works as expected for me also using the API 30 of Android. I update the current release of AB2, because I made some minor changes to the referred sample, but, in general, the plugin work as expected.
I suppose you are using AB1, but, I am not sure about what you want exactly or what of the AB1 camera related sample are you trying to use. If you refer to me what AB1 camera related sample are you trying to use or what you want maybe I can help you. My idea is that may you finally get the plugin working as expected, but, that the above code is not exactly the solution, to say like that, since I try here with the sample of AB2, and, basically we are using the same Cordova plugin.
P.S. May you can try with the "CordovaCamera" plugin of AB2 (please, download -do not update- the current release) to see if work as expected for you, since must do it, because it's working for me here.
Hello Mario,
I personally commonly use the "views.view1.http1.response" way since this works as expected even if we are in another view. Certainly the "view" variable must be taken with some precaution, since we can be in another view as you said. In the control help I use the first way. And now we can use the "self" variable even if we are in another view too. In fact the help refers to the "view" (inside events) variable like below:
Stores the current app view or dialog. This variable allow us to access to that view or dialog properties and methods and also their controls properties and methods. For example, you can access to a control properties using the variable "view.yourControlName", suposing the control is named "yourControlName".
However, may you are right and I can enhance the help, even when probably, if the view is the unexpected one, may we can imagine more or less easy that that is because we are not in the view to what we want to refer. May I can take a look at the help in order to add some information about this for the "view" variable.
Hello Mario,
I was tempted to propose some possible workaround, even when, certainly, the issue that you describes occurs. But then I figure out that the same issue can happen with other controls like the Websocket, AudioPlayer, VideoPlayer and Timer controls. So I decide to handle this and rewrite how the DecSoft App Builder compiler set the "self" variable of all the controls. I published a new release of the product right now as you can see in this forum post, Mario.
Hello to all,
Here is a new DecSoft App Builder with the below changes, fixes and enhancements:
Hello to all,
Here is a new DecSoft HTML Compiler with the below changes, fixes and enhancements:
Hello to all,
Here is a new DecSoft App Builder with the below changes, fixes and enhancements:
Hello Bryce,
About your first question, honestly I need to take a look at HTC 1 in order to see if that option really exists... and why? Because the idea is that the output file must be the same than the "index.html" file of our apps. And why? Because we app may need files, not included in the compiled executable, in order to properly work. For that reason HTC 2 do not include that specific option.
About your second question, certainly it's the system and the "icons cache" who determine the behaviour that you describes. However, if the icon is certainly changed (there is no error when compile the executables), then the real icon of the executable is what you provides, and, you can see that "real icon" if you copy or move the executable into another folder or another computer.
P.S. A possible workaround for the first question can be to use the DecSoft HTML Compiler CLI compiler. From DecSoft HTML Compiler is it possible to create a BAT file who uses the CLI compiler to compile our apps. It's possible then to edit this BAT file (or create a new one from the scratch) who compile the app and then move the executable file to another location.
Hello Bryce,
The local storage is managed by the app browser itself: is not saved in a file or internally managed by DecSoft HTML Compiler, but by the used chromium based browser itself. The user is not able to get it, but your app yes. I mean, the local storage is not removed when the app is closed, so, previously stored information it's available when the user starts the app again.
Hello Andrea,
For the case of AB1, you can certainly establish a timeout for the request like below:
So the above establish 10 seconds of timeout, means if after 10 seconds the server did not respond the Error event of the Http Client is fired with a "Status = -1" and "Response = null".
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.