e42f- Editing connectors causes tackdown object to change from zig to E-stitch

More
8 months 2 weeks ago #1921 by Pascale R.
This is a strange one (using e4.2f)

I copied & pasted part of the design that is acting strangely:

The original 'grass' object was a 'pre-cut' applique object
(this was either a partial-applique object or one I used remove overlaps)
I broke it apart.
I duplicated the placement line (to give myself the option of having 1 design with both cut in place or precut fabric)
I selected the zigzag tackdown & attempted to remove the trim prior to cover stitch by changing value of connector setting.


When I did this, the tackdown changed from zigzag to E-stitch.



Using the Closest Join command didn't remove the trim.
Work-around was to physically move the start point of the cover stitch.

Is this normal or did I somehow corrupt the file?

I have attached the emb file & video.
Attachments:

Please Log in or Create an account to join the conversation.

More
8 months 2 weeks ago #1923 by Karla
Hi Pascale,

This is normal.

It has automatically change the tackdown stitch type to either e-stitch or run with special properties. It has worked like this since e4.0.

What about if editing the connector before breaking the applique object apart? Would that work as another workaround?

Thanks,
Karla

Please Log in or Create an account to join the conversation.

More
8 months 2 weeks ago #1925 by Pascale R.

Karla wrote: Hi Pascale,

This is normal.

It has automatically change the tackdown stitch type to either e-stitch or run with special properties. It has worked like this since e4.0.

What about if editing the connector before breaking the applique object apart? Would that work as another workaround?

Thanks,
Karla


Thanks Karla
I don't understand the reasoning behind it changing - that seems like an odd thing to do.
How does it determine whether to change the tackdown to either a e-stitch or run?

Unfortunately, I don't have the original file any longer to try your workaround. I'll have to try to remember that next time I run across a similar situation. Thanks!

Please Log in or Create an account to join the conversation.

Time to create page: 0.286 seconds
Powered by Kunena Forum