Operations within Component Pattern post with pattern, preview w/o pattern

[Cave_Master]

Hello,

I created a simple pattern component pattern to make 3 instances of one part.  I need to save code that has all three parts and just the front part.  The component pattern works fine so getting all three is no problem.   When I select the operations within the pattern and post them, they still post with the pattern.  

I have several workarounds but am wondering if this is a known bug or not.

This shows the 3 operations highlighted, previewed in F360 and previewed in the router control.  Note in F360 I have the operations highlighted, not the pattern.  Also the preview in F360 is correct, but when it writes the code it is actually patterning the operations.

[seth.madore]

This is a known "feature", and, since it was done with intent, it's not "actually" a bug. Undesired? Yup.

I do know that the team responsible for that decision is examining their options at how to improve this experience. Sorry for the inconvenience, but it does sound like you are aware of the workarounds needed. 

For anyone else reading this thread, the workaround is as follows:
Move the operations OUT of the Pattern folder, or change the settings in the Pattern folder to something that wouldn't trigger multiple instances.

[Cave_Master]

Thanks, Seth.   Yep the workaround I am using to just delete 2/3 of the code.    Interesting about the behavior with patterns.   I don't use many patterns on the CAM end but I remember that it used to work the opposite as it does now.  

The way I use the software, I would benefit from reverting to the old way where posting an operation within a pattern would post only that one instance of the operation, but know that I can workaround both in the software by duplicating or changing folder settings, and in post by deleting code.

[seth.madore]

Yep, it used to work in what many refer to as the "preferred" method. Select a Pattern, get everything. Select the individual toolpaths, get just those.

Why the change? In Process Stock caching. The way Patterns were being handled presented some significant issues to the dev team tasked with the In-Process Stock management. It was the better course (debatedly) to change Patterns behavior

[Cave_Master]

Interesting, OK.