Thanks for the quick reply Nick.
If that solution is feasibly then it would certainly solve the issue of
having to compile a custom version of POI. Allowing external code to
utilise the FormulaParser class which would be very handy indeed!
Cheers,
Tim
Nick Burch wrote:
On Fri, 12 Oct 2007, Tim Wilkins wrote:
Summing it up there is a comment from Avik Sengupta explaining that
you need to use the FormulaParser class to generate the array of
Ptg's and inspect the ReferencePtg and modify the row & column
attributes. This sounds like a good approach but I hit a problem with
the FormulaParser class requiring a Workbook instance that is not
publicly accessible from the HSSFWorkbook object.
I'm tempted to alter the FormulaParser so it accepts a HSSFWorkbook
too, then asks that for the underlying Workbook object. That way we
don't have to have a public getWorkbook() method (which might lead to
confusion on if you should use HSSFWorkbook or Workbook), but will
still allow you to easily do formula stuff
Does that sound sensible to other people? Also, would it help with
your problem?
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
