vpp | Video++ , a C++14 high performance video and image | Computer Vision library

I think

I found by myself the solution. The grouping by a[4] works. I know that this code is pretty awful but i can't handle with templates for the moment. I can't do that. Although, if you have some improvements (they are many ones) to suggest, please let me now. I would like to use templates to split the code. Here is my code

You can use re module to parse the string (regex101):

You could proceed like this by collecting data by concatenation in an array:

Most XSD processors would have at least detected that the closing xsd:element tag just before PriceInformation,

The problem of random values observed on inputs are generally caused by floating inputs. An input is considered in floating state if it's not driven by an output or a some kind of source. In this case, a floating input behaves like an antenna, it can get any voltage level randomly and the logic connected to it switches between 1 & 0 randomly.

It seems most of the time, electronics and uC beginners learn about them for the first time when they experiment with buttons. My experience was similar. The input was triggering when I get my finger close to the button, but before I actually press or even touch it. Later, I observed that they can also be triggered by the changes of adjacent output pins of the uC.

Fortunately, the solution is simple. Just add a pull-up or pull-down resistor, so that the output is driven by VDD or GND even when the button is not pressed. Pull-ups seem to be more popular (I'm not sure why), so you generally connect the button in such a way that it pulls the input pin to the ground when the button is pressed and provide a pull-up resistor between the pin and VDD. In this case, your program logic reads the input as 0 when the button is pressed.

BTW, you could connect the pin directly to the VDD to prevent it from floating. But in this case, a button press would short circuit VDD to GND, collapse the VDD and reset the uC. This can also damage the power regulator (actually most of them have thermal shutdown to protect themselves), the button itself or the wires (or traces on the PCB). This is why you need a resistor.

Most uCs also provide internal weak pull-ups which can be activated by software. Here, weak means that these resistors have high values (like 100k ohms) and they don't pull the pin strongly. In cases where you need stronger ones (like pulling up communication lines) you may need to use external ones.

Some more recent uCs may provide internal weak pull-down resistors too. STM32 uCs have this capability. Your PIC12F1822 has only pull-up resistors, but fortunately they can be controlled individually. In some older PIC models, you have single switch to activate pull-ups on all pins of PORTB.

To activate internal weak pull-up on RA4:

try style = plot.style_linebr instead of style = line or

1. If you want to compare PP_display variable with an integer you should use == (equal to) operator. Single = is used to declare variables.
2. There is no end if in pinescript syntax.
3. You can't use plot function in the local scope, only in global.
4. Declaring a variable using the security() function in the local scope will produce a compilation error - Can't call 'security' inside: 'if', 'for'

The solution is to move all your calcs, security calls and plot function to the global scope.

If your intention is to hide the plot with the PP_display input you could use a ternary conditional operator ? : directly in the series argument of the plot function.

In your configuration is TX pin RC6 so switch: