-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
set and get row height,unit of measure are not uniform?!!!same with col width #279
Labels
confirmed
This issue can be reproduced
Comments
taomin597715379
pushed a commit
to taomin597715379/excelize
that referenced
this issue
Nov 24, 2018
Change-Id: I8a2c378af74a4070ab8e2bfb61eda31b03c0734a
xuri
added a commit
to JDavidVR/excelize
that referenced
this issue
Jul 11, 2023
… pixels conversion factor
jenbonzhang
pushed a commit
to jenbonzhang/excelize
that referenced
this issue
Oct 22, 2023
… pixels conversion factor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
the source code :
and the output:
I get the row height, it's 20, but I set another row to 20, and get 20. OK!!! but the result is not the same.
the actual row height is not the same. When setting row height, the unit of measure is the pound(Because the default unit of measurement of row height for Excel is pound).
But if it is not set, the unit of return value is pixel.
See source code:
So, there are two issues, one is:
In the function of
GetRowHeight
, the code should beif v.R == row && v.CustomHeight != false
, It's better to write this way, but it doesn't matter.the another one is:
the unit of measure of row height is not uniform。So when I insert images,you can see
source code is:
But, but, but,
source code:
it's so funny, ha!The logic of inserting pictures is problematic. When you insert the first picture, it’s ok! When you insert the second picture, you change the row height, and it's ok! But the first picture is not OK! The final effect should not be related to the order of setup. Do you think so?
The text was updated successfully, but these errors were encountered: