Hello Eduardo,
One possible way to achieve that is to use certain record's property. So, for example, the record can include an (or just have one) "Description" property, then we can look for this and shown when exists in the way that you wanted (occuping the three columns). If the record's "Description" is empty then the record are shown normally. Maybe another possible approach can be taken too. Please, download this Report.zip sample, take a look, and then tell me if something like that can works for you.
Hello Eduardo,
I am not quite sure that's is exactly what you wanted, but I modify the Report10 sample (which already uses the "colspan" in their footer) to use the "colspan" attribute in the Report's HTML property. Download this Report10.zip sample and take a look.
Hello Eduardo,
If I am understand well, what you wanted is to shown the Report's record's rows with the same height? If so, you can try with the "special" CSS class "ReportNameRow" like in the below CSS code, that can be placed in the app's Inline CSS option, for example:
On the other hand you can also try the below HTML code instead your own one:
Note how we do not include the "TR" HTML tag inside the Report's HTML property. Please, Eduardo, let me know if you have any further question.
Hello Antonio,
Thanks for the sample. I certainly run it but can't view nothing "particular"... the sample apparently works...on the other hand, please, take a look at this other sample that I prepare for you: Report.zip. They shown how we can use the values already set in the Report's Data variable. I honestly think that this can be the better approach, since we no need to perform calculations in the Report, but only look at the appropiate record's fields.
Hello Antonio,
Maybe you can provide me with a little app sample? Because the above code appear good in principle. But anyway, where the Report's Data source is come? If you control that source, why don't place some other field in the records so we can know if they must be "marked" or not? I means our records can have a field like "Expired", and then we can work with that field in some manners, for example, by assigning a CSS class to the expired records.
In other words, my opinion is that maybe is better to do the apropiate calculations before data arrive to the Report control. So you can add one or more fields to every record in order to work with them. What do you think about?
P.S. I am not now in my PC but I want to prepare some sample around this as quickly as possible. I am not sure if the below code (placed in the Report's HTML property) can work because I can't try it right now, but they can looks very similar to the working code:
Hello Antonio,
Since you are using AB code, you must do something like this:
* I asume we set the "Result" variables in the function's code, so we can use it after call the function.
* When I said above we can use two functions in "ng-if" I refer to the Report's HTML code, not the AB code.
Hello Antonio,
I think that is possible in the "ng-if". If you want call to other function inside another also is possible, but you must use certain variable(s) to store the function's results, or use pure Javascript functions & Javascript code.
Hello Antonio,
What we receive in the function is the record's index, so, certainly we can look for an "index - 1" record or "index + 1" record in the Report's Data variable.
Hello Antonio,
Certainly we can use an app's function also for the "ng-if" attribute. That function must return true or false. Take a look at this modified Report.zip sample. The appear to work not very good (in terms of efficency) when debugging (too much console messages) but apparently works more or less good when the application is build (no debug code present). Take a look at that and tell me if they can be useful or not for your particular case.
Hello Antonio,
I try here various possible approach in order to get your desired multiple headers, but none of them works like expected. Without the need to use a very custom control (made from HTML) I think another possible approach to take is to use CSS classes for certain records' rows, something that is possible using the record's IDs or "index", so maybe we can't create various headers but "simulates" it.
Please, take a look at this Report.zip sample and tell me what do you think about.
Hello to all,
Hi Mr. Esperalta
Very cute datepicker!
I see you used :$rootScope.datePickerIsOpened = true to activate it.
And I cannot find anyplace where you included it into the app?
I can't remember if the variable already exists declared in the application, but there is no matter here: we can declare it directly from the Javascript code.
Seems like it is built into angular?
Can you please direct us to a website if we want to look at more similar goodies hidden away in angular?
Thanks - and keep up the VERY good work!
We use stuff from the UI-Bootstrap project.
Hello Antonio,
I am not sure what to say, because I am not sure if can understand well. Certainly we can have one one header and footer per Report, then, probably this just "put down" your desire. However, what about to use more than one Report control? You know that we can use the Report's Data variable instead an URL, don't you? Then, we can prepare more than one "Data" variable for every Report. Please, let me know if this possbile approach sound too much stupid for your specific case or what.
Hello Antonio,
Yes; certainly before the today's change App Builder just test if the stuff has been previously generated, and if so, skip the generation. This means of course that we need to manually delete the "_Compiled" directory if we change the icon or splashs screens and want to use the new ones in an app's build, which is probably the problem that you experiment.
This don't occur anymore, since the Build command always refresh the icons and splashs now. :)
Hello Antonio,
Well. In fact App Builder do not generate the Cordova's graphics when debug the application. The "Run" command just launch a previously debugged or builded application. Do not compile nor build it. So the point is we can debug the application without generating the Cordova's graphics, but, when build the application, App Builder generates that stuff to refresh any possible changes.
In few words we no need to use the Build command everytime, but the Debug one. In this last case the Cordova's stuff is not generated at all (because in fact they are not needed). Only when Build the application (that is not required to debug it, but when deploy it) the Cordova's stuff is generated. I don't know if this can clarify somethings or if you have any other question Antonio.
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.