GeekyAnts / GeekyAnts/GaugesFlutter
Interactivity problem
@Afroz-Shaikh is already working on this.
Since Jul 31, 2023.
- Dominant language
- Dart
- Stars
- 78
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Gauge is not interactive when the parent widget is a ListView
If you take the Temperature Controller showcase example and encapsulate the Stack widget in a ListView, the gauge stops being interactive. You won't be able to drag the RadialShapePointer properly.
To Reproduce
Steps to reproduce the behavior:
- Use the code of the Temperature Controller example from https://gauges-showcase.vercel.app
- Put the Stack widget in a ListView widget.
- Try to drag the gauge pointer.
- It won't move properly, because the ListView takes the focus away.
Expected behavior
The gauge should remain fully interactive even if it's in a scrollable view.
Additional context
https://github.com/GeekyAnts/GaugesFlutter/assets/78145538/a96b41d7-17d2-4274-8bf7-d5f3f318b698
Flutter Doctor
[√] Flutter (Channel stable, 3.10.6, on Microsoft Windows [Version 10.0.19045.3208], locale hu-HU)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[X] Chrome - develop for the web (Cannot find Chrome executable at .\Google\Chrome\Application\chrome.exe)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[X] Visual Studio - develop for Windows
X Visual Studio not installed; this is necessary for Windows development.
Download at https://visualstudio.microsoft.com/downloads/.
Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 2022.2)
[√] VS Code (version 1.80.2)
[√] Connected device (3 available)
[√] Network resources
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.