elementos | Composable reactive state management | Reactive Programming library

You're running into the error since this.state.myText is a string. You can use [...this.state.myText] to create an array of the characters in the string. You might want to initialize the myText state variable to an empty string for clarity. The input field value is set to an empty string even though the initial value is [] since it gets converted to a string - [].toString() => ''.

If you're trying to clear and repopulate the second DataTable when you click on a different row in the first table, you'll need 'destroy: true' in your initialisation. You can add an Ajax call in the DataTable initialisation as well.

It might be better to have the second table initialised in a separate function, then pass the variable from table 1 as a parameter e.g.

When you say you are assigning a video/mp4 type URL to the src of a then the URL you provide has to point to an mp4 video.

You are pointing at HTML documents. The video element doesn't support HTML document as the source (because HTML documents are not videos).

The element isn't yet visible, that's why you get the not interactable error, also the className method doesn't match multiple classes.

Solution

Find the element by xpath and use the JavascriptExecutor component to scroll to that element after you can click it.

If I understood your problem correctly,

You are calling this method twice listaPreciosPapa();. One from onCreate() & one from the callback of swipe refresh listener.

And inside listaPreciosPapa, you are creating an instance of Tabla class where you are passing an instance of activity & TableLayout.

Inside the constructor of the Tabla class, you are storing activity instance, TableLayout instance, and creating a new instance of filas list.

Since Activity & TableLayout instance is same for both times when you initialize Table class.

The problem is the inclusion order in your database.c file.

You first include database.h which declares the p_register function:

You shouldn't leave setOrigensFilter in the app function like this, try wrapping it inside its own function like so:

Your code has a logic that's serving another purpose.

This is just for learning purposes as mentioned in the comments, you'd solve this with a function or another method.

Also some suggestions:

• Name your procedure and variables to something meaningful
• Indent your code (you may use Rubberduckvba.com)
• Split the logic in steps

Read the code's comments and step into it using F8 key

Code:

The problem is that things like sym *OR = {TERM,"v",2}; isn't valid C, it's just gibberish. You can't initialize a struct pointer with a struct initializer list. It needs to point at an actual object. So just drop the * pointer declaration, why do you need these to be pointers for?

This is why beginners should always compile with a conforming standard C compiler. I recommend using

gcc -std=c11 -pedantic-errors -Wall -Wextra

which would have pointed out the bug for you (unlike default gcc which accepts lots of invalid code). It's much easier to resolve compile-time errors than run-time seg faults.