Posts by DecSoft

Hello Paolo,

I think that one of the abilities of that plugin is what you wanted. So you finally get it working? Please, post here if you need any specific help and we will try to help you.

Hello Paolo,

A couple of things... here is a sample of use of the mentioned Cordova plugin: do not explore all the Javascript API, but, you can read the documentation in order to do what you wanted: the sample prove that, as expected, we can use the plugin in our apps.

https://www.decsoftutils.com/_support/uploads/cordova-plugin-x-socialsharing.zip

On the other hand, maybe you want to try the "Share1" and "Share2" app samples, which use certain existing AB control and don't use any Cordova plugin (this means that the feature can work in all browsers, not only in Cordova compiled apps). You can decide what to use, of course. :-)

Hello Paolo,

There is not an easy way to use the "ngCordova" plugin that you refer, because they require certain dependencies that we can't provide, at least right now. However, in fact, that plugin uses this Cordova plugin:

https://github.com/EddyVerbruggen/SocialSharing-PhoneGap-Plugin

And there is no problem to use that plugin from our AB apps, just in the same way (using the plugin's Javascript API) than any other Cordova plugin, as we can see in various AB samples like "CordovaPlugins", "SendSMS" and others.

Please, Paolo, read the documentation of the Cordova plugin that I linked above, try it, and, if you find some specific problem or need more help, just post it here.

Hello Paolo,

Probably we need to use a Cordova plugin, however, can you explain a little more what you wanted to do?

Hello Adrian,

We already use FastClick to avoid certain "timing" issue between the tap and click on mobile browsers. If I am not wrong, your issue is not specifically related with that.

In principle, we no need touch events, because, at the end a "touchstart" event, for example, finally fire an "onclick" event, also in touch devices. Maybe you don't believe me, but, I have here now various "touch" events implemented in AB, and, after work on it, I am not sure if go ahead or not.

Adding these touch events can made the things more complex, and, I am not really sure if what you wanted amerited to include the touch events in AB. For example, the below code in an app's view Show event can do what you wanted for all the buttons in the view:

Believe me, Adrian, it's not a problem to add these touch events in AB, and, in fact, I already do it for the Push button control. However, I am not sure if go ahead and publish a new AB release with that events. Just because I think that that events can made somethings more complex than now.

Note that the above code, for example, don't prevent the Click event to be executed (this is one of the things that we must to think about), if you want to do that, you must use the "preventDefault" in the "startend" event, like in the below code:

The above code don't work in browsers who don't support the touch (in non touch devices, for example). If you want that the code works also in these browsers you must add the appropriate events, like in the below code:

Hello Adrian,

I understand what you need, however, certainly the Success event of the Report control is fired when the Data has been loaded, but don't work when we query the Report's. So, trying to find a possible workarond, maybe what we need to do is to query the Data variable by hand, in the client side or in the server side, then we can know the records of the Data variable before set it in the Report's control.

Hello Adrian,

Probably we must use here a bit of Javascript code, in order to count the visible Report's rows, for example, the below one:

The below do the same using jQuery, since it's available too:

Hello Amin,

You are right. I just don't know about this "space bar" behaviour, but, in some cases, certainly we must look at that.

Hello Amin,

Curious behaviour... Certainly we can ride on it by a code like the below one in the View's Click event:

No problem! Always thanks you for support our work. :-)

Hello Adrian,

Try to close AB and navigate to this directory: "C:\Users\[Your User Here]\Documents\AppBuilder\Config\"; then delete the "Toolbars.ini" file that you can see inside. Then start AB again and see if that solve the problem.

Hello Amin,

Always thanks you for support our work! :-)

Hello Amin,

If that works for you, it's good. However, I have some considerations. Firstly, maybe you can use "ng-show" or "ng-hide" for your specific purpose, instead of "ng-if". I am not sure right now about the "ng-if", but, the "ng-show" and "ng-hide" can be used in the same element that you wanted, that is, you no need to put it in a container, if you don't wanted that.

So we can do something like this, for example:

And, in the above case, the link is only shown if the Record's ID is greater than 1.

Hello Amin,

About the first question, certainly the "A" tag (or link) made the things a little bit complex, but not imposible. Supose we have an HTML code like the below one in a Report control:

Note that all the attributes are used above. The "href" do not point to any URL or file name. The "onclick" attribute is used to "return false", in order to prevent that the link do their job: goto another place. The "class" attribute is used later (see below) to identify the link, that is, to know that the user tap in a link that must made certain job. Finally, the "id" attribute is used to store the Record's ID, in this case, but, we can store another possible value, or use another "data" attribute if needed.

For the above Report's HTML code, we can place the below AB code in the Report's RowClick event:

The first thing we do above is to identify the link, that is, as you can see, we look if the clicked element (a link in our case) have the class "do-the-job". If that is thruth, then we execute the "Alert" action, which shown the ID of the link that the user tap. So we can identify if a particular link is what we expected. Then we can take some information of the link, like their ID attribute, in order to do what we wanted: goto another view, for example. Maybe in your specific case you can try with a "modal view" instead of a "normal view". But this is something that you must decide.

About your second question, the answer is yes: when the Report was press by the user, no matter if they do in a link or another element, the "[Report.Record]" variable contains the data of the pressed record in the Report control. So, if you want to use this information you can also use it when the link or other element is pressed. Please, go ahead if you have any further question about, Amin.

Hello Amin,

I feel that the forum "editor" is very bad, and, force us to do miracles to get something good and finally post what we wanted. I must work on this, of course. Anyway, certainly we can use the "ng-if", "ng-class", etc., without problems. It's something more or less advanced, but, we can use it. What I want to remark is that they are not the only solutions, but, certainly we can use it and works as expected. So just post here (if you can! :-( ) if you need any help on that.