Open tatiang opened 3 years ago
Hi Tatian,
I think this property applies to the whole Screen, so it includes its children components. You may need to edit the picture yourself in an external editor to reduce its opacity, then add it to your project.
I have filed a bug report about this: I would say that the Screen itself shouldn't have an opacity property, but we could consider adding a Background Picture Opacity property.
Thanks, @jane-d-alt. I think you're right that screens don't really need an opacity property as long as each Background Picture has an opacity settings.
Platform
Thunkable X, legacy interface
Issue/Request Origin
Steps to Reproduce
*It would be great to have some clarification and documentation (ideally) about what value range the opacity property has. It seems like anything over 1 = 100%. Is that true?
Project Link
https://x.thunkable.com/copy/00a41c5d9f2f311c15de4ab37d846595
Expected Behavior
The DVL should have an independent opacity property that isn't affected by the screen's opacity value. It should be possible to display text in a DVL at full opacity (100%) while lowering the background element (screen, column, row, etc.) opacity.
Actual Behavior
The DVL's opacity gets lowered to the same value as the screen.