You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I notice that in this line you are packing scalar values into an array.
But only for floats. Integers don't do this.
Is this a bug or is this expected behavior?
With the current behavior, I end up with interesting data results such as this attached image (after pulling into JavaScript). Note, the single integer is placed directly as a scalar, while the single float value is packed into a single element array.
I found that changing the float encoding line to: txt=D_(mat,varargin{:});
yielded what I expect to be correct results.
But I'm curious if there is some other design decision that this change would break?
The text was updated successfully, but these errors were encountered:
Last one (for now) 馃槈
I notice that in this line you are packing scalar values into an array.
But only for floats. Integers don't do this.
Is this a bug or is this expected behavior?
With the current behavior, I end up with interesting data results such as this attached image (after pulling into JavaScript). Note, the single integer is placed directly as a scalar, while the single float value is packed into a single element array.
I found that changing the float encoding line to:
txt=D_(mat,varargin{:});
yielded what I expect to be correct results.
But I'm curious if there is some other design decision that this change would break?
The text was updated successfully, but these errors were encountered: