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

Easy Way to Return Current Scale of Object #156

Closed
TheCedarPrince opened this issue Sep 10, 2020 · 2 comments
Closed

Easy Way to Return Current Scale of Object #156

TheCedarPrince opened this issue Sep 10, 2020 · 2 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Milestone

Comments

@TheCedarPrince
Copy link
Member

Is your feature request related to a problem? Please explain.

Currently, it is not intuitive to retrieve the current scale of an object. One has to use the current method of val(:_current_scale) to gain access to the current scaling value of an object. This is not very user friendly at the moment.

Describe the solution you'd like
Perhaps we could somehow define a new struct that is associated with each new drawn shape or object. Maybe have the struct be optionally created for only when you want to capture relevant information about a particular object? I am not sure what would be the best approach currently.

Additional context
Currently, this method is invoked in #143 so when we get this issue figured out, we need to update that tutorial somewhat.

@TheCedarPrince TheCedarPrince added documentation Improvements or additions to documentation enhancement New feature or request labels Sep 10, 2020
@TheCedarPrince TheCedarPrince added this to the v0.2.x milestone Sep 28, 2020
@Wikunia
Copy link
Member

Wikunia commented Oct 17, 2020

I don't think that we want to support this current scale at all. Normal use case would be to scale a layer and move it to a different part of the screen. If one wants to scale a text one uses fontsize, for the circle the radius is used etc.

What do you think? Also see #234

@TheCedarPrince
Copy link
Member Author

I agree with you. I am going to close this issue because I think #234 rather takes care of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants