-
Notifications
You must be signed in to change notification settings - Fork 131
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
Step Y Axis missing Label. Bubble Indicator cut off at top. #34
Comments
It looks like the missing step number and top number is hidden if you have a background color set. So this is no longer an issue. |
You can close the issue then :) |
I still have an issue with the bubble indicator being cut off at the top. Is there some setting I'm missing? |
Could you add a simple code to reproduce the issue? What version of the
package are you using?
…On Mon, Aug 12, 2019, 5:45 AM Tim Ricciardi ***@***.***> wrote:
I still have an issue with the bubble indicator being cut off at the top.
Is there some setting I'm missing?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#34?email_source=notifications&email_token=ABFL3UANQ55YJSF6QT4REYTQEE5LFA5CNFSM4IK3UUGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4CFCJY#issuecomment-520376615>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABFL3UDGYZJ6P66GCHCIHEDQEE5LFANCNFSM4IK3UUGA>
.
|
That's because you are using a color on the parent container, check the
samples I put inside the library
…On Fri, Aug 16, 2019, 1:07 AM Dhuliang ***@***.***> wrote:
@diegoveloper <https://github.com/diegoveloper> Thanks for great job !
But tooltip will be cut off .
[image: image]
<https://user-images.githubusercontent.com/40012139/63146926-2d72b980-c02f-11e9-8f4d-5a2e50ebb7f9.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#34?email_source=notifications&email_token=ABFL3UF6ZX2B53KTT7ISPFTQEY73FA5CNFSM4IK3UUGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4NYGBQ#issuecomment-521896710>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABFL3UDNH4RQ5K6MFUPY6NLQEY73FANCNFSM4IK3UUGA>
.
|
I made the container colors Transparent and it's still cut off. |
All of your samples use whole numbers. Could it be that we are using decimals. So instead of 10 we have 10.2. |
Try using transparent color for the widget above the chart (hourly)
…On Fri, Aug 16, 2019, 8:37 AM Tim Ricciardi ***@***.***> wrote:
All of your samples use whole numbers. Could it be that we are using
decimals. So instead of 10 we have 10.2.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#34?email_source=notifications&email_token=ABFL3UGRF2V5WH623ZWIAKLQE2UTDA5CNFSM4IK3UUGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4OUIKQ#issuecomment-522011690>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABFL3UBYNLU262A2LVE5IX3QE2UTDANCNFSM4IK3UUGA>
.
|
Tried that. I don't think it's a color issue. I think the issue is the height calculation of the chart widget needs to be adjusted. Let me create a simple test example and see if I can recreate the issue. Maybe its my app. |
ok let me know if I can help you |
It looks like it's a combination of things that is causing the bubble to be cut off:
I modified sample1 to duplicate the issue.
|
I decided to file a separate issue, since the both cases seem different to me. |
could you use |
I rather wait until bubbleLabelCallback is merged, so I would try to kill two birds with one stone :-) |
That fixed it! Bubble Indicator is no longer cut off at the top. Thanks! |
We're having an issue when setting a Custom Scale chart to display the Y axis with steps set to 2.
Thank you for your efforts on this widget!
`Container(
color: Colors.transparent,
height: 250,
child: BezierChart(
bezierChartScale: BezierChartScale.CUSTOM,
xAxisCustomValues: const [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23],
footerValueBuilder: (double value) {
The text was updated successfully, but these errors were encountered: