Nick, Thanks for the instructions. I realize I need to make changes to the underlying CT_DataBar class as well as that defines the actual attribute for gradient. That is a separate library. Is there a standard process for stacking such dependent changes across 2 libraries? Mahesh
On 1/27/16, 10:39 AM, "Nick Burch" <[email protected]> wrote: >On Tue, 26 Jan 2016, Maheshwar Jayaraman wrote: >> The default is gradient fill for a data bar. I wanted it to be a solid >> (I think it translates to a gradient=0 attribute). I spent enough time >> trying to set this via reflection that I think I can take a stab at >> adding a patch for this. I will read docs to see how to contribute and >> take it forward from there. > >First thing would be to produce new versions of >NewStyleConditionalFormattings.xls / NewStyleConditionalFormattings.xlsx >which add in examples of the formatting you want into additional columns > >Next, work out how to read that difference (unzip the XLSX file & read the >xml / use BiffViewer) > >Next, work out a sensible way to expose that difference in the conditional >formatting usermodel classes > >Now, add that to the usermodel, and matching lower level code as needed > >Then update the unit tests to check on read and write > >Finally, update the example to also generate these > >And then you're done :) > >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]
