Skip to content
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

[Bug]: Should the widget controls scale down proportionally to the Layer size? #317

Closed
saif-ellafi opened this issue Jan 10, 2025 · 3 comments
Labels
bug Something isn't working stale Inactive issue

Comments

@saif-ellafi
Copy link
Contributor

Package Version

7.0.0

Flutter Version

3.27.1

Platforms

Android, iOS, Web, Windows, macOS, Linux

How to reproduce?

Hello,

I was wondering if this layer editing aspect should or could scale down its tools, to avoid this experience:

image

Essentially, a combination of zoom in and reducing the size of a Layer, may cause the tools of that Layer to clutter.

Best regards

Logs (optional)

No response

Example code (optional)

No response

Device Model (optional)

No response

@saif-ellafi saif-ellafi added the bug Something isn't working label Jan 10, 2025
@hm21
Copy link
Owner

hm21 commented Jan 10, 2025

The problem with scaling directly based on the layer size is that the buttons can become either too large or too small, depending on the scale factor, but I agree that this is an issue, and I plan to fix it.

Another problem is that when there are two layers, and you select the background layer, the interaction buttons can get hidden behind the top layer. After finishing the state history improvements until update 8.0.0, I’ll start working on this issue.

I think using overlays will help keep the interaction buttons on top. The buttons should also stay at a minimum distance from the layers, even when they are scaled down. This sounds maybe simple, but the calculations are tricky because they need to respect the transformations from cropping and rotating in the editor.

Copy link

This issue is stale because it has been open for 3 days with no activity.

@github-actions github-actions bot added the stale Inactive issue label Jan 14, 2025
Copy link

This issue was closed because it has been inactive for 5 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale Inactive issue
Projects
None yet
Development

No branches or pull requests

2 participants