Hello to all,
This post is to inform about this new release, which try to solve the problem with the app options and program options dock forms, around the "scrollboxes" and the problem to reach some options in some specific "small" screen resolutions. I hope this new release can be useful to you!
Hello to all,
Here is a new DecSoft App Builder with the below changes, fixes and enhancements:
Read the entire product's history
Hello Mark,
Yes; please, try an IMG markup like the below one:
Hola Juan,
Si no me equivoco, lo que necesita está en el tutorial "External Javascript", que, puede encontrarse en la ayuda del programa y también online aquí. Si necesita otra información o tiene cualquier duda al respecto, no deje de añadir un mensaje en este hilo para tratar de ayudarle.
Hello Mario,
Yes; If I understand well, you have something like the below in an HTML control placed in an app view:
If that is correct (the link markup can change, but, I hope you got the point), probably the most easy way to handle the link is to use the Click event of the HTML control, so, we can place the below code (which asume an "htmlContent" control inside an "view1" app view):
Note the usage of the Cordova InAppBrowser plugin, which you must "check" in the Apache Cordova tab of the app options.
The above is just a way to handle the links, so, if you find it not really useful in your particular case, just post here, and I will try to help you with other possible ways, Mario.
Hello to all,
Here is a new DecSoft App Builder with the below changes, fixes and enhancements:
Read the entire product's history
No problem, Peter! Thanks for your kindly words! :-)
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:
';
window.App.RootScope.MapWindow = new google.maps.InfoWindow({
content: contentStr
});
window.App.RootScope.MapWindow.open(window.App.RootScope.Map, marker);
};
// Prepare a click handler for our marker
marker.addListener('click', function() {
// And show our marker's info window when the marker is clicked
showInfoWindow(this);
});
// Finally, this is an event delegate for all the existing ".goto-view-button"
$('body').on('click', '.goto-view-button', function () {
// Use the "view-name" data attribute to go the right app view
$scope.showView($(this).data('view-name'));
});
EndJS]]>
HtmlContent1
16
16
288
448