MixinNetwork / MixinNetwork/flutter-plugins
[desktop_drop] issue when using Responsive framework with scale factor
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 512
- Forks
- 292
- Avg merge
- 15h 8m
- Merged PRs (30d)
- 7
Description
First of all, I think I have to address that this is my first time contributing in open source issues so bear with me
What is the issue
The issue is that drop zone area would be shifted and wouldnt be centered to whatever the child widget is.
imagine the red point is where my cursor pointing
The issue happens when you use Responsive Framework package with desktop_drop package.
not sure if it happens with all platform but I'm using windows 10 and it happened with me.
from my testing this issue only happens when you use scale factor from responsive framework
this is my widget
Expected Behavior
The area wouldnt be shifted when using Responsive Framework
Current Behavior
The area of dropping is shifted away from the original child widget
Possible Solution
I tried an ugly solution that actually which is changing the factor scale in desktop drop package to be same as the one used in RF :
Steps to Reproduce
- Use Responsive frame work package with Desktop Drop
- use scale factor (other than 1)
- enjoy the chaos 👾
Context (Environment)
Global:
Flutter 3.3.9 • channel stable •
Tools • Dart 2.18.5 • DevTools 2.15.0
Windows 10
Project:
Dart:
sdk: ">=2.17.5 <3.0.0"
responsive_framework: ^0.2.0
desktop_drop: ^0.4.0
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.
Research direction
Reproduce the issue in Flutter on Windows 10 using responsive_framework with desktop_drop and a scale factor other than 1. Start by tracing how the drop zone is positioned relative to the child widget under scaling; no source file or test is named in the report. Done means the drop area remains aligned with and centered on the child widget.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100