Posts by DecSoft

Design for small screen devices but deploy also (without changes) in larger devices like tablets.

DecSoft HTML Compiler include a convenient Command Line Compiler, so you can compile your apps from the console.

Save money by purchasing our NeoPlugins bundles. Five, Ten and even the complete NeoPlugins collection at an incredible price!

Apache Cordova's official plugins are supported out of the box and there are hundreds of plugins ready to use.

Save time, resources and money creating apps for Android, iOS and more with the same base of code.

Create apps and expand their capabilities by using the world's popular programming language: Javascript.

Create multiplatform apps with DecSoft App Builder, including Android and iOS with the same base of code.

DecSoft HTML Compiler is easy to use: set your project's options and compile your apps and games in a nutshell.

DecSoft NeoPlugins are available in both runtime and designtime flavours to keep your apps as small as possible.

DecSoft App Builder integrates an Open AI assistant in order to assist you while developing your apps.

Take a look at our YouTube channel and subscribe to be notified about new videos!

Compile, convert your modern HTML apps and games into Microsoft Windows executable programs without dependencies.

Take a look at some frequently asked questions about us and our products!

DecSoft App Builder include a convenient Command Line Compiler, so you can compile your apps from the console.

DecSoft NeoPlugins put your VisualNeo projects into another level with +1,000 new actions for your apps.

Create modern HTML apps and games at another level making things impossible to do even by modern HTML apps and games.

Show threads by DecSoft

3348 posts found, page 52 of 224

DecSoft (In thread: New App Builder 2020.64)

Hello to all,

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


2020.64 (02/22/2020)

* Remove the scrollboxes used in the app options dock form and try to made it (all the options tabs) in order to be ready for use in some specific screen resolutions. Some customers report that he can reach some parts of the app options dialog: this release try to solve this. The same changes has been made in the program options dock form.

Read the entire product's history

DecSoft (In thread: Base64 Images with in HTML Object)

Hello Mark,

Yes; please, try an IMG markup like the below one:

<img v-bind:src="app.store.imload">

DecSoft (In thread: Open web url from html view control)

No problem, Mario! :-)

DecSoft (In thread: Llamar a los controles desde javascript)

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.

DecSoft (In thread: Open web url from html view control)

Hello Mario,

Yes; If I understand well, you have something like the below in an HTML control placed in an app view:


<a href="https://www.decsoftutils.com/" class="open-link">Open a link</a>

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):


// This is important to avoid the default links behaviour
views.view1.htmlContent.event.preventDefault();

// Look if there is a link which has been pressed by the user
if (views.view1.htmlContent.event.target.className.indexOf('open-link') !== -1) {

  // Get the URL from the link "href" attribute
  var
    url = views.view1.htmlContent.event.target.href;

  // If we are in a Cordova platorm (like Android)
  if (window.cordova) {

    // Use the InAppBrowser plugin with the "_system" argument
    app.cordova.inAppBrowser.open(url, '_system', '');

  } else {

    // In other platforms (like a browser) open a new window
    window.open(url);
  }
}

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.

DecSoft (In thread: New App Builder 2020.63)

Hello to all,

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


2020.63 (02/18/2020)

* Fix a bug in the app Files Manager when we move up or down the position of an script or style sheet previously added: due to this bug we get the styles are filled with the scripts, which is wrong, and, of course, causes problems when the app run. This release fix the bug and therefore we can now move up or down as expected both scripts and styles.

Read the entire product's history

DecSoft (In thread: Google maps in AB1)

No problem, Peter! Thanks for your kindly words! :-)

DecSoft (In thread: Google maps in AB1)

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.

