Posts by DecSoft

Hello to all,

Here is a new DecSoft HTML Compiler with the below changes, fixes and enhancements:

2021.32 (04/10/2021) * Prepare the Microsoft Edge Runtime to enable the Web Speech API. This API is quite experimental but interesting. You can find some examples of usage and get some fun from this Mozilla page: https://developer.mozilla.org/docs/Web/API/Web_Speech_API Thanks Leonardo for the idea!

Read the entire product's history

Hello to all,

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

2021.37 (04/09/2021) * Place a small text hint when entering an empty (not yet used) event of the app, app views, app dialogs, native visual and non visual controls and app plugins visual and non visual controls. The text hints inform us about the specific event that we are seeing and also give us information about possible keys to be used. * Remove an annoying flicker in the main toolbar Save All and Save buttons (basically the buttons alternates between the enabled / disabled states without apparently any reason). These buttons work as expected without any problem, however, the flicker referred to can certainly be a bit annoying distracting us about what we are doing. * Assign the proper images (we lost this in a previous release) for the popup / contextual menus of the app views list, the app dialogs list and app frames list.

Read the entire product's history

Hello to all,

Here is a new DecSoft HTML Compiler with the below changes, fixes and enhancements:

2021.31 (04/07/2021) * Appropriately handle app's files which contain spaces in their names: before this change / release the app's files with spaces cannot properly work if they are included in the app's executables. Thanks Greg for the report! * Fix a minor bug which causes that the icon which appear in the New app's index file dialog becomes the "help" instead of the "folder" when we over the mouse by the index file input or just select a new index file for the new app.

Read the entire product's history

Hello to all,

Here is a new DecSoft HTML Compiler with the below changes, fixes and enhancements:

2021.29 (04/04/2021) * Enhance the program's help to describe and provide samples of code for the new dhc.themes.* related external Javascript functions, which allows to deal with the app's executable themes at runtime. * Add the new Themes sample app, which shows how we can use the new dhc.themes.* related external Javascript functions, in order to get the list of the available themes for the app's executable, get the current established theme and set a specific theme at runtime. * Add the new dhc.themes.getThemes() external Javascript function, which we can use to retrieve a list of the available themes to be set for the app's executable. * Add the new dhc.themes.getTheme() external Javascript function, which we can use to know the current app's executable theme name. We can set a theme to be used at designtime, from the app's options. We can also set the app's executable theme at runtime by using the dhc.themes.setTheme() external Javascript function. * Add the new dhc.themes.setTheme() external Javascript function, which allows to establish the app's executable theme at runtime, in addition to use the app's options, which allows to establish the app's executable theme at designtime.

Read the entire product's history

Hello to all,

Here is a new DecSoft HTML Compiler with the below changes, fixes and enhancements:

2021.28 (04/01/2021) * Add the new FindWindow sample app, which show how we can use the dhc.shell.windows() in order to determine if a specific program is running in the user's computer, based in the program's windows' captions. * Add the new dhc.shell.windows() external Javascript function. This function retrieves all the windows' captions from the executing programs in the user's computer. This function can be useful, for example, do determine if a specific program is running or not, based in the program's windows' captions.

Read the entire product's history

Hello to all,

Here is a new DecSoft HTML Compiler with the below changes, fixes and enhancements:

2021.27 (03/31/2021) * Add the new dhc.folders.getAppExecutableDir() external Javascript function, which let us to know the absolute directory path of the app executable. This function can be useful to get that directory path, and to conform absolute paths for certain files, in order to be used with other Javascript functions like dhc.shell.command(), for example.

Read the entire product's history

Hello to all,

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

2021.35 (03/29/2021) * Continue with the efforts to make the program GUI ready for high DPI (Dot Per Inches) screen configurations. This release try to fix the item height for the control properties inspector and the control styles inspectors, as well the item height for the editor Quick Code List. Thanks Philip for your help!

Read the entire product's history

Hello to all,

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

2021.34 (03/28/2021) * In this product release we make several internal changes and enhancements in order to prepare the GUI (Graphic User Interface) to be ready for 4K monitors, and, in general, for screens with a DPI (Dot Per Inches) configuration larger than the used when designing the product, that is, the Windows default DPI configuration. The menu and toolbars icons, the dialogs and all the GUI forms and controls have been reviewed and tested to achieve this objective. We are particularly proud of this product release, because the work we expend on it and because the results that we finally can obtain. * In a previous release of the product we lost the ability to list in the integrated contextual help the available app plugins, as well their help. This release of the product reincorporates the app plugins list in the integrated contextual help. Additionally, the app plugins help button from the app options works again as expected: we lost this ability also in the past due to some changes. * We experience certain very, very rare bugs due to the lack of initialization for certain variables related with some events of the Edge Runtime WebView. This product release fixes these rare bugs by properly initializing the appropriate variables before trying to use it.

Read the entire product's history

Hello to all,

Here is a new DecSoft HTML Compiler with the below changes, fixes and enhancements:

2021.26 (03/28/2021) * In this product release we make several internal changes and enhancements in order to prepare the GUI (Graphic User Interface) to be ready for 4K monitors, and, in general, for screens with a DPI (Dot Per Inches) configuration larger than the used when designing the product, that is, the Windows default DPI configuration. The menu and toolbars icons, the dialogs and all the GUI forms and controls have been reviewed and tested to achieve this objective. We are particularly proud of this product release, because the work we expend on it and because the results that we finally can obtain. * We experience certain very, very rare bugs due to the lack of initialization for certain variables related with some events of the Edge Runtime WebView. This product release fixes these rare bugs by properly initializing the appropriate variables before trying to use it.

