Posts by DecSoft

Hello John,

I never deal with something like that, but, may you can take a look at the MutationObserver interface.

Hello John,

I think there is no way to know when all the AJAX calls in the content page has been done: we can't control something like that. However, maybe we can use event delegation. I will talk about the jQuery event delegation: as a task for you, may you can find some possible vanilla JS to be used, so you no need to add the jQuery library as a content script.

If you add the jQuery library as a content script, you can write some code like the below in another content script or the WebExtContent app's event:

The above jQuery / Javascript code attach a click event handler to all the paragraphs in the body, but, not only the existing ones: also the possible paragraphs added later into the body.

Hello John,

If you refers to AB controls, we can use the value property in both the Text input control and the value property of the Textarea control, and, the items and the value properties in the Select control. Take a look at that help topics and post here if you have some further questions about it.

Hello John,

If we are talking about our own Ajax calls (for example, using jQuery), then yes... may we can do something about... however, if we are talking of the Ajax calls made by the content page... I think there is not a way to know that, John, at least in my knowledge. If you refer here what you are trying to do, maybe we can find a possible workaround, for example, maybe can be stupid, but, these days a page can't take too much time in order to be loaded, so, if we wait a few seconds (five, more?) may we can **asume** that all the things are already loaded...

Hello Mario,

Please, no problem nor inconvenience at all! I am happy to help when possible. So don't hesitate to post here everytime you think I (or may other of our mates) can do something for you. Have a nice weekend too (yes... if possible...)!

Hello Mario,

A bit more about the possible flag variable to be used. Before you made the HTTP call, you can set a flag variable in order to know if the work has been done or not. This variable can be set to "false", for example. In the HTTP control Done event, you can set that flag variable to "true". If no error occur and the user back to the main view, that flag variable is "true". If some error occur, since the Done code is not executed (after the error), then the flag variable is still "false", and you can know if in the main view.

It's just an idea, of course: I am not sure if that can be exactly what you wanted, but, I hope you got the idea. This kind of flag variable can maybe also combined with the app's ViewChange event: if the flag variable is "true", you allow the user to back to the main view from the another one: if the variable is "false", you cancel the navigation to the main view, or do something before if needed.

Hello Mario,

Thank you David!

I endet up with your fourth solution with two buttons one for select and one for capture.

Because and Android and iOS app only.

Thank you!

Always thank you for your trust!

Hello Mario,

I am near to understand your point, however, I am not completely sure. Please, let me to explain. Certainly, the situation is like you describe, and, an error occur, however, it's not a fatal error, that is, once the user back to the main view, everything in that view continue working as expected, even the ability to go again to the another view.

So what's the point to check if "self" is defined or not? I mean, if the error occur, your code after the error is not executed, but, nothing else... I supose that you do something if the error did not occur, but, if the error occur, because the user go back to the main view, then you do nothing (because your code is not executed) and then nothing happens...

If you need from the main view that something is well executed in the another view, then you can use a flag variable, so, if the done event of the Http control is well executed, your flag variable is "true", for example, and, if the error occur, that flag variable can be "false" (you can set to "false" when enter the view), so, you can check that flag variable in the main view, so you know if the work is done or not.

Another possible idea is to use the app's ChangeView event, which allows to look what is the next view and the prev view: we can event prevent the user to change to a view from another, for example, until some code has been executed. So please, let me know if all of these can help you and just post here if you want to explain me a bit more about or what to place any questions.

Hello John,

We can use the MouseEnter and MouseLeave events of the Image control.

Supose we set an "a.png" to the Image's Url property, then, in the MouseEnter event, we can write something like this:

... so we are changing the Image's Url to "b.png", and, in the MouseLeave event we can back to the original image:

Hello John,

Yes; must be some issue related with the cache and the Frame controls. I am sorry. I wil take a look when possible and try to see what can happen. Certainly the cache can have some issues like this: I'll try to do my best, but, certainly some issues can appear related with the cache and in particular with the Frame controls. I will take a look when possible!

Thank you for your kindly words, John!

Hello to all,

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

Read the entire product's history

Hello to all,

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

Read the entire product's history

Hello John,

Yes; certainly in the previous generation of AB we have the Master View. Instead of that, in the new generation of AB we have the Frame controls (not IFrame controls), which allows to do the same (share stuff between app's views) but in a more powerful way, since we can have several Frame controls inside an app's view, for example. You can take a look at the Frame sample app.

Hello John,

You're welcome, sir! :-)