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-06 08:45:40 +02:00
committed by JacobStoren
parent 05ae735519
commit a7ba7c793c
5 changed files with 13 additions and 14 deletions

View File

@@ -176,7 +176,7 @@ DEFUN_DLD (riSetGridProperty, args, nargout,
// Check if we have a Requested TimeSteps
if (!(nargin > argIndices[4] && args(argIndices[4]).is_matrix_type()))
if (!(nargin > argIndices[4] && args(argIndices[4]).is_matrix_type() && !args(argIndices[4]).is_string()))
{
argIndices[4] = -1;
for (size_t aIdx = 5; aIdx < argIndices.size(); ++aIdx)