At pre.65, Entities hierarchy still can't have precise component search that wrapped by class type or namespace. For example: if you have BarComponent wrapped by Foo class type, when u search at Entities hierarchy it only show BarComponent instead of Foo.BarComponent. I hope next Entities release will fix issue since at inspector it's already able to show Foo.BarComponent
#[1.0.0-pre.65] Entities hierarchy still can't have more precise component search
meager grotto
tulip sable
@strong cloak plausible to me?
strong cloak
I thought we had fixed that. I'll follow-up tomorrow.
strong cloak
Ok, I was mistaken. This is currently not fixed and unclear when it will be. We'll have to see how much work it represents.
On a technical level, it's very different from displaying it in an inspector and for performance reasons, were not doing simple type name searches. We actually generate an entity query with that type. We'll look into a few possibilities like allowing fully qualified names when we detect name collisions or generate an Any query with all matching types.
strong cloak
All right, just wanted to come back with more information on this. I did some digging in my free time and we used to have a fix for it that got squashed once we changed the default from OR to AND with the c= token. Now that we have all=, any=, and none= tokens, you should be able to construct your query however you want. The only bug that we have is that we do not propose auto-complete options for fully qualified names. But here's what I managed to get with some typing in the latest version of Entities.
And the old fix was that when there were collisions, it would create an entry per colliding item, meaning that with the example above, searching for all=MyComponent requires an Entity to have all 3 flavours of MyComponent to show up.
I'm not really following the releases of the Entities package anymore so I don't know when 1.0.0-pre.65 came out and which version is releasing when, but the above screenshots work as of 1.0.0-pre.90 and probably work in any version released since February. If you have those filters, it should just work.
ripe ginkgo
oh is that why all= is broken and doesn't seem to work?
Hmm then again, I'm pretty sure I only have 1 component called FreeCamera in that post -edit- oh there's a monobehaviour in the core render pipeline package with the same name
strong cloak
If that MonoBehaviour does not have a matching component, that shouldn't be the issue. Strange...
strong cloak
But based on your linked thread, it seems to be your issue. I'll bring it up to UX to figure out an elegant solution for this problem.
meager grotto
I'm not really following the releases of the Entities package anymore so I don't...
🧐 Do u mean at next release I can search and filter the component wrapped by class type like Foo.BarComponent?
strong cloak
The syntax for nested types is + so in your case: Foo+BarComponent. I don't remember when that went in to be honest, you can try it now but if not definitely soon™.
meager grotto
The syntax for nested types is `+` so in your case: `Foo+BarComponent`. I don't ...
Alright thanks. As long as it's included in next final 1.0 release. 😆
meager grotto
@strong cloak Looks like 1.0.8 release dun have this yet. Will it available at next patch release?
strong cloak
What I described is definitely in now. What is not working for you?
meager grotto
What I described is definitely in now. What is not working for you?
Ya the feature is there but u will need to explicitly typing yourself. The hint is not working yet
