Posts by DecSoft

Hello Tin,

With some time, I want to improve the forum, of course, for example, implementing some kind of "cookie login". The new forum have one big advantage: it's integrated in the website, no more an thirdparty software, so, for example, you can login it in the website (to view your purchased licenses, upgrade it, download previous major releases, etc.) and the same login works for the forum too. In fact, previously you must to login twice, Tin, one for the forum, and another one for your customer area.

It's a question of time that I improve the forum, but certainly I am busy with other projects too! :-)

Hola Julio,

Respecto de la primera cuestión, deberás darle un color de fondo a la vista que quieras poner a pantalla completa. Por ejemplo, puedes usar la pestaña Estilo del inspector de objetos, previa selección (clic) en la vista, y, establecer la propiedad "BackgroundColor" con un valor "#fff" (sin las comillas), por ejemplo. No necesitas usar la acción SetViewSize.

Respecto de la segunda cuestión, no estoy muy seguro de entenderla, pero, igual esto te sirve de algo en todo caso: las vistas de la app se sitúan dentro de un contenedor (DIV) con una clase clase "appView", y, dicho contenedor, además, se identifica con el nombre de la vista, es decir, tiene un atributo "id" que concide con el nombre de la vista.

No sé si esto te sirve de algo o no Julio. Añade alguna pregunta o detalla un poco más si lo ves necesario.

Hello Tin,

Ok! I will add it as a sample (number 174) in the next App Builder release. Thanks Tin! :-)

Hello Tin,

Thanks for sharing! I tested it and certainly works like a charm. :-)

Hello Tin,

Interesting stuff... thanks for share it with us Tin!

P.S. Sorry for the problems while edit a post here in the forum. Certainly I must do something about when possible.

Hello to all,

I think, if use variable to store data before view change can resolve this problem too.

The fact is that... what is the problem? :-) Because I think this is not a problem, but, the expected behaviour. Supose you want to alert the user before change to another view... well... you can do it... for example, you can use an MessageBox, and, only if the user press the Ok button (for example), you proceed with the view change, and, not in other case.

But I am only place here an "possible scenario"... and an possible "approach"... depend on what we wanted we can do one thing or another, but, the "AlertBox" problem described above is the expected behaviour... not really a problem to be solved, but something that works like expected.

Hello Tin,

No, you don't miss anything. :-) AB do not provide an Switch action, but the If, IfEx, Else and ElseIf actions. Of course, if you wanted to use the Javascript Switch, you can do it, between the StartJS and EndJS actions, that is, using Javsacript code.

Hello John,

About the first question, if you need to use pure Javascript to shown a view, you can do in this way:

About your second question, you describe the expected result. When we shown another view, the DOM of the previously one is removed, and, therefore, actions like AlertBox can't work like you expected.

Depend on what you want to do, you can do one or other thing. For example, if you try with the Alert action, you can see that, in this case, the alert is shown as you expected. But may you can also take other approach... depend on what you wanted...

Hello John,

Supose we have an Input1 control in View B. Then, even from View A, we can get the value of that control in the variable [Input1.Value].

On the other hand, I supose that you are showing View B with the ShowDialog action. If so, certainly the View B don't fit all the screen (this is how dialogs or modal views works), however, the user can't reach the View A until the View B are opened.

However, if you wanted that the View B occupy the space of the View A, then you can / must use actions like ShowView and ReplaceView, instead of the ShowDialog action.

Hello to all,

Some customers report to me and strange error with the font size of our apps when run in mobile browsers. The problem was introduced some releases ago, and, it's in the "viewport" meta tag, which are not correctly written in the app's HTML file.

This message is to encourage to the users to upgrade their App Builder copy to be ready with this error fix.

Hello Tin,

Before my last post I try something, but, without lucky. However, I wan to take another look when possible.

Hello Tin,

The problem with the sticky header (I already try it) is that we can't use any CSS code that works like expected in most browsers. Maybe we can find something that works in some browser, but not in others. This is the cause for what the header don't have an "sticky" option.

Hello Tin,

Finally I upgrade App Builder in order to try to fix the problem that you found. Certainly the problem is related with the Report's swipe left and right events. What I do for now is to avoid to refer to that events if we not really used it. Doing that the problem is fixed.

However, what if we want to use the swipe events? Then our report can't exceed the screen width, at least in touch screens and for now. If we stop to think a bit, certainly, if we wanted that events... we are stopping the scroll default behaviour...

Anyway, even when the issue can be probably considered solved (since the Report works now as expected, and, if we did not use the swipe events), probably I must work on this in the near future (due to some Javascript library update), and, maybe allows the swipe events also in this specific cases.

This, suposing that the above is possible... again, because, certainly, if we use the swipe events... we stop the default behaviour of the scroll, and, I don't know how to pass around this right now, if something like that is possible, and I am not sure right now if can be possible.

Thanks for your report Tin.

Hello Tin,

The sticky header is not a solution, and, as you mentioned, in fact the problem is other. Yes; you are right from the scratch: the problem is apparently related with the swipe events, even if you did not use it. The point that this did not occur previously, so, I am not quite sure how to fix the problem. But of course I will try it.

Hello Tin,

Thanks for the sample. Certainly, I can see what you say, and, it's a suprise to me, since I expect the right behaviour. Please, let me to investigate around and I will inform you here.