Read the entire product's history

Hello to all,

I hope you are well, Donald!! I want to add something into this thread, because I am dealing with this (exit the app) in the iOS platform for certain app. We have the cordova-plugin-app-exit plugin for Cordova, who works like a charm in the iOS platform, and, uses exactly the same instructions than in Android to exit the app, that is, the below one:

navigator.app.exitApp(); So, even when maybe this instructions need to be considered to be used (because maybe close an app is not something we must do in Android nor the iOS platforms), the point is that that instructions works in Android as expected, and, with the referred plugin, also in the iOS platform. So, if we really need to close the app... we can do it in both Android and iOS.

Hello to all,

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

2021.33 (03/14/2021) * Fix a wrong behaviour which occur when we launch the app using one of the possible available external browsers buttons in the program's main toolbar: the expected behaviour is that the app become launched in the external browser, but, also in the internal debugger browser. Before this change the app is launched in the external browser, but, not always in the internal browser, as is expected. * Close the app's debugger panel when stop the debugger process by clicking the Stop button of the program's main toolbar. Previously to this change the internal debugger HTTP server is deactivated when clicking the Stop button, but, the debugger panel are not closed. * Remove some hints from the app's debugger panel to avoid some problem (which do not occur everytime, but can cause that the program hang during a time) caused by that hints when the app is launched in the debugger browser (which is inside the debugger panel).

Read the entire product's history

Hola Jordi,

No estoy 100% seguro, pero, el evento "load" del IFrame se dispara cuando todos los recursos de la página dentro del Iframe han sido cargados: de este modo, si al hacer clic se requiriese de algún recurso (alguna llamada HTTP, por ejemplo), en efecto, es posible que se dispare el evento "load" del IFrame. Echa un vistazo a esta documentación de Mozilla, acaso algún atributo como "importance" pueda ser de tu interés.

Hola Jordi,

Es complicado decir algo... supongo que el "problema" está en la propia página que muestra el IFrame. Se me hace raro que no ocurra con "OpenWindow", pero, en fin, puede haber alguna particularidad de los "IFrames" que se me escapa. La cosa es que deberías intentar algo en la propia página que se muestra en el IFrame, y, no estoy seguro qué podría ser: tal vez podrías aprovechar eventos como "window.onunload", "window.onload"... esto es que depende ya un poco de cómo esté montada la página que se muestra en el IFrame. Tal vez aligerarla lo más posible para que la carga se produzca en el menor tiempo posible... se me hace complicado dar una respuesta, Jordi.

Hola Jordi,

A bote pronto se me ocurre que, si el "blanco" se produjese porque el Iframe tiene que cargar... tal vez puedas probar lo siguiente: ocultar el IFrame con otro control, por ejemplo, un HTML control, y, aprovechar el evento "Load" del IFrame, para ocultar dicho control HTML, una vez el IFrame se ha cargado. Aquí me da un poco de miedo que el evento "Load" del IFrame se disparase antes de la carga total... o que tardase más de la cuenta... pero podrías probar algo así: el control HTML podría contener un "spinner", algún texto o una imagen GIF, indicando la carga del IFrame.

Hola Jordi,

Varias cosas. He podido notar que en Firefox no se solicitan permisos de geolocalización, pero, sí se solicitan en Google Chrome, ahora bien, no si usamos un control IFrame al que añadimos un atributo "allow". La forma en que he logrado que se soliciten permisos en Google Chrome es usando un control HTML, dentro del cual ponemos un "iframe" ya con su atributo "allow".

Sin embargo, dicho lo anterior, también parece que es posible usar un control IFrame en lugar de un control HTML, de modo que Google Chrome nos solicite los permisos: la forma de hacerlo es dejando la propiedad "Url" del objeto IFrame vacía, y, utilizar el siguiente código en el evento Show de la vista:

StartJS $('#IFrame1 iframe').attr('allow', 'geolocation'); $('#IFrame1 iframe').attr('src', 'https://pruebas1.comolo.es'); EndJS

Como ves, la idea es poner el atributo "allow" y a continuación la URL del IFrame. Haciéndolo así Google Chrome nos pide los permisos adecuados. Ahora bien, el comportamiento del IFrame, de la página del IFrame, no parece correcto, como podrás ver si corres la app en Google Chrome con la consola de desarrollador abierta. Uno de los mensajes que obtenemos en la consola es el siguiente:

[Violation] Only request geolocation information in response to a user gesture.

Aparentemente, lo que quiere decir ese mensaje es que no debemos intentar la geolocalización del usuario sin que antes el usuario pulse en algún botón, por ejemplo. Es decir, el proceso de geolocalización debería comenzar después de que un usuario hiciese clic en algún botón, y, no de forma automática al cargarse la página.

Me pregunto si ese problema tiene algo que ver conque Firefox no nos pida los permisos de geolocalización... acaso si el proceso de geolocalización se iniciase después de que el usuario pulsase un botón, todo funcionaría como se espera también en Firefox. Quiero pensar que sí. Debes revisar en todo caso el comportamiento de la app funcionando en Google Chrome con la consola de desarrollador abierta: vas a ver la "violación" que he mencionado arriba, así como otros mensajes que pueden acaso ayudarte.