Hello John,
Yes; please, use the app's File manager to add an specific image or a directory: then you can use the app's image's path into the Image variable of the "NavBar", even in designtime, that is, using the "NavBar" object inspector.
Hello John,
Yes; please, use the app's File manager to add an specific image or a directory: then you can use the app's image's path into the Image variable of the "NavBar", even in designtime, that is, using the "NavBar" object inspector.
Hello John,
About your first question, we can use the Image variable of the NavBar control. You can choose an 30px image in order to be used at the left of the NavBar, in which they called "NavBar's brand".
About your second question, certainly, apparently we can apply some gradient style to a NabVar, for example, by using the below code in the "Inline CSS" option of the app, suposing we have a "NavBar1" control in the app.
Hello to all,
Here is a new DecSoft App Builder release, with the below changes, fixes and enhancements:
Me too! :-) :-)
Hello to all,
Sorry to confuse you, Peter... my humor sense and my english... sorry for that. The point is that the answer of everything is 42, as you probably know... (google around this if you wanted :) and the new release of App Builder (which allows to specify a minimum length of characters to show the TypeAhead list) is also the release 42 of the year. I don't know why I want to made a joke around this!
Thanks for your answer Samuel! :-)
Hello Peter,
Hello to all,
Here is a new DecSoft App Builder release, with the below changes, fixes and enhancements:
Hello Peter,
When I read your post I supose that maybe the HTML must be in fact XHTML, but, in fact I try with "br" and also works... anyway, what matter here is that you got the point. :-)
Hello Peter,
Take a look at the below modified "TypeAhead" sample: I hope that more or less can suit what you need:
Copy the above code and save it in a file like "MyApp.ab". The open that app file with DecSoft App Builder and run it.
Hola Juan,
Me alegro. :-) Instalar Apache Cordova y sus dependencias no es sencillo, pero, una vez hecho... ya podemos comenzar a pensar en la propia app, que, es lo que nos interesa. A veces Apache Cordova hace de las suyas... pero hay bastante información en internet, puesto que se trata de un proyecto muy utilizado. De momento, siempre hemos conseguido salir adelante, eso sí, con más o menos trabajo por delante, es verdad. :-)
You're welcome! The point is that you got what you wanted. :-)
Hello Samuel,
Yes; the "$$hashkey" is added by AngularJS internally for their own purposes. The "problem" is that commonly we simply can ignore this property, except in case like what we are having here: we want to store the objects and therefore the objects are stored with their possible "$$hashkey" properties. Maybe this can be investigated in some way... but probably it's enough to "simply" iterate the objects before save it... in order to remove whatever properties that we don't want to store.
P.S. One thing to note: the "$$haskey" property are only added when the objects are part of a Report 's Data, for example, that is, commonly, we can have a list of objects or whatever structure... and nobody interfere in that objects: in this case the variable are assigned to a Report's Data, and then retrieved, and, here yes, the Report's processing added to their Data (our objects) the "$$hashkey", which may we need to remove, or not, depend on what we wanted.
Hello Samuel,
Thinking about... maybe your problem is exactly what I have in the "TodoApp" sample? That is,... what you want is to save a previously "reported data", and, at that time, the "$$hashKey" has been added behind the scene. So, when you try to load the saved data... a "$$haskey" property already exists in the objects, and therefore it's not possible to add a new one. So probably what you must to do is to delete the "$$haskey" property before save the object... and this is exactly what you can see in the "TodoApp" Ready event.
Hello Samuel,
Looking at the "TodoApp" sample... well... I remember that I deal with "$$hashKey"... but what I do is to delete that key from the objects, before saved it to the local storage. So it's not exactly your case, Samuel. If I am not wrong, what you must to do is to assert that every object in your array are unique, and, this can be reached by adding another property to the object which are unique.
But reading twice your message... now I am not sure if what I imagine (the required unique objects) can be the problem in your specific case... or may you need to delete the "$$hashKey" property (then yes, look at the "TodoApp" app's Ready event. Or maybe we are talking about other thing... so please, go ahead and post here whatever you consider that can help... in order to try to help you too! :-)
Yes; I think Samuel is right (thanks for your help here, sir). What the Typeahead control expected is an Array of strings, and not an Array of objects, so we must prepare the appropriate Array to be used from our Array of objects.
P.S. Just to add something... if we can provide to the app the right Array... instead of Array of object... that's better, because we no need to do it in the app itself. In other words, if we can do it in the server's side, better. If not, we can always do it in the app, of course.
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.
This website uses some useful cookies to store your preferences.