I thought, after how poorly I was expressing everything else in this thread, to work up a picture of what I meant for this comment...
bogs wrote: ↑Mon Aug 05, 2019 9:35 pm
One thing I still don't understand is this, though.
1. I didn't change the transparency of the image in Lc, I created the rounded rect picture in GIMP and set the trasparency of it in there. How come the field sitting on top of it is also semi-transparent? After all,
2. it (shouldn't) be inheriting the images transparency, should it, like it would from the stack?

- If a picture is worth 1000 words,...
1.) The top 2 images I changed nothing but the window shape, the image is the same image for both.
2.) The 3rd stack has the same image as a solid black, and is set to window shape.
3.) The terminal window in the picture works as I would expect opacity *should* work, pretty much as SparkOut says, with each element's opacity set individually.
[-hh] wrote: ↑Mon Aug 05, 2019 11:42 pm
The transparency of the stack window should, as Mark said on my bug report, be controlled by the opaque of the stack (and be inherited).
Yes, this is exactly how I was thinking it should be working, but instead, it appears the transparency of the stack is being controlled by the transparency of the image (which is correct), and is affecting every control placed on it down the line (which is not correct), so that while the blendlevel of the stack (which is what should be inherited by the objects) is '0', the objects are instead inheriting the base image's alpha setting.
This seems to be a bug paralleling the one in the report you made, but one which is reproducible on all 3 desktop OS'es, in all versions of Lc I was able to test it in.
Or I could just be WAY off, I spend so much time way off I forget how to get back.