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
Transparency for layers/pad functions #74
Comments
Transparency is allowed by the |
If I understand this right, I am hearing two requests:
The answer to the first one is to take a look at
|
Thanks for the tips! I think I got what I want. I packaged it up in some
They're pretty similar to |
Looking at the implementation I'm not sure what these functions are supposed to do. Can you give a description of just the first one? |
It's more or less like the So
Is that clear enough? If not, I could make a screenshot of what I mean. |
That makes sense. Thanks! |
Hi,
first of all: I really like how this library feels, great job!
However, I have some problems laying out stuff for an ascii game. Consider two widgets I want to place in the top-right and bottom-left corner, respectively. I'd like that to work independent from the bounds of the containing widget. Is there a way without asking the container for its current size, e.g. reusing the
pad*
functions or something? It should also be composable, e.g. if I add other widgets to the container it should not influence the positioning of the already specified widgets.What I had in mind was similar to having a separate layer for each widget and then just
pad* Max
, but unfortunately the padding characters aren't transparent.What it boils down to, I guess, is: Is there a notion of transparency?
The text was updated successfully, but these errors were encountered: