TRIM / EXTEND Selection Issue

Kyudos — Fri, 24 Mar 2017 01:12:11 GMT

Until I have time to implement these functions properly for my custom entities, I'm trying to disable them.

I already have code to cancel the current command (for given commands) if my entities are selected. This only partially works for TRIM and EXTEND.

If my entities are in the PICKFIRST selection - my code cancels the command via documentLockModeChanged
If my entities are selected as the boundary entities (i.e. the trim-to or extend-to entities), my code cancels the command via endSSGet
If my entities are not selected and an ACAD entity is picked for the boundary, I don't get the chance to cancel.

It seems like I can prevent anything untoward by implementing subIntersectWith to return eNotImplemented, but I'm concerned that disabling those functions will have unforeseen effects.

Is subIntersectWith only used by TRIM and EXTEND, or will I be breaking something else by disabling it? It seems to break intersection snaps for instance...

Re: TRIM / EXTEND Selection Issue

Alexander.Rivilis — Fri, 24 Mar 2017 06:47:49 GMT

As far as I remember, if your custom entity is not AcDbCurve-derived class and not implemented extend() and getSplitCurves() and some others methods - then EXTEND and TRIM (also BREAK and OFFSET) can not work with your entity.

topic TRIM / EXTEND Selection Issue in ObjectARX Forum

TRIM / EXTEND Selection Issue

Re: TRIM / EXTEND Selection Issue