-
Notifications
You must be signed in to change notification settings - Fork 389
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
Enhancement to add excel formula options (#1643) #1644
Enhancement to add excel formula options (#1643) #1644
Conversation
I researched the original changes of JT and compared it with the latest version of our master-branch. |
@@ -786,11 +787,12 @@ protected int getRichTextRunIndexForStart(List<RichTextRun> richTextRuns, int st | |||
* @param defaultFont The font to be used prior to the first RichTextRun. | |||
* @param widthMM The width of the output. | |||
* @param richTextRuns The list of RichTextRuns to be applied to the string | |||
* @return The heigh, in points, of a box big enough to contain the formatted | |||
* @param wrap The text use wrapped style |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment for wrap is not clear to me (and grammar errors)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will change it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's too much code changed to understand it.
Is all of this actually related to formulas?
I mean, you added a whole line-breaking algorithm.
From what I did decades ago when I developed the wordaxe hyphenation library including using it in a new a paragraph line-breaking algorithm for the Python ReportLab library, I know that those line-breaking algorithms are very fragile kind of program, where things can easily go wrong.
Is it possible for you to split the formula support and the layout enhancements you mentioned (which exactly?) into two separate PRs?
Of course there are some changes because the biggest change is to add the "formula"-options and give the formula-values the option for the correct styling on excel side. You talking about the "new a paragraph line-breaking algorithm" - which section do you mean exactly, do you mean the else-block with the "TextMeasurer measurer"? |
I mean the height calculation in |
I know and therefore my specific question for this method because, calculateTextHeightPoints-Method has know 2 options to calculate the height based on:
The options will be controled via "wrap"-variable which is comming from "cell.getCellStyle().getWrapText()". What is there the problem for you that the height "won't be calculated correctly" or that we get "exceptions" (which is currently catched)? What do you think about an additional uer-property - would it be helpful to handle it? I would make an additional comment on the title & ticket put we can leave it in the same PR. |
Thomas, if you say this is needed then I believe you :-). I'm +0.5 for merging. Even if I don't understand all the changes, probably they will have an effect only for cells with formulas, which are a new feature. Thus I think that the risk of breaking existing reports is near zero. |
Enhancement to add excel formula options (#1643)