[Connect C++] tessellation representation for Text

danny zhu said:

One more question, what’s the difference between drop way and the override _ProcessAsFacets way? 

Drop's purpose is to create "simple" element(s) to represent a more complicated element according to the given drop options. Drop may do nothing if the drop options aren't appropriate/supported by the given element. After a successful drop, if what you really wanted was geometry, not elements, you'd still have to extract that geometry somehow...and you've already potentially lost information about the original element's geometry (i.e. a shape element can be dropped to 4 line elements and no longer represents an area).

IElementGraphicsProcessor is sent the element's geometric representation and includes some commonly needed geometry conversions (ex. output all surfaces and solids as a polyface). It doesn't create elements, and you get to choose whether to handle the higher level geometric primitives directly (TextString, ISolidPrimitive, etc.) or have them output as another geometry type (CurveVector, PolyfaceQuery, etc.).

FUN FACT: The code to drop a text element to region/curve elements is actually implemented using the same output as IElementGraphicsProcessor.

-B

danny zhu said:

One more question, what’s the difference between drop way and the override _ProcessAsFacets way? 

Drop's purpose is to create "simple" element(s) to represent a more complicated element according to the given drop options. Drop may do nothing if the drop options aren't appropriate/supported by the given element. After a successful drop, if what you really wanted was geometry, not elements, you'd still have to extract that geometry somehow...and you've already potentially lost information about the original element's geometry (i.e. a shape element can be dropped to 4 line elements and no longer represents an area).

IElementGraphicsProcessor is sent the element's geometric representation and includes some commonly needed geometry conversions (ex. output all surfaces and solids as a polyface). It doesn't create elements, and you get to choose whether to handle the higher level geometric primitives directly (TextString, ISolidPrimitive, etc.) or have them output as another geometry type (CurveVector, PolyfaceQuery, etc.).

FUN FACT: The code to drop a text element to region/curve elements is actually implemented using the same output as IElementGraphicsProcessor.

-B

Brien Bastings said:

FUN FACT

Please, more fun facts.

Jon Summers said:

Please, more fun facts.

Yes, I vote for the same: More facts that (from reasons I really don't understand) "are fun" for those weird persons called developers ;-)

Regards,

  Jan

Thank you Brien, That's really helpful for me to understand the internal behaviors.