Hello again,
Well. Apparently we can't go without the "window.App.RootScope" variable. I update right now the program give us access to "window.App.RootScope" and "window.App.Scope". The first variable can be used to access app variables, just like you do in your app. The second one can be used to access app functions.
The External Javascript tutorial has been updated as well the External app sample.
Sorry for the inconveniences and thanks for the advise Walter.
Hello Walter,
You are completely right and I am wrong. The problem is that some variables are accesibles and not others, depending in where the variables are defined. Please, sorry for the inconveniences. I am working right now for a solution.
Hello Walter,
In principle "window.App.Scope" is now the way to access app variables. In my tests I can access it without problems, then, please, assert you use the very latest version of App Builder not upgrading from the program, but downloading from their web: www.getappbuilder.com. Uninstall the program and then install the new release. If you continue having problems then I will take a look in more deep.
Hello Cícero,
Please, try this:
1º Uninstall App Builder from the Windows control panel
2º Delete these directories completely:
3º Download the latest App Builder release and install it:
http://www.getappbuilder.com/
I did not try in a VM, but App Builder must works in Windows 10, 8.1, 8 and 7.
In fact I use Windows 10 at this moment.
Hello Nelson,
Don't worry. In fact we can use the npEncodeDateTime action to prepare certain value (a "Delphi" datetime string, stored in the result variable) in order to do later two possible things: just use the value like you do above, for example, to show the datetime in an alertbox, or, more commonly, to be use it with other plugin related actions, in order to compare dates, increment days, get number of between days, etc.
The npWeeksBetween action, for example, offer us a sample of the npEncodeDateTime use.
Always thanks you Walter!
Hello,
Yes; if we wanted to show the checkbox over an image, then we need to play with the "z-index". In my test the checkbox appear over the image if assign a "z-index=9999" in both designtime (using the object inspector) or in runtime (using the SetStyle action). Try to assign a value like "9999" to the checkbox "z-index" Walter.
About the "no cache" meta tag, finally I add a new HTML tab into the app options dialog. From this new tab we can specify if App Builder must automatically add app information and prevent browsers cache using the index.html metadata, and, we can also specify custom metatags to be added into the refered index.html file.
Hello Walter,
This works to me in all browsers I test, including Chrome:
Then take care about "[myObject_Y]" and "[myObject_X]" variables. Also take care about "[myObject]" variable. This cannot be the same name than the Checkbox control. You can always specify the name of the control if you like:
About the "no-cache" meta tag, please, let me sometime in order to investigate it.
Hello again,
Just to say that the current available release of App Builder have a new Barcode control (based in the same Adobe Phonegap plugin you use), a new BarcodeScan action and a new Barcode app sample. Take a look if you like Jürgen and hope everyone found this new control useful! www.getappbuilder.com
Hello Jürgen,
Don't worry at all. Yes; in these scenarios we can use the ApplyModel action, in order to tell the GUI that some of our model variables changes. Use this action in your "BarcodeReaded" app function, after you set the "barcode result" variable.
Hello Jürgen,
Always thanks you and thanks to tell me you finally got it!
Hello David,
the solution with:
is really cool. Works really great.
Thanks for helping me.
Best regards
Jürgen
Hello again,
Please, update (if you like) your App Builder copy: I add the new External app sample, which show us how we can set an app variable and call an app function from external app Javascript code: www.getappbuilder.com
Hello Jürgen,
My latest post solution must works like expected, however, I forget than "window.App.RootScope" variable dot not give us access to app functions, which made the solution unuseful.
I made the appropiate changes right now in order to allow us to get access to app variables and app functions too. However, note that I rename "window.App.RootScope" to "window.App.Scope" to maintain some internal coherence.
You need to update your App Builder copy to get this changes ready! www.getappbuilder.com
And remember:
1º Call an app function when the barcode is ready:
Or:
If you need more help please tell me. If you finally got it please tell me too.
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.