Mailing-List: contact user-help@poi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "POI Users List" <user@poi.apache.org>
Message-ID: <BLU436-SMTP113F22BF3187C6CCD22D7D382DE0@phx.gbl>
User-Agent: Microsoft-MacOutlook/0.0.0.151217
Date: Mon, 1 Feb 2016 10:17:21 -0800
Subject: Re: Ability to set solid color on DataBarFormatting
From: Maheshwar Jayaraman <maheshwar_eng@hotmail.com>
To: POI Users List <user@poi.apache.org>
Thread-Topic: Ability to set solid color on DataBarFormatting
References: <BLU436-SMTP2378E9DF0FCFBE73EA3071082D80@phx.gbl>
 <4CBBBDD7FB566C4DB70EB7A04E0B466FC40FC8@Exchange3.exchange2.metalexmfg.com>
 <BLU437-SMTP75D65D2E12653748FC18A882D80@phx.gbl>
 <alpine.DEB.2.11.1601271837000.14695@urchin.earth.li>
In-Reply-To: <alpine.DEB.2.11.1601271837000.14695@urchin.earth.li>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

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" <apache@gagravarr.org> 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: user-unsubscribe@poi.apache.org
>For additional commands, e-mail: user-help@poi.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@poi.apache.org
For additional commands, e-mail: user-help@poi.apache.org