END misunderstood in MATALAB APP

Hi everyone

I have a matlab APP with a part like this:

if (dato1(end,6)==1)
                trigger =1;
end

The problem is that the environment automatically thinks that the "END" in dato(end,6) is the one terminating the IF structure. As a consequence, the next end is taken by another thing in the code. This also happens in a while cycle where a statement like:

vector = vector2(end,:)

and that END is taken as the end for the while cycle.

The same code in a script works correctly obviously. Is this an issue of the app?

Thanks

[dpb]

I see similar issue in AppDesigner R2019b -- use of the end keyword definitely seem to confuse the parser.

The workaround would seem to be to use size with the appropriate dimension argument value and/or a temporary variable to store the appropriate value.

Looks worthy of a bug report to me.

[Stefano Massardi]

Yes I indeed solved using dato(length(dato),1)

Answer 1

[Reshma Nerella]

Hi,

I understand that clicking on the 'if' is highlighting the wrong end.

This issue is fixed in R2020a Update2.