C#•4y ago

ReferenceEquals?

Am I missing something obvious?

ReferenceEquals(text.textInfo.meshInfo[0].mesh, text.mesh) // true
ReferenceEquals(text.textInfo.meshInfo[0].mesh.vertices, text.mesh.vertices) // false

ReferenceEquals(text.textInfo.meshInfo[0].mesh, text.mesh) // true
ReferenceEquals(text.textInfo.meshInfo[0].mesh.vertices, text.mesh.vertices) // false

ReferenceEquals(text.textInfo.meshInfo[0].mesh, text.mesh) // true
ReferenceEquals(text.textInfo.meshInfo[0].mesh.vertices, text.mesh.vertices) // false

ReferenceEquals(text.textInfo.meshInfo[0].mesh, text.mesh) // true
ReferenceEquals(text.textInfo.meshInfo[0].mesh.vertices, text.mesh.vertices) // false

This is Unity, TMPro.
If

text.textInfo.meshInfo[0].mesh

text.textInfo.meshInfo[0].mesh

text.textInfo.meshInfo[0].mesh

text.textInfo.meshInfo[0].mesh and

text.mesh

text.mesh

text.mesh

text.mesh are pointing to the same instance - how come the vertices property of the same instance doesn't return

true

true

Cisien•10/1/22, 2:20 PM

Are those classes or structs

Cisien•10/1/22, 2:21 PM

If they are structs, your dealing with value types, which get copied

Cisien•10/1/22, 2:23 PM

Vectors are structs

The MistOP•10/1/22, 2:24 PM

It's an array of value types though

The MistOP•10/1/22, 2:24 PM

Aren't arrays reference types?

Cisien•10/1/22, 2:25 PM

Vertices is?

が

がんばるかも•10/1/22, 2:25 PM

If text.textInfo.meshInfo[0].mesh and text.mesh are pointing to the same instance

if meshmesh is a value type, those are not "pointing" to the same instance

が

がんばるかも•10/1/22, 2:25 PM

meshmesh is the value itself

が

がんばるかも•10/1/22, 2:26 PM

so reference equality for a value doesn't make sense

Cisien•10/1/22, 2:26 PM

Mesh returns true

が

がんばるかも•10/1/22, 2:26 PM

right

が

がんばるかも•10/1/22, 2:26 PM

vertices

が

がんばるかも•10/1/22, 2:26 PM

が

がんばるかも•10/1/22, 2:26 PM

but still

The MistOP•10/1/22, 2:27 PM

Unless I'm misinterpreting the result, looks like an array of structs, yeah

が

がんばるかも•10/1/22, 2:27 PM

が

がんばるかも•10/1/22, 2:28 PM

possible that verticesvertices is a property that happens to be returning a new instance of array everytime it's called?

Cisien•10/1/22, 2:28 PM

Your sure you are pointing at the same array?

Cisien•10/1/22, 2:30 PM

This wouldn’t be the first time ive seen unity do strange things

ががんばるかも possible that `vertices` is a property that happens to be returning a new instan...

The MistOP•10/1/22, 2:32 PM

Ah, yeah, it's a getter that returns a copy apparently, had to view the actual implementation to see that
Idk why the IDE didn't show the doctsring, and why it's nowhere in the docs (nowhere I could find anyway)

が

がんばるかも•10/1/22, 2:32 PM

yeahhhhh

が

がんばるかも•10/1/22, 2:32 PM

unity is funky

Cisien•10/1/22, 2:35 PM

UnityDoesWeirdShit++

The MistOP•10/1/22, 2:36 PM

Yeah, the TMPro documentation is honestly kinda useless

The MistOP•10/1/22, 2:37 PM

I'm still in the process of trying to figure out what the difference between text.textInfo.meshInfo[0].mesh.verticestext.textInfo.meshInfo[0].mesh.vertices, text.mesh.verticestext.mesh.vertices and text.textInfo.meshInfo[0].verticestext.textInfo.meshInfo[0].vertices is

The MistOP•10/1/22, 2:37 PM

The documentation for all of them is just this which is very helpful lol

The MistOP•10/1/22, 2:38 PM

One youtube video said this:

The MistOP•10/1/22, 2:39 PM

And I'm not really sure if that's true, if accessing the property always returns a copy - what's the point

The MistOP•10/1/22, 2:39 PM

Maybe one of these doesn't return a copy in some cases

The MistOP•10/1/22, 2:40 PM

Not according to the docstring though

The MistOP•10/1/22, 2:41 PM

text.textInfo.meshInfo[0].verticestext.textInfo.meshInfo[0].vertices this one is an actual array within the meshInfo struct

The MistOP•10/1/22, 2:43 PM

I'll place a few breakpoints to hopefully figure out what it's doing under the hood

The MistOP•10/1/22, 2:43 PM

In any case

The MistOP•10/1/22, 2:43 PM

That's another can of worms

So what's the procedure here once a post has been solved, do I close it or do I leave it as it is?

Cisien•10/1/22, 2:46 PM

you can /close or just leave it

ReferenceEquals?

Similar Threads

Similar Threads

Similar Threads