-
Notifications
You must be signed in to change notification settings - Fork 2
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
Is it possible to grey out inactive scraps? #21
Comments
I was going to do this with transparency, but due to issues in paper (the framework I'm using) or HTML canvas itself, large amounts of half-transparent objects were extremely slow. So I gave up on this idea. We could however do recolouring like XTherion does, though I find it very visually unappealing. This would mean recolouring every object every time a scrap change happens, but that should not be a problem on reasonably sized project files - especially since you can hide the other scraps and only show three or four at a time. |
great addition! like it very much! |
I didn't know that this is new behaviour, I thought you could change the visibility of any scrap, regardless of it being active (?). But yes I think this is how it should work anyway. |
Also, yes the localisation is still missing for that config option. |
I may not have thought this through properly, however...
Objects in inactive scraps are hard to distinguish from objects in active scraps.
We can hide inactive scraps but often I want to see the inactive scrap objects as context for the scrap I am drawing.
Inactive scrap objects can be identified by the fact that they cannot be selected, but this is not sufficient for me where the drawing might be a little complex.
Is it possible to make the colour/rendering of inactive scraps recessive or greyed out by default?
This way we can see them and use them for context while drawing adjacent scraps, but not inadvertently think they are part of the scrap we are currently drawing.
The text was updated successfully, but these errors were encountered: