Ryan,

First things first..
We have the following fields in the PAPAbstractType class. 
 private  byte[] field_60_anld;  // to do implement ANLD class & give getter & Setter 
 private  byte[] field_63_dttmPropRMark;  // DTTM class to be implemented
 private  byte[] field_64_numrm;  // NUMRM class to be implemented 
 private  short[] field_66_rgdxaTab;   // changed by Praveen, initially was byte

field_66_rgdxaTab was initially byte , but according to Spec it is short so I have 
changed 
it to short array in my LOCAL file . But in CVS its still byte, I guess.
Please see to it., also the setter & Getter.

Shouldn't we implement the ANLD ,DTTM ,NUMRM classes & fill in their fields. Now they 
are read as byte array.

Regarding PAPX Sprms, what should we do to sprmPHugePapx. (0x6645) The spec refers "fc 
in datastream", is it that from Mainstream 
find fc, take the grpprl & pass it to our unCompressProperty() function to uncompress 
it??


Thanks & Regards
Praveen






"Ryan Ackley" <[EMAIL PROTECTED]>
30/07/2003 18:37
Please respond to "POI Developers List"

 
        To:     "POI Developers List" <[EMAIL PROTECTED]>
        cc: 
        Subject:        Re: HWPF status

 


>  Should we keep the grpprl and offset parameters , because we are 
already
passing "param" to the function from which we can get the values we want.
>
> like eg:  for getting short value from "param" which is an int. :
> lspd[0] = (short)(param & 0x0000ffff);
> lspd[1] = (short)((param >> 16) & 0x0000ffff);

If you have coded out the necessity for it, then go for it.

> Before going to SEPX & TAPX I need to clarify some facts with you.

Ask away.

Ryan


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to