Hi guys,
I am trying to filter Text Entities using Content Filter with “ObjectType” as the filtering criteria.
Is this a bug or am I doing something wrong?
FilterTextEntity.3dm (154.5 KB)
FilterTextEntity.gh (9.4 KB)
2 Likes
Thanks for replying. Just to clarify, I already know how to handle this with MatchText. I was mostly curious whether Filter Content can do it, since I wasn’t sure if I was using it incorrectly or if it’s just a bug.
Can’t help with R8 features. Why complicate it 
This is not about making it complicated. I am simply trying to confirm whether this is a bug so it can be fixed.
Depending on a bug fix that could take years is unwise, in my experience.
Hope it’s a misunderstanding rather than a bug.
I am not depending on a bug fix. I already have a working solution. I am simply trying to understand whether this is expected behavior or an actual issue.
These are the object types in Rhinosciptsyntax:
3 Likes
Hey @martinsiegrist, thanks for this—however, I went there and didn’t know what to make of it. I’m not good with these R8 querying/filter components. Pardon my ignorance, can the content shown by @howtograsshopper be filtered through a text object type?
(nothing personal @martinsiegrist)
So what’s the answer to @howtograsshopper’s original question about filtering?
In part. this illustrates why I haven’t bothered with R8. (along with all the bugs!)
Who comes up with this unintuitive junk?
1 Like
Joseph, these are bit flags…
The answer is you cannot filter for the word ‘text’ because ‘text’ is not an object type.
As @dfytz1 mentioned, the correct object type is ‘Annotation’
The other option is to insert all parameters on the Query Model Objects component and get rid of the ones which aren’t needed.
2 Likes
I recognize that pattern from decades of experience as a programmer. But what has that got to do with the intended audience for GH? Answer: ABSOLUTELY NOTHING!!!
The world is painful enough already. I will use R7 as long as possible to avoid this nonsense.
1 Like
Rhinoscriptsyntax has been around for ages and no one forces you to reference geometry and bake / cache model objects efficiently.
Also I don’t understand why you write that my explanation has nothing to do with the OP’s problem. The filter was wrong and I gave a reference to the source of the object types.
Thanks Martin, this makes more sense now. I know you’ve pioneered these components since they appeared.
This is none of my business, apologies—nonetheless, I didn’t interpret Joseph’s comments as such, I think he’s just making it clear and obvious (for me at least, though I get it more now with your clarifications) that these “beneficial” R8 model-content-referencing/filtering components are far from being intuitive or easy to figure out 
- but I differ in that I will still use R8 and 9.
Anyway, edited the title, please change to what fits best.
1 Like
I sort of agree, that the new components aren’t easy to comprehend at first, but when you got the concept and master it…holy cow! how much you can do with it.
1 Like
Mark as solved? 
How the Rhino tab components work in themselves isn’t too complicated to understand, but how they are meant to be sequenced isn’t always immediately evident. I can recommend this youtube playlist https://www.youtube.com/playlist?list=PLNHt2A_Ge-xAqbDy83N7ZOVPpoF8wXmUD where a Finnish guy is going through all the components of the Rhino tab. Good for beginners and quick reference.
2 Likes
I didn’t write that.
But the correct answer (“Annotation”) wasn’t obvious from this either:
67 videos
2 Likes
You’re right that isn’t obvious…
1 Like