Octave Interface: Fixed wrong timestep array detection

The test to check whether an argument was a array of timestep indices
was not good enough. Text was also interpreted as a matrix.
Typechecking of the arguments is difficult due to the lack of
documentation of the octave API
This commit is contained in:
Jacob Støren
2013-10-07 11:47:09 +02:00
committed by JacobStoren
parent 05ae735519
commit a7ba7c793c
5 changed files with 13 additions and 14 deletions
+2 -2
View File
@@ -168,8 +168,8 @@ DEFUN_DLD (riGetActiveCellProperty, args, nargout,
}
// Check if we have a Requested TimeSteps
if (!(nargin > argIndices[2] && args(argIndices[2]).is_matrix_type()))
if (!(nargin > argIndices[2] && args(argIndices[2]).is_matrix_type() && !args(argIndices[2]).is_string()))
{
argIndices[2] = -1;
for (size_t aIdx = 3; aIdx < argIndices.size(); ++aIdx)