topic Re: Post Mods in Fusion Manufacture Forum

Post Mods

ktorokU233T — Sun, 30 Jan 2022 22:13:11 GMT

Working on trying to bring some updates to my post. Found the new documentation for the scope member of the property table as well as the property groups definition.

Tried adding a scope to one of my property definitions in the property table to be able to use it per operation:

Also set the member property enabled to "milling" in hopes this would only be seen on milling operations. In actual usage, this appears to show up in milling AND drilling operation dialogues under the post tab

Is this intended behavior or am I missing something? There is also a "drilling" value for the enabled member, which does limit the addition of the property to a drilling operation. So does this mean a drilling operation is a milling operation, but a milling operation is not a drilling operation as far as the property table is concerned?

Re: Post Mods

KrupalVala — Mon, 31 Jan 2022 07:15:39 GMT

Hi @ktorokU233T ,

At the moment, “drilling”, is also a part of “milling” due to that you will get the operation dialog in both.

thanks,

Re: Post Mods

ktorokU233T — Mon, 31 Jan 2022 10:00:45 GMT

Thank You @KrupalVala

Is this the way this behavior is expected to remain, or will it be changed in the future to limit drilling to only drilling operations instead of including all milling operations also?

Another "quirk" I noticed was the difference in the way the choices of the values for the property are presented. I presently have it set as "integer" for property type, with an array for the acceptable values.

In the operation dialogue tab, the values are presented in a textbox input with increase/decrease buttons and no input limiting or checking:

In the post process screen, the input is presented as a drop down with the choices limited to the range selection as set in the "ranges" member of the property table:

I have not tried a "type" of enum as of yet, but will this present both options as a drop down selection in both the operations and post dialogs? enum would work for selections with limited choices, but would get cumbersome for an option with a limit set to a wider range.

I am happy to see these capabilities added to the post processing end and am looking forward to seeing how they integrate into the user experience.

Re: Post Mods

KrupalVala — Mon, 31 Jan 2022 11:36:50 GMT

Hi @ktorokU233T ,

Yes, In the coming days you will get that capability.

Regarding the other question, The input type "type" play a major role in post properties. It is associated with other property object like value.

For example, You can check following Post Properties

sequenceNumberIncrement - integer
preloadTool - boolean
useSubroutines - enum

The enum input type defines this variable as having fixed choices associated with it. These choices are defined individually in the values property array. An enum input type should be defined using "string" values. Where an integer value when associated with an integer. For boolean values, it should be an array of 2 strings, with the first entry representing true and the second representing false.

Please refer following chapters from Post Processor Manual for more detail.

4.1.2 Property Table

4.1.3 Property Scopes

Thanks,

Re: Post Mods

ktorokU233T — Wed, 02 Feb 2022 10:10:24 GMT

Thank you @KrupalVala . For the milling/drilling distinction, it's nice to hear it will progress in the future.

With the variable types I was trying to understand why the presentation of the same variable is different in the post process tab of the operation dialog as compared to the nc post process window. With the integer type variable, in the operation dialog, it is presented as an increase/decrease type box to the user when limited with a values member:

The user is allowed to increase/decrease the integer value below and above the values limit at this point, with no indication of being out of range.

In the nc post process dialog, this same integer variable is presented as a drop down selection with the selections limited to a set of values matching the values member of the variable:

I guess my concern was more in the end user experience using these dialogs and the programming back end work involved in the post processor to further check these values. I mentioned the enum type variable as a comparison only because the presentation and handling of this variable type appears to be the same in both the operations dialog and the nc post window at the moment. The way I was using the integer variable type presents a different set of challenges and I was just trying to comprehend which direction I might want to take using this newly found (to me) capabilities.

I have read through the updated manual and keep checking the reference material on the post processor web pages. They are a wealth of information, and is how I ended up here at this post. Being able to "converse" with the actual developers and other users is priceless. Keep up the progression, it is well appreciated.

Re: Post Mods

KrupalVala — Thu, 03 Feb 2022 08:09:32 GMT

Hi @ktorokU233T ,

It looks like an UI issue.

We will look into that and fix it in priority basis.

Thanks,