- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Operation Properties and VS Code issue
Has anyone had any issues when using these when debugging them in VS Code. I have a few different 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?
because of this I am getting different results when comparing regularly posting code with milling post and vs code debugging output.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I'm not sure, but you may be able to make a modified copy of the export to vs code post and add your custom properties to it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I have tryed this with no success. It still wants to change the value.
The Code I have is:
blkFormRotP: {
title : "BLK FORM ROTATION",
description: "BLK FORM ROTATION Tongle ",
group : "configuration",
type : "enum",
values : [
{title:"Off", id:"Off"},
{title:"On", id:"On"}
],
value: "Off", // THIS MUST STAY OFF TO AVOID ALTERING OTHER PROCEDURES
scope : "operation",
enabled : "contour2d"
}
I am using Fusion to turn this on a certain procedure in my program. In the post this has to stay off because I am posting multiple procedures and only want this to effect that one procedure NOT ALL. This use to work fine before that update that added this status change in.
Fusion