Posts by DecSoft

Hello Peter,

I am now busy, but, want to think about. However, the Fixed (not scaled) style has that behaviour: since it's a fixed size, the screen must be at least the same than the fixed size, in order to see everything as expected. Said that, if what you wanted is an app working from smaller to larger screens, then probably the Scaled option is for you, as I shown you in the modified sample: you can see all the controls, from small to larger screens.

Hello Peter,

Here are my comments around the sample app that you sent to me. Please, take note about the changes that I made in the modified sample app which I send to you when publish this post:

1. You are using the app's Scale option set to "False": consider or just (in order to follow these advises, since I think you can get what you wanted) set the Scale option to "True".
2. Instead of use a 960px pixels height, use a 480px pixels height: the idea is that we can go beyond the app view, but, not necessarily by increasing the view's height: just place controls below the view bottom.

That's all. As you can see in my modified sample, we can now reach the bottom controls using the scroll (note the container which I place at the very bottom: it's to get some space between the latest bottom and the end of the view).

Try the app in a browser with a size of 320x480 pixels (which is the design size), and you can see how we can scroll the view to see all the controls. You can also try to increase the size of the browser, and see that the app scales reasonably too.

That's is in fact the way to get an app that can work from a small screen size to a more or less greater screen, in other words, from mobile to tablets. For more larger screens may can be a good idea to use the app's "MaxWidth" property, in order to avoid the controls to scale "too much".

You can try it by set the "MaxWidth" property to 1024, for example, and then run the app in a larger (desktop) screen to see the result. Take a look and tell me that do you think about, Peter.

Hello Peter,

Hello David, yes, I see your point, I tried to modify the view1.html and frame the containers in a row and "col-md-4" columns. This works in principle, but bootstrap does not know how to handle the container, so it is of no use.

I am not sure if can understand. You can try the below codes, and, certainly, see how Bootstrap deal as expected with the "container" and the "container-fluid", you can see how this containers are dealing in a different way, as expected.

When I change the apps size to be larger than the browser (eg. to 320 x 960 px for my portrait version) then you can scroll down the app but the upper 10%-15% is unreachable, you can not see it and you can not scroll up to it. Do you have an idea, how to change this?

I need a sample app to see what you refer, Peter. Send to my E-Mail a sample app, so I can take a look. On the other hand, take a look at the "Inputs" sample app: it's possible to place controls beyond the app view, allowing the user to scroll the view in order to see all the controls. Maybe this sample app can give you some alternative ideas.

Hello Peter,

You can't place different grid columns in different HTML controls. At least, that don't work as expected, since a "col" must be placed inside a "row". Depend on the target of your app, the grid system can be interesting or not. In my opinion, only if you want the app running in more or less larger screen, you can consider to use the grid system. In other case maybe that is not needed: even for larger screen, sometimes the grid system can be good, and, sometimes not necessary.

You did not loss the AB functionallity by using the HTML control: this control is one of the available ones, and, in fact one of the most powerfull, basically, because we can place in that control almost any HTML markup, for example, using the Bootstrap Grid system. Doing that requires a bit extra work, for example, to control the possible "buttons" (or other controls) placed inside the HTML control, however, this is perfectly possible.

Hello Peter,

Thanks for your kindly words: I hope you and yours are also good, Peter. About your first question, I need to take a look. Maybe it's certain problem that must be fixed. About your second question, it's possible to use the Bootstrap Grid system by using the HTML control. In fact, you can copy the below code and then paste it in an app view designer: the result is that a new HTML control is placed in the view with that HTML markup inside:

You can place in an HTML control almost any HTML markup, including buttons, rows and cols for the Bootstrap Grid system, etc. Just post here if you have an further question around this.

Hola Juan,

Gracias, hombre. Yo también espero que usted y los suyos estén bien. Respecto de lo que pregunta, ¿ha probado a usar el evento "BackButton" de la app? ¿Podría servirle?

Hello to all,

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

Hello Michael,

I publish right now a new DecSoft App Builder release wich fix the bug with the TAB key. Taking a look at the adaptative icons in Android, what we do is to follow the Apache Cordova documentation, so, if you experience some particular problem, please, post it here, so maybe I can find some information about that.

Hello to all,

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

Read the entire product's history

Hello Ryan,

Yes; both ways can be fine.

Hello Ryan,

If the option that we are trying to get do not exists what we get is an empty string.

No problem! And the same for you and yours, Ryan, stay safe! :-/

Hello Ryan,

Maybe you already use a variable name "current_crew_name" or "current_crew_lead_id" previously used in the app? It's the only think that I can think right now... so you can maybe try with options names like "__current_crew_name" and "__current_crew_lead_id", just to assert that that names are not already used for any variable in the app.

Hello Ryan,

I hope everything goes fine for you and yours. I can't reproduce the problem that you mention. The below code works as expected:

Look in your code for some possible typo errors, because, you must remember that JavaScript is case sensitive. There is a problem in your code in the below line:

Note that the last argument must be "String".

Hello to all,

Thanks, Amin, for share such information here. You are right, of course, Android and iOS can have different notifications' payloads.