Some issues with report pro designer
https://www.xsharp.info/forum/public-product/2140-rp-2-35-expression-editor-line-breaks-solved
- there's a bug in the parsing of the expression editor. If e.g. i put this in: "23.09.2020 Flügelschlagquartett (2 Klaviere + 2 Schlagzeuger)" + CRLF + "11.11.2020 Trio con Brio (Klaviertrio aus Copenhagen)" written on one line, the checker says: "expression valid" If i enter a linebreak (using CTRL-Enter) after the "CRLF +" part, i get "error in the expression".
EDIT: got it, it follows the same rule as in source, after the "+" has to follow a semi-colon...
-
if i want to make a new label report, it can't find "Label.sys" - my "Search everything" find's no such file on this computer, but the ol' 2.17k version works
-
Have a look, how i have to overlap the fields in the design, to get somewhat decent output. If i reduce the fieldheight only minimaly, the second line gets stripped from output. Feels like some mismatch between font size in designer and output...
-
if you remove "header and footer bands" from the section tab, "page properties" dissappears entirely
-
label report, two columns, 1cm midway distanced, have a look: the right label-border in the designer is painted at the position, where the left border of the second column-label starts, i.e. wronlgy includes the horzizontal gap value
-
i paint a field in design, -> align, center horizontally in margins - won't result in centering to the label width -> ok, if one reads margins as per paper - but there's no center in label.
- The problem with these expressions is that CRLF is not found by the macro compiler. In X# this is defined as a preprocessor constant and not a GLOBAL. If you replace CRLF in the expressions with e"\r\n" or with chr(13)+chr(10) then the expressions work fine
- I will included labels.sys in the next distribution package
- I will see what I can do.
- This was coded explicitly. You should set the size through the Column/Labels Properties dialog. and there was an error opening this dialog.
- I can confirm this and will fix this.
- I can conform this and will try to fix this too.
Updated forum post link: https://www.xsharp.eu/forum/topic?p=17107#p17107