mana | IncludeOS C Web Application Framework

Custom constructor is not properly initialized. When call Monster vampire = new Monster("Vampire", 2000, 300, 25); no values are set, so obvious null:string and 0:numbers returns (java default initializers).

Adapt with:

The variable and the rendered Surface are not tied. The Surface does not magically change when you change the variable. You need to re-render the Surface when the variable changes:

You have to make also the connection so that it uses utf8

Assuming that you have uft8mb4

Design your classes and use super correctly, as discussed in further detail at Python's super() considered super!.

When you define a rule in a kv file using , that rule gets applied to every instance of that SomeClass that gets created after the kv file is loaded. If you have two different rules like , then the second set of properties from the second rule just get added to the first.

If you want different properties, you can create different classes and define different <> rules. Or, you can define a single rule that contains two instances of the original SomeClass.

In your case you can do something like:

Some how coin_name is twice as long as your other lists. Once you fix that you can do this:

strtok returns pointers into the input string.

If you store these pointers in your list and then read a new line into the same buffer, the data at the saved addresses may get overwritten with the text from the next line. As noted by Barmar in a comment, if getline calls realloc, the memory may even become invalid.

At the end of the processing, the buffer will contain text from the last line and possibly parts from longer lines and all saved pointers will either point into the same memory range or maybe to invalid memory which results in undefined behavior when you try to use the pointers as strings.

You have to create copies of the strings when/before storing them in the list, e.g. by using strdup (or malloc and strcpy).

Based on MDN docs, spread radius has the effect of growing or shrinking box shadows relative to the element's dimensions:

Positive values will cause the shadow to expand and grow bigger, negative values will cause the shadow to shrink.

Since you're using a spread radius of -4px, this means that the edges of the shadow will be inset 4px from the edges of the element. If your element has insufficient dimensions (i.e. width <8px or height <8px, as 4px * 2 = 8px), the box shadow will not show since it will have a dimension of <0px in either axes.

Here is a proof-of-concept example, using the same box-shadow properties (but I increased the y offset to make it more obvious). Notice that the box shadow will only be rendered at elements of width >=9px: