Samsung/Tizen.CircularUI

Button with either Background Color set Black or Transparent has an actively pressed color of default blue

axa88 opened this issue · 3 comments

axa88 commented

Describe the bug
The actively clicked background color of a Button is relative to its BackgroundColor:

ex: BackgroundColor = Color.DarkOrange

Not pressed:
image

Pressed:
image

But when the Button has set either BackgroundColor = Color.Black or BackgroundColor = Color.Transparent the actively pressed color is Color.Default a sort of blue:

Not pressed:
image

Pressed:
image

Id rather mark this as enhansment than a bug but unsure how to do so.

To Reproduce
Steps to reproduce the behavior:

  1. Create a Button, give it a BackgroundColor of Color.Black or Color.Transparent
  2. Click on it
  3. Notice that the clicked background is that of Color.Default and that doesn't necessarily correspond to black/transparent

Expected behavior
It is expected that either a more more aesthetically relative color is chosen for these 2 background colors or provide a way for the user to set them.
Perhaps a shade of gray for the Color.Black.
Perhaps no color set for Color.Transparent (keep it Transparent)

Environment:
Target Product Emulator 4.0 Release on 3.6 SDK (2.8.0.24)
Tizen Platform Version [Tizen 4.0.0]
Tizen.CircularUI Version [1.4.0]

Additional context
This is noticeable when attempting to set a color theme to your objects.
A black/transparent theme is infused with blue which seems out of place

jkpu commented

Thanks you for your issue reporting.
I have checked backend(Elmsharp.Button) of CircularUI. There is no way to set button pressed-color separating from background color.
And default(dark blue) color is native UI framework behavior. this is not CircularUI renderer's behavior.
Native UIFW can't be updated because this emul(Tizen 4.0) and watch device is already released.
This issue is restriction of Native, so I recommend you to use another button color instead of using black and transparent color.

axa88 commented

Yes sometimes changes are not feasible. Thanks for investigating the issues

I have the same problem, the changes are not feasible either. Users have to live with it unfortunately.
#345