From: John Machin <sjmac...@lexicon.net>
Date: Thu, 31 Dec 2009 14:10:31 +1100
Local: Wed, Dec 30 2009 10:10 pm
Subject: Re: [pyxl] Bug in row.height ?
On 31/12/2009 1:00 PM, John Yeung wrote:
> If only I had read this more carefully when I first opened it, I could A wise person once said: You can lead a horse to water, tie a brick to > have saved myself hours of painful BIFF-documentation-reading and > bit-by-bit (byte-reversed!) file inspection. (More comments below.) its nose, and kick it in the fundament with a size 12 Doc but you can't make it drink :-) > On Mon, Dec 28, 2009 at 6:18 PM, John Machin <sjmac...@lexicon.net> wrote: >> A. If height_mismatch is true, Excel will use the requested height. In >> B. Else: (1) Excel will calculate a row height high enough to accomodate > Given behavior A (which I independently discovered through much effort > "Do not be fooled by the height attribute of the Row class, it does > The height attribute certainly does more than nothing when combined Your vague idea covers behaviour A, leaving the tutorial to explain that > with height_mismatch. The font-based solution has its merits, but > isn't a perfect substitute for being able to pick a specific row > height. > As a vague idea (weaker than a suggestion), it might be easier, or at if behaviour B is required, they must not set height_mismatch to True etc etc. Your proposed method would do nothing else but set the height attribute to the arg value and setting height_mismatch to 1. Do you plan on not documenting why height_mismatch is set to 1? Perhaps you'd like to explain what you mean by "easier" and "less cryptic". > Oh, it might be useful to mention that the reason I was investigating I presume you didn't read far enough into that cryptic message to get to > setting the row height in the first place was because I couldn't coax > Excel into doing automatic height adjustment to accommodate wrapped > text in merged cells. the mention of the demo script :-( > (As far as I can tell, this is a bug in Excel Can you produce the required behaviour using the Excel UI? > 2000 and doesn't imply any deficiency in xlwt.) Cheers, You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| ||||||||||||||