Posts by DecSoft

Hello Harald,

No problem! Don't worry for that. The point is that I can't remember ALL... but I am sure that there are more than one reason to don't auto save the app before build or compile... but remember the Debug option! The Debug options is your friend if you want to auto save the possible changes before compile the app! Of course, when you want to build the app... you must save it... but I take this as something required: we want to prepare a build, so, we assert that we use the latest version, with the latest changes properly saved.

Yes; maybe can be an option... however, for some reason we leave the app unsaved when compile and build... I can't remember if for other reasons, but, maybe because save the possible changes is not something that we wanted. Or in other words, sometimes don't save the changes can be good: in fact we are trying an app version which is different to the "saved one", and this can be interesting. Remember, anyway, that the Debug button auto save the changes, Harald... you can simply use the Debug button... except when need to Build... if you doing that... the possible app's modifications are autosaved already, no need for any option. :-)

It's the same... my it's my mistake, Harald. We are talking here about the same: the app is modified. If you press the Debug button, then yes, the possible changes are automatically saved before compile. But not when you press the Build or the Compile button: in this case, if we want to compile the possile changes, we must save the app by ourself. This bring us the ability to don't save the changes, for example, which can be useful in certain situations.

Hello Harald,

I don't bet for Angular here... but the point is what kind of content its shown... I don't know... what I can say is that I have an iOS app which uses HTML and Report controls by just the "overflow-y" in "auto", and, the referred CSS rule for iOS... and there work as expected... Anyway, send the me a sample of the possible issue and I will try to take a look.

Hello Harald,

You means that the app's options are not saved automatically? If so, the point is that I am not quite sure if auto save it can be a good idea... it's better to know, that, we need to save the app, before compile or build it... if we want the latest changes to be applied.

Hello Harald,

This new AB release allows to provide a background and foreground icons for the Android versions that support adaptative icons. The app's icon is used anyway as the fallback for Android versions that don't support adaptative icons.

Hello Harald,

The problem while update a selected icon in the app's option dialog has been fixed in this new AB release.

Hello to all,

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

Read the entire product's history

Hello Harald,

More information about this... I remember now... and check it... that the HTML and Report controls already uses the "-webkit-overflow-scrolling: touch"... AB defines a CSS class named "ios-inertial-scroll", and, it's automatically assigned to HTML and Report controls.

Hello Harald,

Probably a sample of what you are doing is required here. I am not sure what the "wrapper" is, for example. My recomendation, however, is that you use an HTML control to place more or less larger text or content. If we place an HTML control, and set their CSS "overflow-y" to "auto", then the scroll appear automatically. Maybe you can apply the "-webkit-overflow-scrolling" rule to that HTML control, but maybe this is not really required... at least I don't remember to use it,... but I use in certain app various Reports and HTML controls in the described way, without problems.

Hello Harald,

Let me to take a look when possible. Maybe I see something that can help.

Hello Harald,

Maybe... it's rare anyway... But the question can be if to use a network drive can be a good idea, talking about the app files... because we wanted that the app's files can be "portable" to other systems too...

Hello Harald,

Sorry, but, I can't reproduce the problem here! (?)

Hello Harald,

Yes; I know about the first issue yesterday while work around the "adaptative icons". I will try to fix this. However, I can't reproduce the second one, that is, if we change the icon, the new icon is used when compile: be sure that you save the app when close the options dialog and before compile it.

Hello Harald,

Thanks for the link. Just for your information... you are right... or in other words... I am wrong... let me to explain. Taking a look here at the app that I know it's published in the Apple Store, I can see that we have here a transparent icon... but this is not the icon used by the app! In fact, we use a "white" icon... which is not transparent, so, probably for this reason we have no problem in the Apple Store.

I continue doing here some tests... my intention continue be to allows to select a background and a foreground icon, only to be used in the Android platforms that support this kind of icons. So the things remains equals than now for the other platforms. I need to work on it and made some other tests. I will post here on any progress.