Verified Members
  • Content count

  • Joined

  • Last visited

Community Reputation

71 Excellent

1 Follower

About c++

  • Rank
    Advanced Member

Profile Information

  • Gender


  • Location

Recent Profile Visitors

691 profile views
  1. I need to go through the project and remove all the unused functions. Id say about 90% of the code has been rendered obsolete
  2. You can check out the latest project here : Github
  3. I spent about 15 hours working on the refactoring saturday, I made modifications to the logic so that the chook iterates through all the top and bottom surfaces sorting each on individually.
  4. It seems to me lock feedrates is what you want, It is the path of least resistance IMO.
  5. This is the results of which operations I validated as stable or safe to use : Circle Mill <- not approved this operation has some issues of unknown origin with user defaults and api generated operations (Mastercam 2018) //removed operation we will no longer use this, use pocket or contour ramp instead Helix Bore <- not approved this operation has some issues with user defaults and api generated operations (Mastercam 2018) //removed operation we will no longer use this, use pocket or contour ramp instead .Net Drilling <- yes this operation is approved, no issues .Net Contour (2d , oscillation) <- yes this operation is approved, no issues .Net Pocket <- yes this operation is approved, no issues Not sure what happened with the helix bore and circle mill, in my machine and some of my friends it was okay but for other people they would get giant circular toolpaths spawning for no reason, especially inside of nesting, this is a bug we have seen prior to our implementation of chooks so we know it is a bug in the operation helix bore and circle milling, if the operation is regenerated on my machine it is fine, anyway I reprogrammed all my chooks to only use pockets ,contours and simple drilling, this way there won't be any problems, my initial project written in vbscript actually did the same thing.
  6. c++


    To use the silhouette boundary function ; select the solid, then in the wireframe tab select silhouette boundary and press okay.
  7. In my user profile these functions work well, however on 2 other users there is some undefined behavior where toolpaths are being sometimes mangled, I will probably switch to using only pocket and contour toolpaths to deal with the former helix bore, circle mill toolpaths, the drilling doesn't seem to cause a problem, but I will most likely return to the c++ point based system for drilling.
  8. Thanks for the reply Roger!! I will continue to use the stl containers. So far I haven't had any instances of Mastercam crashing due to memory leaks so I would say they have been working well.
  9. mill operation defaults and operations files are stored in c:/users/public/documents/shared mcam2020/mill/ops Keep a copy elsewhere, then when your update happens just replace the files.
  10. If the contents are being stored on the heap, what I have read about the heap, slower performance, memory fragmentation, It seems like vectors are probably good for new programmers to manage memory, but we will need to evolve. I wonder what the implications are of storing a vector of c-arrays a specific size, maybe map would be better. I'ts not an issue, I am working on the NEthook Nesting Project, I need it to rewrite it in c++/cli since we are going to do math, I need to find a means to simulate different nesting scenarios(probably shuffling the priority and rotation of the part using Rand) to automatically deduce the "most" efficient Nesting Pattern. It will also need to deduce the material size "x and y" from the name of the parts and have an input for a user provided string to the directory containing the parts. That is a very good point, and I haven't heard about stl, but I am watching some videos about it now, thanks for all the help.
  11. I noticed CNC software uses different array types in their code, I was thinking its probably faster, but harder to manage.
  12. This is where I read that the memory is actually allocated on the heap. https://stackoverflow.com/questions/8036474/when-vectors-are-allocated-do-they-use-memory-on-the-heap-or-the-stack I tried using the smart pointer in a project I am converting, not sure If I am doing this right : System::String^ data = "data"; System::String^ nstlist = NETHookNesting::NestingConstants::NestListExampleFile; auto nestListFile = System::IO::Path::Combine(System::IO::Path::Combine(Mastercam::IO::SettingsManager::UserDirectory, data), nstlist ); auto nestingDefaultsFile = System::IO::Path::Combine(Mastercam::IO::SettingsManager::SharedDirectory, Mastercam::IO::SettingsManager::Metric ? NETHookNesting::NestingConstants::MetricNestingDefaultsFile : NETHookNesting::NestingConstants::EnglishNestingDefaultsFile); auto NestingFile = std::make_unique<Mastercam::Nesting::NestingFile>(nestingDefaultsFile); // Create an instance from nesting defaults and clear out any existing parts and sheets array<Mastercam::Nesting::NestingPart^>^NestingPartArray; array<Mastercam::Nesting::NestingSheet^>^SheetArray; NestingFile->SheetArray = SheetArray; NestingFile->PartArray = NestingPartArray;
  13. Thanks for the info.. I've been reading a lot about this, right now I write everything in c++/cli project using various c# and c++ libraries. I store the bulk of my data in vectors declared like int get_size() { std::vector<int> vector_of_ints; int randomnumber = 1000; for(auto i = 0; i < randomnumber; i++;) { vector_of_ints.push_back(i); } //do something with the vector return i; } I guess that technically stores the data on the heap then it gets deallocated when the function goes out of scope, If I am understanding correctly would a vector be a good place to use a smart pointer, or would you recommend an array?
  14. New users looking for help sometimes turn out to have legitimacy issues with their software licencing.
  15. Hi John, thank you for the response. I previously deleted the users .config file but not the workspace file, I was not under the impression that this file was potentially problematic, but I will definitely try.

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us