-
Notifications
You must be signed in to change notification settings - Fork 852
Trackball Overlapping after Flutter Upgrade #2205
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
Comments
Problem is solved after downgrading to Flutter 3.24.5 (still using updating syncfusion_flutter_charts 28.1.33) |
Hi @Shunt22, We have checked the mentioned scenario and tried to replicate the reported issue regarding the Trackball overlapping in the SfCartesianChart widget with the updated SDK version 3.27.0. However, we were unable to reproduce the issue on our end. We have attached the sample we used to test the scenario. Please review the attached sample, and if you are still encountering the issue, we kindly request that you replicate it in the attached sample and provide us with additional details about the specific scenario in which the issue occurs. This will help us assist you more effectively. Regards, |
Hi! I'm testing on Samsung SM-T220. Android 13. Here is the code:
|
Thanks for looking into this. And thank you @Shunt22 for also providing additional test-information! I pasted your code (in the video just used 1 instead of the linear value to show the moving overlay) into an iOS App and the issue is present like in my example above. On Android the problem is also present. I tested it also on real devices and the behavior is the same. Simulator.Screen.Recording.-.iPhone.16.Pro.-.2024-12-20.at.11.30.23.mp4 |
Hi @Shunt22 , We have replicated the reported issue regarding the Trackball overlapping in the SfCartesianChart widget with the updated SDK version 3.27.0 . The issue is scheduled to be fixed in our upcoming weekly patch release on December 31, 2024. We will notify you here once the release has been rolled out, and we appreciate your patience in the meantime. Regards, |
@Kaviyarasansf4298 Thanks a lot for the quick response and the fast rollout of the fix! |
Hi @lsrmg , We have validated the reported issue on our end and found that it is a framework-level issue involving an incorrect depth value for the drawPoints method in the canvas with line and polygon PointMode. This issue has been acknowledged and fixed by the Flutter team. In Charts, we used the drawPoints method with PointMode.polygon to render a FastLineSeries, enabling the rendering of a large number of data points with high performance. You can track the issue using the links below. Issue report link: flutter/flutter#160343 Issue fix: flutter/engine#56494 However, you can resolve this with the help of disabling the impeller in your project. Please refer to the following link to disable the impeller. iOS: https://docs.flutter.dev/perf/impeller#ios Android: https://docs.flutter.dev/perf/impeller#android macOS: https://docs.flutter.dev/perf/impeller#macos We will notify you once the reported issue is fixed and moved to the stable channel by the Flutter team. Thanks, |
Hi @lsrmg , The reported issue of the z-axis depth in the drawPoints method point mode as polygon has been fixed and included in the Flutter 3.27.2 SDK and we ensured that it works fine. Please upgrade the Flutter SDK version to the latest 3.27.2 to avoid the issue. If you have any more questions, please feel free to let us know we are always happy to help you. Thanks, |
The issue indeed seems to be resolved. |
The issue is solved for me too. Thanks a lot! |
Uh oh!
There was an error while loading. Please reload this page.
Bug description
After upgrading Flutter to 3.27.0 (from 3.24.4) the Z-axis for the Trackball are not working correctly anymore.
The same issue is present for Crosshair Tooltips for example.
(updating syncfusion_flutter_charts from 27.1.53 to 28.1.33 didn't resolve the issue)
Steps to reproduce
Code sample
Code sample
Screenshots or Video
Video demonstration
Screen.Recording.2024-12-13.at.17.03.05.mov
Stack Traces
Stack Traces
The text was updated successfully, but these errors were encountered: