trad | C based language for building user interfaces | Runtime Evironment library

Basically, what you can do is pass a value in the command when the button is pressed, and change the label text then according to that. For passing an argument in command of the buttons, you can use lambda

You could do it this way :

I had success with this in the past:

That code sort of tries to have runTimer reach out and reuse the code prior to the call to it within the timer interval. Functions can't do that.

Instead, move all of the logic that you want to run for each interval callback, including the video.style.opacity = part, inside a function that you pass to setInterval. See *** comments:

As pointed out in the comments, you can use group_by from dplyr to accomplish this.

First, you can extract keywords for each comment/sentence. Then unnest so each keyword is in a separate row with a date.

Then, use group_by with both date and comment included (to get frequency for combination of date and keyword together). The use of summarise with n() will give number of mentions.

Here's a complete example:

First step for three keyed expressions: \$trad\s?\['([\w\-]+)']\['([\w\-]+)']\['([\w\-]+)'\]([^\[]) replace with lang('$1.$2.$3)$4. Second step for two keyed expressions: \$trad\s?\['([\w\-]+)']\['([\w\-]+)'\]([^\[]) replaced with lang('$1.$2')$3. I optimized the code to avoid more than 3 keys.

Please, change your Function with the below Code. First Get the parent Layout and then remove the child layout from a parent. I suggest you use only one linear layout.

In NewSal.kt Modify Below Function.

Your problem is related to covariance & contravariance. In some cases we can have a solution by declaring the view model abstract as interface instead of using abstract class (so that we can use covariance). The covariant interface can only expose get-only properties. So in this case I think you can change to that to keep your current design and I think it's reasonable because usually the ViewModel class should have readonly properties (once loaded). That prevents the properties from being accidentally modified after loaded (such as in the view scope). That makes sense and we can adapt to that design. The data instead can be loaded via the constructor (once).

Here is my proposed design with the most minimal change applied to your current design. Note that due to the constraint where Trad : BaseTrad which requires the BaseTrad to be an interface as well (cascading the variance of Item). So basically you need to turn 3 classes into 3 interfaces. I would use interface without hesitation but not sure if it's applicable in your case. However I'm pretty sure that this is the only solution if you want to keep your current generic design. The logic can be maintained as much as possible, by changing your current generic design, a lot of code will be changed as well.

The 3 interfaces you need are as follows (Note about using the keyword out and some properties being changed to get-only):

You can use conditional aggregation: