Missing hover states on buttons : fill , stroke , background

[adambelis]

1. open fricion
2. hover over this buttons
   

there is no hover effect user does not have feebcakt that this are clickable buttons
bonus points if the label and icon were included as a clickable button
hover state

clicked state

[rodlie]

Sure, I also assume we need something to indicate (tooltip?) that you can change the color while hovering with:

• scroll = change hue
• scroll + shift = change value
• scroll + ctrl = change saturation
• click = open fill/stroke widget

[adambelis]

Oh yes that's not very discoverable. Maybe as a tooltip or infobar. On hover

[pgilfernandez]

May I have a look at this one?

[rodlie]

May I have a look at this one?

I don't feel like refactoring the toolbutton right now ;)

Feel free, but from my POV there are more important things to fix before release. IMHO this issue should be moved to 1.1.

[pgilfernandez]

I've been looking at this for 2 hours and I'm unable to style it... as you say it would need to refactor the whole toolbutton to allow changing it's style... so, I give up

[rodlie]

You can't style it, I use custom painting. I know what the problem is, but I didn't design it with hover state in mind. So some work is needed.

[pgilfernandez]

BTW, what other important things are pending to be fixed before release? I could have a look and help if the issues are not so difficult or inside my not big C++ knowledge...

[rodlie]

BTW, what other important things are pending to be fixed before release?

• Bug with flipping a path #204
• Auto smooting graph uses wrong values #167
• SVG Export: if Visibility range is ON, transforms are not working #300
• Docs

https://github.com/friction2d/friction/milestone/10

[pgilfernandez]

yeah, I was looking at milestone 1.0.0.
I might be able to fix #300, if not I will focus on Docs as I sometimes said I was gonna do but ended up doing other stuff...

Thanks

[rodlie]

My current plan:

Beta 3 (~Monday)

• Update the SDKs
• Merge open PRs tagged 1.0.0

RC 1

• Check for regressions
• Try to fix open issues tagged as bug for milestone 1.0.0
• Write basic docs
• Write full release notes for 1.0.0
• Review open issues for 1.0.0, move what we can't fix to milestone 1.1.0