[email protected], Matrix3.multiplyVector3Array refers to removed function applyToVector3Array XD

[jaygarcia]

FYI, installed [email protected].

	Object.assign( Matrix3.prototype, {

		flattenToArrayOffset: function ( array, offset ) {

			console.warn( "THREE.Matrix3: .flattenToArrayOffset() has been deprecated. Use .toArray() instead." );
			return this.toArray( array, offset );

		},
		multiplyVector3: function ( vector ) {

			console.warn( 'THREE.Matrix3: .multiplyVector3() has been removed. Use vector.applyMatrix3( matrix ) instead.' );
			return vector.applyMatrix3( this );

		},
		multiplyVector3Array: function ( a ) {
                       /** SEE below! **/
			console.warn( 'THREE.Matrix3: .multiplyVector3Array() has been renamed. Use matrix.applyToVector3Array( array ) instead.' );
			return this.applyToVector3Array( a );

		},
		applyToBuffer: function( buffer, offset, length ) {

			console.warn( 'THREE.Matrix3: .applyToBuffer() has been removed. Use matrix.applyToBufferAttribute( attribute ) instead.' );
			return this.applyToBufferAttribute( buffer );

		},
		applyToVector3Array: function( array, offset, length ) {
                        /** Orly? **/
			console.error( 'THREE.Matrix3: .applyToVector3Array() has been removed.' );

		}

	} );

These deprecation warnings are great, but when they call a remove method, it feels a bit awkward. Like a dead end.

Was exploring and just found this. =)

[Mugen87]

This actually happened here #10367. I think i was not aware that other deprecated methods already referred to .applyToVector3Array().

Maybe we could rewrite methods like . multiplyVector3Array() to:

multiplyVector3Array: function ( a ) {

    console.error( 'THREE.Matrix3: .multiplyVector3Array() has been removed.'  );

},

[mrdoob]

Good catch! 😅

[mrdoob]

@Mugen87 that sounds good 👍