StartJS

  // Create our map

  window.App.RootScope.Map = new google.maps.Map(document.getElementById('map'), {
    zoom: 12,
    //mapTypeId: 'satellite',
    center: {lat: 36.703306, lng: -4.452712},
    disableDefaultUI: true,
    zoomControl: false,
    mapTypeControl: false,
    scaleControl: false,
    streetViewControl: false,
    rotateControl: true,
    fullscreenControl: true,
    //gestureHandling: 'cooperative',
    mapTypeControlOptions: {
      style: google.maps.MapTypeControlStyle.DROPDOWN_MENU,
      mapTypeIds: ['satellite', 'roadmap', 'terrain', 'hybrid']
    },
    styles: [{
      elementType: 'labels.icon',
      stylers: [{visibility: 'off'}]
    }]
  });

  // Prepare our marker

  var
    marker = new google.maps.Marker({
      position: {lat: 36.703306, lng: -4.452712},
      map: window.App.RootScope.Map,
      title: 'Hello marker!'
    });

  // Use a function to show the marker's info window

  var
    showInfoWindow = function(marker) {
      var
        contentStr = '<div>';

      // Prepare the content of the window, in this sample, just a button, which identify the view
      // to go using the "view-name" data attribute. See bellow the "goto-view-button" event handler.

      contentStr = '<button data-view-name="View2" class="goto-view-button btn btn-sm btn-primary">Goto View2</button>';

      contentStr += '</div>';

      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

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

<?xml version="1.0" encoding="utf-8"?>
<AppBuilder Version="2019.56">
  <App>
    <ID>com.appbuilder</ID>
    <Name>New App 1</Name>
    <ShortName>New App 1</ShortName>
    <Version>1.0.0</Version>
    <Width>320</Width>
    <Height>480</Height>
    <Description>Another App Builder app</Description>
    <AuthorName>App Builder</AuthorName>
    <AuthorUrl>https://www.decsoftutils.com/</AuthorUrl>
    <AuthorEmail>info@decsoftutils.com</AuthorEmail>
    <Created>2020-02-13T20:02:18.524</Created>
    <Modified>2020-02-13T20:47:36.185</Modified>
    <InlineCSS>
      <![CDATA[
#map
{
  width: 100%;
  height: 100%;
}]]>
    </InlineCSS>
    <Metadata />
    <Webapp />
    <ProWebApp />
    <WebExtension />
    <Cordova>
      <General />
      <Plugins />
      <Electron />
      <Android />
      <IOS />
      <Windows />
      <Phonegap />
      <Platforms />
      <Splash />
      <Config />
      <Paths />
    </Cordova>
  </App>
  <Views>
    <View>
      <Name>Master</Name>
      <IsMaster>1</IsMaster>
      <Controls />
    </View>
    <View>
      <Name>View1</Name>
      <ShowEvent>
        <![CDATA[
StartJS

  // Create our map

  window.App.RootScope.Map = new google.maps.Map(document.getElementById('map'), {
    zoom: 12,
    //mapTypeId: 'satellite',
    center: {lat: 36.703306, lng: -4.452712},
    disableDefaultUI: true,
    zoomControl: false,
    mapTypeControl: false,
    scaleControl: false,
    streetViewControl: false,
    rotateControl: true,
    fullscreenControl: true,
    //gestureHandling: 'cooperative',
    mapTypeControlOptions: {
      style: google.maps.MapTypeControlStyle.DROPDOWN_MENU,
      mapTypeIds: ['satellite', 'roadmap', 'terrain', 'hybrid']
    },
    styles: [{
      elementType: 'labels.icon',
      stylers: [{visibility: 'off'}]
    }]
  });

  // Prepare our marker

  var
    marker = new google.maps.Marker({
      position: {lat: 36.703306, lng: -4.452712},
      map: window.App.RootScope.Map,
      title: 'Hello marker!'
    });

  // Use a function to show the marker's info window

  var
    showInfoWindow = function(marker) {
      var
        contentStr = '<div>';

      // Prepare the content of the window, in this sample, just a button, which identify the view
      // to go using the "view-name" data attribute. See bellow the "goto-view-button" event handler.

      contentStr = '<button data-view-name="View2" class="goto-view-button btn btn-sm btn-primary">Goto View2</button>';

      contentStr += '</div>';

      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]]>
      </ShowEvent>
      <Controls>
        <Control Role="6001">
          <Name>HtmlContent1</Name>
          <Top>16</Top>
          <Left>16</Left>
          <Width>288</Width>
          <Height>448</Height>
          <Html>
            <![CDATA[
<div id="map"></div>]]>
          </Html>
        </Control>
      </Controls>
    </View>
    <View>
      <Name>View2</Name>
      <Controls>
        <Control Role="2001">
          <Name>Button2</Name>
          <Top>136</Top>
          <Left>56</Left>
          <Width>200</Width>
          <Height>40</Height>
          <Text>
            <![CDATA[Back to View1]]>
          </Text>
          <Kind>primary</Kind>
          <TabIndex>0</TabIndex>
          <ClickEvent>
            <![CDATA[
ShowView "View1"]]>
          </ClickEvent>
        </Control>
      </Controls>
    </View>
  </Views>
  <Functions />
  <Files>
    <Styles />
    <Scripts>
      <Path Query="">https://maps.googleapis.com/maps/api/js</Path>
    </Scripts>
    <Folders />
    <Images />
    <Others />
  </Files>
  <Generator>
    <Name>App Builder</Name>
    <Version>2019.56 (2/10/2020)</Version>
    <Email>mailto:info@decsoftutils.com</Email>
    <Website>https://www.decsoftutils.com/</Website>
    <Copyright>©2020 App Builder by DecSoft</Copyright>
  </Generator>
</AppBuilder>

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

DecSoft (In thread: Date related functions in the new AB)

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.

DecSoft (In thread: Google maps in AB1)

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

DecSoft (In thread: Google maps in AB1)

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":

for (var i = 0; i < num_markers; i++) {
  window.App.GoogleMap.markers[i] = new google.maps.Marker({
    position: {lat:locations[i][1], lng:locations[i][2]},
    map: window.App.GoogleMap.Map,
    html: locations[i][0],
    id: i,
  });
} // This bracket is missing in your code

DecSoft (In thread: New App Builder 2020.62)

Hello to all,

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


2020.62 (02/09/2020)

* Made some additions in the documentation around the "app.setVar()" method. Basically we clearly establish that this method is used to set global reactive variables to be used in all app views, app dialogs and app frames. We extend the method documentation to add information about the global reactive variables, and, clearly establish that may such global reactive variables are not needed, and we can use just global variables instead, avoiding the cost in resources to maintain the referred global reactive variables.

* Fix a bug in the app.js template which causes that the app KeyUp event are not properly fired. It's a typo in the event handler name which has been fixed.

* Fix a bug which causes that the filter editbox of the app resources listbox become unuseful, since once we write any filter, the resource's editor take the focus, and therefore we can't continue writting in the filter editbox. This release fix that problem.

Read the entire product's history

DecSoft (In thread: Plugin ADMOB Video recompensa)

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:

// onAdLoaded
// onAdFailLoad
// onAdPresent
// onAdDismiss
// onAdLeaveApp

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"...

DecSoft (In thread: frame did not update after changes in it)

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.

DecSoft (In thread: frame did not update after changes in it)

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)...

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.