Build 3.0.0.112 of xlsgen renders picture borders whenever these are being formatted.


Rendering picture borders in xlsgen (taken from a PDF generation snapshot)

The picture borders are rendered whether they are coming from a XLS or a XLSX file, and whether the picture is floating or inside a chart.

Build 3.0.0.111 of xlsgen improves the automatic source code generator in that whenever a chart has rich labels in the main title or axis titles, the automatic source code generator will create a label statement in the programming language chosen by the user. Before this build, the automatic source code generator would only create a label statement if the chart titles were not rich labels.

Build 3.0.0.110 of xlsgen has a fix related to default page setup details. Whenever a XLSX file would be opened, xlsgen would default a sheet's pagesetup orientation to landscape, even though Excel actually defaults to portrait, unless the sheet is actually a chart sheet. This is an undocumented feature in Excel and was not taken into account yet. Build 3.0.0.110 of xlsgen makes sure this is the case now.

Build 3.0.0.109 of xlsgen has a fix related to chart marker formatting. Whenever marker formatting are read from a chart in a XLS file (a marker is for instance a diamond displayed in each data point of a given series), not all formatting details were read consistently, causing marker formatting to be lost whenever the chart would be manipulated : copy, edit, ... This fix ensures that properties such as the size, foreground color, background color are read and preserved.

Build 3.0.0.108 of xlsgen has a fix related to chart legend positions in charts. Whenever reading the legend position in a chart from a XLS file, there would be a bug that prevented the position to be preserved consistently should the chart be manipulated : copy, edit, ...

Build 3.0.0.107 of xlsgen has a fix related to chart stack and stretched property, which is the property you can set to displays bar/lines/areas on top of each other rather than side by side. The bug was that by not reading this property properly in existing charts from XLS files, the property would be lost anytime the chart would be manipulated : copy, edit, ...