SkSolve error

Comments

• Options

  MichaelPascoe Member Posts: 1,724 PRO

  November 2023

  
  @hervé_pipon this means that you have an operation in your code with a duplicate id. Each id must be unique. For example if you have opExtrude with an id of: id + "extrude1" 
  your next extrude would need a different id, something like: id + "mySecondExtrude"
  
  If you have an operation within a for loop, you can name the operation like this:
  id + i + "extrude"
  
  Also, if you share a link to your document, we can help troubleshoot specific issues you may have.
  
  

  
  Learn more about the Gospel of Christ  ( Here )
  
  CADSharp  -  We make custom features and integrated Onshape apps!   cadsharp.com/featurescripts 💎
  

  0
• Options

  kevin_o_toole_1 Onshape Employees, Developers, HDM Posts: 565

  November 2023 edited November 2023

  An example of this error and how to fix it can be seen in the documentation for the Id type:
  

  The full id hierarchy must reflect creation history. That is, each Id (including parents) must refer to a contiguous region of operations on the context.
  Thus, the following code will fail because id + "extrude" alone refers to two non-contiguous regions of history:
  

  for (var i in [1, 2])
  {
      opExtrude(context, id + "extrude" + i, {...}); // Fails on second iteration.
      opChamfer(context, id + "chamfer" + i, {...});
  }

  
  For the above code, a pattern like id + i + "extrude" or id + ("loop" ~ i) + "extrude" would work as expected, as would the unnested id + ("extrude" ~ i).

  2
• Options

  hervé_pipon Member Posts: 60 ✭✭

  November 2023

  @MichaelPascoe @kevin_o_toole_1
  Except for the plane name, all my Ids are unique and based on the for loop index. That's why I'm wondering.
  

  0
• Options

  kevin_o_toole_1 Onshape Employees, Developers, HDM Posts: 565

  November 2023

  Hi Hervé,
  
  If you take a careful look, that's also true of the of the failing example provided.
  
  This issue isn't duplicate ids. The issue is that the "+" operator is not a simple string concatenation, it is creating a parent id with children, and that FeatureScript requires each parent id to only be used in one contiguous region of history. This breaks because your code is starting one parent id ("sketch_"), then starting another ("1") and then reopening the original ("sketch_"). Take a look at the example above for several suggestions of different patterns of ids that will work without error.

  1
• Options

  hervé_pipon Member Posts: 60 ✭✭

  November 2023

  @kevin_o_toole_1very interesting indeed .
  But not very intuitive. I would love to find some video on FeatureScript explaining the philosophy and architecture of objects and tools.
  I think the documentation is not really user friendly.
  Fortunately there is the forum and people like you, who can put one's finger on the important detail.
  Thanks a lot.

  0