Properties per Operation

[firearmssubmoa]

I'm playing with properties per operation I cannot get it to display at all when I open up a drill dialog??

  testProperty1:{

    title      : "Test Property",

    description: "Some type of property",

    group      : "Options",

    type       : "boolean",

    value      : false,

    scope      : "operation",

    enabled    : "drilling"

  },

2.  Also, can you disable or enable a user property based on say a toolnumber inside the drill dialog?

[viacheslav.shapilov]

It should work:

To make it working, you need to have a machine assigned to the setup, and post with operation properties, assigned to this machine.

2. It is not possible to have an expression for enabling/disabling operation post property right now. But it sounds like a sensible improvement for future.

[firearmssubmoa · Accepted solution]

?
I would assume that a Boolean is a check box, why is it doing a drop down?

[viacheslav.shapilov]

It definitely should be a checkbox, like in my screenshot.

Could you please attach an example post and document, so we can investigate, what's wrong?

[firearmssubmoa]

Seems it didn't proliferate all the way through before compile. It is present now.

[firearmssubmoa]

An additional question, that relates directly.

Is there a way to add a group inside the dialog, all my test shows the same General Group header on top???  Can I add another inside the dialog?

It acts like it doesn't see the group value?

[firearmssubmoa]

An additional question, that relates directly.

Is there a way to add a group inside the dialog, all my test shows the same General Group header on top???  Can I add another inside the dialog?

It acts like it doesn't see the group value?

[viacheslav.shapilov]

Operation post properties do not support groups for now. And we did not have any plans to implement them.

Do you think, groups could be useful?

[rusty.bird]

Has anyone had any issues when using these when debugging them in VS Code.  I have a few Operation Properties defined in my milling post but when I try and output them to VS Code I get a checkbox from Fusion that it automatically removed them/changed there value because I am switching posts to output to VS Code.

Is there a way to turn them back on in VS Code for a SINGLE operation?