sNCProgram.Toolpaths.Count returns zero
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- visualbasic
- Domain
- api
Research direction
Start by reproducing the Visual Basic example against the affected 2017 project and a newly created NC program, checking PMNCProgram.Toolpaths.Count with PowerMill API version 1.1.53. Compare the result with a project created in the 2021 PowerMill version; done means determining why contained toolpaths are not counted or documenting the version-specific limitation.
Written by the indexing model from the issue text.
Description
Hi Luke,
Hope you can help me with this. I've run below code and not sure why the toolpaths count I'm getting is 0. There are definitely toolpaths inside the NC program. Please note this is old 2017 dated project, which I want to modify and re-post. I have just checked there is no issue with a project created in 2021 version of PowerMill. I even created new NC program, added toolpaths to this freshly created NC program - same issue - Toolpath count=0
Please approach me and I can send you the whole affected project, for you to investigate this.
I've updated project to 1.1.53 in NuGet but still the same issue.
**_powerMILL = New PMAutomation(Autodesk.ProductInterface.InstanceReuse.UseExistingInstance)
Dim pSession As PMProject = powerMILL.ActiveProject
For Each sNCProgram As PMNCProgram In pSession.NCPrograms
If sNCProgram.IsActive Then
MsgBox("Toolpaths count =" & sNCProgram.Toolpaths.Count)
End If
Next_**


Hope you can help me with this.
Cheers
Arthur
- Dominant language
- C#
- Stars
- 52
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Autodesk/PowerShapeAndPowerMillAPI
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
All issues in Autodesk/PowerShapeAndPowerMillAPI
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·