matlab/bfGetPlane.m: avoid use of makeDataArray2D when Octave (ome/bio-formats-octave-docker#29) #4130
+14
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes ome/bio-formats-octave-docker#29
Octave does not autobox multi-dimensional arrays (Matlab does) so
makeDataArray2D
can't be used in Octave. this commit makes use ofmakeDataArray
to get a 1D array and then reshapes it. This commit partially reverts 3aa468e (see #3301) for Octave only. the data copy that that commit was meant to prevent is back but is limited to Octave.For reference, the issue of Octave not autoboxing ND Java arrays is Octave bug #58745 (the issue description references a function
java2mat
that in theory should make this conversion but that function never worked for me and newer Octave functions have marked it somewhat internal by renaming it__java2mat__
).