Preset browser LAF - hover?

[tomekslesicki]

Is it possible to add a hover state to the preset browser list with LAF, without crating a custom preset browser from the ground up just for that?

[d.healey]

@tomekslesicki For the list items?

[Christoph Hart]

with CSS, yes:

const var laf = Content.createLocalLookAndFeel();

Content.getComponent("FloatingTile1").setLocalLookAndFeel(laf);

laf.setInlineStyleSheet("

tr /** HTML table row => preset browser list item */
{
	background: red;
}

tr:hover
{
	background: green;
}

")

[d.healey]

With standard laf, obj.hover, no?

[tomekslesicki]

This post is deleted!

[tomekslesicki]

@d-healey yes, thank you.

@Christoph-Hart may I point a little inconsistency here? On some objects, obj.over works, on some it's obj.hover. Wouldn't it make sense to make both of these descriptions perform the same function in LAF?

[Christoph Hart]

@tomekslesicki I'm quoting your deleted post her because these are still valid questions:

thanks! How do I know which css classes correspond to which elements? Also - I remember seeing a commit when you allowed LAF and CSS to co-exist. How do I approach this?

This is documented in the Preset browser docs with a cheat sheet that shows all CSS identifiers for each component. However I've noticed that I haven't ported all the nice debugging tools that are available in the multipage dialog editor to the HISE CSS workflow, so I'll be doing that over time. For now I've added a simple overlay that shows some (but not all nested component IDs):

I remember seeing a commit when you allowed LAF and CSS to co-exist

Yes, this is now possible, you can give a single LAF object a style sheet as well as a script paint routine and it will use whatever is best (with the script functions always having the precedence over the style sheet definition with the exception of the popup menu styling which is CSS first).

On some objects, obj.over works, on some it's obj.hover. Wouldn't it make sense to make both of these descriptions perform the same function in LAF?

Yes that also annoyed me whenever I'm writing LAF functions. I obviously can't just correct the typo as this would break existing projects, but I can duplicate the property so that every LAF object that has over will get a hover property with the same value, then we can phase out over in 20+ years lol.