Shortcut casting causes errors

[marcsous]

It looks like the strClass way of casting added here causes problems if the scaling factor is not 1. The order of the operations is scale then cast with the MappedTensor, even if they were applied in a different order, which creates inconsistencies.

Example:

>> a=MappedTensor(1);
>> a(1)=1.5;
>> a=2*uint8(a);
>> a(1)
ans =
    3
>> a=1.5;
>> a=2*uint8(a);
>> a(1)
ans =
    4

I really like the shortcut way of doing things but it would need to track the order of the operations if there are more than 1 of them, as discussed a little bit here.

Probably best to revert this change in the meantime - sorry for the lack of insight when requesting it!

[DylanMuir]

Fixed. :)