From: John Yeung <gallium.arsen...@gmail.com>
Date: Wed, 30 Dec 2009 21:00:53 -0500
Local: Wed, Dec 30 2009 9:00 pm
Subject: Re: [pyxl] Bug in row.height ?
If only I had read this more carefully when I first opened it, I could
have saved myself hours of painful BIFF-documentation-reading and bit-by-bit (byte-reversed!) file inspection. (More comments below.) On Mon, Dec 28, 2009 at 6:18 PM, John Machin <sjmac...@lexicon.net> wrote: Given behavior A (which I independently discovered through much effort > Assuming hidden=0, collapsed=0, has_default_height=0, as far as I can > tell the following rules are applied: > 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 earlier today), I suggest the "tutorial" (de facto manual, available at python-excel.org as python-excel.pdf) be updated, because it currently says "Do not be fooled by the height attribute of the Row class, it does The height attribute certainly does more than nothing when combined As a vague idea (weaker than a suggestion), it might be easier, or at Oh, it might be useful to mention that the reason I was investigating John Y. 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.
| ||||||||||||||