I can't seem to do it for the life of me lol

Do I really need to keep setting the style manually?

@camdenorrb You can't bind CSS properties directly, but we have automatic functionality to add/remove classes based on some property. For the background issue, you can create an ObjectProperty<Paint>() that holds your color, and bind that to the property controlling the background color for your component.

@camdenorrb What's your specific requirement? Change between some colors based on som other state, or actually change the background color to be any color picked from a color picker or something? The best approach would vary depending on your use case.

Color picker @edvin

What control do you want to change the background color for?

Customizability

I meant, what class is the control you want to change background for?

Currently it's all handled in view

I don't think I'm able to convey my question in a meaningful way, so let me just create a quick example for you instead 🙂 It's been a long day 🙂 hehe

Alright 😛, I'm sorry I'm kinda new to this stuff aswell

Color_picker.kt

The

colorProperty

is bound to the colorPicker, and the backgroundValue will update accordingly, converting the color into a

Background

object, which is then bound to the

backgroundProperty

of the Form.

(It seams we've forgotten to add a property

colorpicker

builder to support direct binding, will add it now.

Ok, I'll give it a go :3

bandicam 2018-11-20 21-15-59-475.mp4

@Sergio Casero - an example fragment similar to what you described?

Is exactly the code I have, yes, (but I don't move the code to fragment yet)

I've committed a saner version of the

colorpicker

builder so now you can write

colorpicker(colorProperty)

instead.

@gtnarg @Sergio Casero Here is an improved version of the progress view/fragment:

-.kt

i think the problem that i am having is that changing the search string will not trigger the filtered list to update / rerun the predicate

how can i wire that up ?

@Nikky Are you using a

SortedFilteredList

? If so, call

filterWhen

on it and pass in the

textProperty

of your input as the first parameter and then the predicate function as the second.

can i add additional triggers ?

i want to also have a set of checkboxes that wil ltranslate int oa ObservableSet

currently i did this:

val filtered = allStrings.filtered { !it.filtered }

    val String.filtered: Boolean get() {
        return !this.contains(searchText.get())
    }

@Nikky I think I have an example of additional triggers and also multiple checkboxes that affects the filtering somewhere. I think the code is pretty old (from our CRM system) so it might not be best practices, but I'll have a look, hang on

Ah, here it is.. Basically what you can do is to set the

predicate

property of a

SortedFilteredList

to be a function that evaluates how many conditions you want and return true or false for each row:

_No_best_practices_here_.kt