A modern programming language that makes developers happier.

kotlinlang

This used to work but the `clickable`  is not being applied anymore. What's the proper way to handle dynamic modifiers?
```val localModifier = Modifier
    .fillMaxWidth()
    .height(IntrinsicSize.Max)
    .apply {
        if (!disableClick) {
            this.clickable {
                Timber.w("Music CLicked")
                onMusicClick.invoke(music)
            }
        }
    }
    .padding(8.dp)```


I think `clickable` accepts a `enable` parameter. You can pass `!disableClick` there

<@U048X2H6PV4> this solved the problem and it looks 100x better now haha Thanks!

It is 100% a bug since calling `clickable` on a modifier creates a *new instance*

Also the previous code and the new one of setting `enable` are not equivalent at all.

The correct fix is to change `apply`  to `run`

&gt; It is 100% a bug since calling `clickable` on a modifier creates a *new instance*
Agree. Using let  or run will work

&gt; Also the previous code and the new one of setting `enable` are not equivalent. One always adds the clickable modifier and disables it while the other does not add the clickable at all
Surely they aren’t the same, but I think that’s what Tiago tries to achieve judging from the name of the parameter disableClick

Fully agree <@U048X2H6PV4>.

But removing the clickable modifier altogether is slightly better because clickable internally uses `Modifier.composed { ... }`  which has some *very slight* performance impact (cant remember the details)

<https://kotlinlang.slack.com/archives/CJLTWPH7S/p1669469299052219>

i use: ’modifier.then(if(a) Modifier.sth() else Modifier)