We recently updated t this version which added a number of functions we
required, particularly the streaming option for very large excel files and
does not have the new enum options.
Alternatively if you sort out all the java method calls using enum's I am
sure quite a few people on this list would look to use it.
Date: 07/11/2017 07:35 AM
Subject: Newsletter / Marketing: xssf cellstype setAlignment
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx>
Can anyone suggest how I can change the prototype and call to
ssCellStyle_setAlignment in Scott's HSSFR4 service program to work with
POI HSSF version 3.17? Seems the parm has changed from a short data type
to an enum. I can't figure out how to define the prototype to get the call
I've been successfully using POI HSSF version 3.6, but now trying to
convert to release 3.17.
In version 3.6 the setAlignment definition was;
void setAlignment(short align)
In version 3.17;
void setAlignment(HorizontalAlignment align)
This is in class org.apache.poi.ss.usermodel.CellStyle.
The prototype as defined in HSSF_H for version 3.6 is;
D PR EXTPROC(*JAVA
D : HSSF_CELLSTYLE_CLASS
D : 'setAlignment')
D align like(jshort) value
I've tried various data types and keep getting a compile error;
The type of parameter 2 specified for the call does not match the
This e-mail and any files transmitted with it may be privileged and
confidential and intended solely for the use of the individual or
entity to which it is addressed. If the reader of this message is
not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this
communication is strictly prohibited. If you have received this
e-mail in error, please notify the sender immediately by replying
to this e-mail and deleting it from your computer.
This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact