https://issues.apache.org/bugzilla/show_bug.cgi?id=46800

           Summary: No Workbook.getRepeatingRowsAndColumns method?
           Product: POI
           Version: 3.5-dev
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P3
         Component: HSSF
        AssignedTo: [email protected]
        ReportedBy: [email protected]


I hope this is the correct place for this, if it is not, please point me
elsewhere.

Using the POI 3.4 beta 4 build I have created a utility to convert Excel
Spreadsheets from Excel 97/HSSF format to the Excel 2007/XSSF format and vice
versa.  Its purpose is to automate the conversion of spreadsheets in real
timeon on a Linux system. Most of our spreadsheets are pretty basic (no charts,
pivot tables, or macros) and this solution works really well.

However I ran into one minor "snag".  The org.apache.poi.ss.usermodel.Workbook
interface, as well as the HSSFWorkbook and XSSFWorkbook classes all provide a
setRepeatingRowsAndColumns() method, but there isn't the converse
getRepeatingRowsAndColumns() method.

Is there a way, through the SS/HSSF/XSSF usermodels to discover the settings
for the repeating rows and columns as found in Excel's File->PageSetup->Sheet ? 

If not shouldn't this be added to the API?  Typically I would think that if one
can implement the "set", the "get" would be relatively straightforward to
implement but I haven't actually looked at the lower level structures to be
certain.  Maybe there is something I'm missing.

Please let me know if I need to provide more information, I would be glad to
post my class I wrote that does this Excel version coversion if that would help
clarify.
-alan ramsey

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to