Posts by DecSoft

Hello Peter,

Checking your code in this online tool, apparently there is no problem. So, I suspect that maybe a code like that (particularly the "onclick" event) can cause some problems... or... anyway... maybe it's required more information about, a possible sample app to reproduce the problem, for example.

However, I think there is a better approach: identify the button, place some information inside in a "data" attribute (optionally, I do it below because I like it), and then, use a jQuery event delegate in order to be ready for the button's click. Doing that, we no need to place any event in the button itself, which can cause undesired problems like you experience.

The below code is all what we need, and, can be placed in the app view Show event, in order to initialize the map, place a sample marker, and prepare the appropriate marker's info window, with a button inside, which go to another app view when it's pressed.

Below you have the complete sample app for AB1: save the XML into a "MyApp.ab" file, and open it with AB:

Remember to set your Google Maps API key (using the app Files Manager).

Hello Michael,

It's possible to add virtually any Javascript library using the app Files manager, however, in this particular case, the momentjs library is already included by default by AB, so, you can use it without anything extra. Some date related functions can be planned, but, for now, you try with momentjs following the documentation, and, of course, if you need any help, post it here and we will try to help you, Michael.

Glad to know that you finally got it Peter! ;-)

Hello Peter,

If we talk specifically about the code that you shown, certainly there is a syntax error: a missing end bracket in the "for":

Hello to all,

Here is a new DecSoft App Builder with the below changes, fixes and enhancements:

Read the entire product's history

Hola Juan,

En efecto, si no me equivoco, se trataría de usar el evento "dismiss". Pero tendrá que hacer alguna prueba... no estoy seguro de si este evento se dispara también cuando el usuario cierra por fin el vídeo, esto es, vuelve a la app... incluso si ha visto el vídeo completamente. En el API del plugin no se menciona un evento tal que "videoFinished" o algo similar..., como puede ver en la documentación. Tal vez la única forma de saber si el usuario ha visto el vídeo... es cuando este se "cuente" (digo yo que así será) por parte de quien ofrece el anuncio...

No obstante, si nos fijamos en los eventos que soporta el plugin:

Tal vez también podría probar con el "onAdLeaveApp"... aunque creo que ando errado, puesto que, me parece que este evento se dispara cuando el usuario pulsa, en efecto, el enlace de la publicidad. Pero... no aplique acaso a los vídeos... o bien no es exactamente lo mismo que un evento tal que "videoFinished"...

Hello Michael,

I am here made some tests in the "Frame" sample app, and can't reproduce the problem (in fact I deal in the past with problems around the compiler cache related with the Frames controls and already apply some fixed)... if I made some change in the Frame's controls, that changes are reflected when the app is running. The same if I move the Frame controls around the app view which contains it, for example.

So please, first of all, check that you are using the very latest release of AB. Then, check that you are using the Debug button (and not the Run button) when you made changes and expect to view it when run the app. Remember that the Run button launch an existing compiled app, but do not save it firstly, nor compile it. The Debug button, instead, save the possible changes and then compile and launch the app. More information here.

If you continue experiencing the issue, please, try to reproduce the error, and post here the steps in order to reproduce it, then I can try to solve the possible bug.

Hello Michael,

Good to know it, because, certainly, there can be some issues with the compiler cache, which of course try to be perfect, but,... So I will to made some tests around the frames control and post here what I can found. (I am currently working in other tasks, so, please, be patience! And use the possible workaround if needed.... by moving the frame control (because 99,9% this causes the right cache files to be removed)...

Hello Michael,

If I am not wrong you are talking about the new generation of DecSoft App Builder. Then you made some changes in an app frame, and, that changes did not appear as expected when you run the app. If this correct? Certainly, can be a problem with the compiler cache. I will take a look around, Michael. Please, if you refer to other thing, don't hesitate to post it here. A possible work around is to move the frame control in which you shown the frame, since moving the control causes the compiler cache to be removed. But anyway I will take a look at this.

Hello to all,

Here is a new DecSoft App Builder with the below changes, fixes and enhancements:

Read the entire product's history

Hello Amin,

No problem! I am happy to help when possible. :-)

Hello Amin,

For sure something is "missing" here. I try to update the jQuery library and AngularJS to their latest versions without lucky. Certainly I understand the point of use the app Ready event instead of the view Show event. This is something that works as a charm in the current generation of AB, and, I use it in various apps. What happen in the previous generation of AB (in your discovered issue) is a mistery to me right now **, however, I find that we can use the app Ready event as you wanted, if we can use events delegation, that is, the below code, placed in the app Ready event, works as expected:

** Apparently what happen is more or less clear: when the app Ready event is fired (in principle, when the DOM is ready if the app is running in a browser), the app view HTML markup is not certainly ready to use, so, the elements that we wanted don't exists, and therefore we can't attach any event handler to it. Probably we must asume this "as is": we can't use the app Ready to attach events handlers, except if we delegate the events like in the above code. That... or use the view Show event, in which certainly the elements are ready to be used or manipulated.

Hello Amin,

This disturb me a bit, because, I think this cannot be considered a solution, however, if we use a "setTimeout", even as smaller as 100 milliseconds, then the code also works in the app Ready event:

I say it's not a solution... because I did not see it elegant, since, maybe the solution must be to know what really is happen... however, can be taken as a possible workaround, if we can't move the code into the view Show event, then use the app Ready one, but with the above "setTimeout", which certainly works...

I am not very friend to use something like the "setTimeout" for cases like this... so... my recommendation is to use the view Show event if possible.

Hello Amin,

Certainly I can see some "rare things" around your issue. For example, the app Ready is suposed to be fired once the DOM is ready (if the app is running in the browser) or when the device is ready (if the app is running in a Cordova platform like Android).

However, despiste the above, if we place a code like this in the app Ready event:

... what we can see is a "0" (zero), means there is no "test_id" element, and therefore we can't attach any event handler on it. However, if you place such alert before your event code handler, you can see that the event is fired... something unuseful, because we can't place such alert there...

I made several tests, however, nothing works as expected (for this specific case) in the app Ready event. If you can move your code into the view Show event, then the things works as expected. So the question is, can you move the code into the view Show event, Amin?

Hello to all,

Here is a new DecSoft App Builder with the below changes, fixes and enhancements:

Read the entire product's history