Welcome, Guest. Please login or register.
Did you miss your activation email?

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - iwbnwif

Pages: [1]
1
Discussion | Обсуждение / Re: New user questions
« on: September 07, 2016, 11:58:19 AM »
Quote
Thanks to Alex Arin for the project   ;)

Yes, I totally agree.

2
Discussion | Обсуждение / Re: New user questions
« on: September 06, 2016, 05:32:03 PM »
Ah, thank you it is always much easier when there are some examples to follow ;).

I have to say that this is a seriously impressive project.

3
Discussion | Обсуждение / Re: New user questions
« on: September 06, 2016, 12:08:33 PM »
@Subst thank you for the link, it is a good place to get started and I will try to find some tutorials also.

4
Discussion | Обсуждение / Re: New user questions
« on: September 05, 2016, 10:51:09 PM »
Thank you, that is really great - everything you suggested exactly answers my problems.

I can do everything that I need to do, LimeReport really is the best tool.

Obviously I need to spend more time to learn the scripting language better, but everything else is clear.


5
Discussion | Обсуждение / New user questions
« on: August 31, 2016, 01:22:12 PM »
Hi, I have been trying out some reports and have collected a few areas that I haven't been able to find an answer to.

1. Is it possible to set a parameter or script such that a TextItem doesn't take any space in the report if it is empty. A bit like the printIfEmpty feature for bands, but on individual database fields.

So for example if an address is setup like this:

    addressline1
    addressline2
    state
    zip

and the field "addressline2" is empty for a given record, then the output would be like this:

    1600 Amphitheatre Parkway
    California <- no vertical space from the top line
    94043

instead of this:

    1600 Amphitheatre Parkway
                   <- space reserved for addressline2
    California
    94043

I tried a script like this:

Code: [Select]
$S{if(address.addressline2 == "") THIS.geometry.height=0}
but it gives a parser error. Actually, a "printIfEmpty" checkbox for textItems would be even better if that is possible  :)

2. Is it possible to set a space between a band and the next band if the "autoHeight" property is enabled? From what I found, an autoHeight band will always fit tightly to the bottom of the last object.

Similarly if I set the border for a band, it would be nice to have an adjustable gap between it and the border for the next band.

3. In the preview window, the zoom figure does not appear to relate to the actual zoom. For example, if I make it 100% zoom the paper size is much bigger than A4 on the screen. Is that because of my windows setup (Windows 10, dual monitor)?

4. How do I use the "format" property in the property inspector?

Sorry for the basic questions, but other than these things I was able to reproduce some quite complicated reports in a couple of hours, including learning LimeReport from scratch. The same reports took me days to setup in another tool, so big, big thanks!




6
Okay, thanks for getting back to me!

7
Firstly thank you for a truly amazing piece of software. This is really one of the best reporting tools I have seen :).

It is so good that I would like to attempt a port to wxWidgets (which is my main development framework). It might be an impossible project because some necessary classes are missing, but I would still like to give it a try.

wxWidgets has a permissive clause in their licence that allows users to use, copy, link, modify and distribute under their own terms, binary object code versions of works based on the Library.

I think this is incompatible with a 'raw' LGPL so I wonder if you would be prepared to either open a similar exception or provide a MIT or Apache licencing option?

I very much appreciate that an extraordinary amount of effort has gone into this work and you would like to protect that, so please consider this as a request with only the best intentions.

Pages: [1]