You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using series->type:treemap, the height and width of the rectangle can only be obtained in the labelLayout function. After practice, it is speculated that the execution order of the label formatter in the underlying code implementation of echarts takes precedence over the execution order of the labelLayout function, so it is implemented in the label:formatter function. There is no functional logic such as "determining the text size or the number of display lines through the height and width of the rectangle".
What does the proposed API look like?
It is expected that the length and width data of the rectangle can also be obtained in the label formatter function.
The text was updated successfully, but these errors were encountered:
echarts-botbot
changed the title
[Feature]如何在series->type:treemap->label:formatter中获得矩形的高宽?
[Feature] 如何在series->type:treemap->label:formatter中获得矩形的高宽?
Apr 9, 2024
@dannishushu It seems you are not using English, I've helped translate the content automatically. To make your issue understood by more people and get helped, we'd like to suggest using English next time. 🤗
TRANSLATED
BODY
What problem does this feature solve?
When using series->type:treemap, the height and width of the rectangle can only be obtained in the labelLayout function. After practice, it is speculated that the execution order of the label formatter in the underlying code implementation of echarts takes precedence over the execution order of the labelLayout function, so it is implemented in the label:formatter function. There is no functional logic such as "determining the text size or the number of display lines through the height and width of the rectangle".
What does the proposed API look like?
It is expected that the length and width data of the rectangle can also be obtained in the label formatter function.
dannishushu
changed the title
[Feature] 如何在series->type:treemap->label:formatter中获得矩形的高宽?
[Feature] How can I get the rectangular when I use series->type:treemap->label:formatter function?
Apr 10, 2024
dannishushu
changed the title
[Feature] How can I get the rectangular when I use series->type:treemap->label:formatter function?
[Feature] How can I get the height and width of the rectangle when I use series->type:treemap->label:formatter function?
Apr 10, 2024
dannishushu
changed the title
[Feature] How can I get the height and width of the rectangle when I use series->type:treemap->label:formatter function?
[Feature] How to get the height and width of the rectangle when I use series->type:treemap->label:formatter function?
Apr 12, 2024
dannishushu
changed the title
[Feature] How to get the height and width of the rectangle when I use series->type:treemap->label:formatter function?
[Bug] Can't get the height and width of the rectangle when using series->type:treemap->label:formatter function
Apr 12, 2024
dannishushu
changed the title
[Bug] Can't get the height and width of the rectangle when using series->type:treemap->label:formatter function
[Feature] Can't get the height and width of the rectangle when using series->type:treemap->label:formatter function
Apr 12, 2024
What problem does this feature solve?
When using series->type:treemap, the height and width of the rectangle can only be obtained in the labelLayout function. After practice, it is speculated that the execution order of the label formatter in the underlying code implementation of echarts takes precedence over the execution order of the labelLayout function, so it is implemented in the label:formatter function. There is no functional logic such as "determining the text size or the number of display lines through the height and width of the rectangle".
What does the proposed API look like?
It is expected that the length and width data of the rectangle can also be obtained in the label formatter function.
The text was updated successfully, but these errors were encountered: