Messages

1

Scripts and Plugins / Re: MophMuse V 1.0.0.0 (Pre-release)

« on: November 02, 2025, 18:51:24 pm »

Yes, it is what I said on a previous post,     poly.Transform = Matrix4x4F.Identity; is not working if applied on a polyrectangle, you must first convert it to a polyline then apply transformation on the resulting polyline.

Aha, I see, now, what you pointed out, David.

But applying ConvertToPolylines(bool x) to polyrectangles does all the magic—If I'm not mistaken regardless of whether the argument is true or false. So we don't need to explicitly apply the transformations.

Excellent week!

2

Scripts and Plugins / Re: MophMuse V 1.0.0.0 (Pre-release)

« on: October 28, 2025, 00:30:56 am »

Hello!

Eddy, the issue that's occurring is that when selecting rotated polyrectangles, the plugin completely ignores the rotation — it seems to be a particular behavior of polyrectangles.

From what I understood, you're both suggesting something like this:

Code: [Select]

if (poly.ApplyTransformation())
{
    poly.Transform = Matrix4x4F.Identity;
    poly.Update();
}


I tried applying it to the code like this:

Code: [Select]

case Polyline poly:
    if (poly.ApplyTransformation())
    {
        poly.Transform = Matrix4x4F.Identity;
        poly.Update();
    }
    if (poly.Closed) closedPolys.Add(poly);
    else openPolys.Add(poly);
    break;

But it didn’t make any difference.

On the other hand, I was able to simplify the code I was using down to a single line:

Code: [Select]

poly = poly.ConvertToPolylines(true)[0];

So the code now looks like this:

Code: [Select]

case Polyline poly:
    poly = poly.ConvertToPolylines(true)[0];
    if (poly.Closed) closedPolys.Add(poly);
    else openPolys.Add(poly);
    break;

Could this have any unintended side effects?

very nice work !!

It's been very rewarding — the methods used aren't sophisticated, but the result is quite reasonable.

Have a great week!

3

Scripts and Plugins / Re: MophMuse V 1.0.0.0 (Pre-release)

« on: October 23, 2025, 23:02:36 pm »

I have tried out v1.3.87, and it is almost there. The closed shape can be polyline, polyrectangle or circle, but a closed spline does not seem to work.  The open spline works as the shape to be swept around the closed shape.  An arc also works

It was just another bug, I think it's resolved now. Thanks for testing and for your patience.

For  the rotated rectangle, you must convert it to polyline first, then "apply transformations" on the polyline to reset the transformation matrix.

When the same issue occurred with the other plugin, it was resolved using the following code snippet:

Code: [Select]

                        if (poly.CanConvertToPolylines == true)
                            poly = poly.ConvertToPolylines(true)[0];

I even tried applying transformations, but just like last time, without success.

Big thanks!!

4

Scripts and Plugins / Re: MophMuse V 1.0.0.0 (Pre-release)

« on: October 21, 2025, 04:10:56 am »

Hi Geoff,

1) I believe this issue occurred in earlier versions of the plugin. I removed the form, but there was still a message box for cases where no valid selections were made. That’s been removed.
2) Adjusted the versioning. Hopefully it worked.
3) Implemented an internal conversion and tested it with circle, rectangle, arc, line, polyline, and spline. It worked, but rotating the rectangle breaks the algorithm. I’ve run into this issue before, and as far as I remember, the fix is simple — I just need to look it up in my files. But I’ll leave that for later.

Thanks a lot for the great feedback!

5

Scripts and Plugins / Re: MophMuse V 1.0.0.0 (Pre-release)

« on: October 19, 2025, 23:50:30 pm »

Hi!

-Customized CreatePointListFromPolyline().
-Adopted the use of the STEP resolution configuration item (David's idea). 

Code: [Select]

// C#
double stepResolution = CamBamConfig.Defaults.STEPResolution;

-Plus some additional internal improvements.

6

Bug Reports / Re: NumMove Plugin V 1.2.0.62 Bug with CB1.0 and Win11 Pro

« on: October 16, 2025, 01:00:13 am »

Yep, I don't know why, but the fact to use a "key filter" for the text box entries kill the ability to use the CTRL V/C .. I never find how to solve this problem.

It is the reversed of what happens in CamBam text editor (text object and GCode editor), no context menus but the CTRL C/V works ...

David,

This tip comes from my cyber friend — Microsoft Copilot 🤖 — who helps me understand a lot of things… though sometimes it slips up too 😅. Still, it's been a great companion for debugging quirky code behavior!


<Copilot>

You're absolutely right — using a "key filter" or intercepting keyboard events in a Visual Basic TextBox can unintentionally disable standard shortcuts like Ctrl+V or Ctrl+C.

This happens because when you handle KeyDown, KeyPress, or PreviewKeyDown events, you might be overriding or suppressing the default behavior that Windows provides for those shortcuts.
To fix this, you can try the following:

✅ Allow Ctrl+V explicitly in your key filter
If you're using KeyDown, check for Ctrl+V and manually trigger the paste:

Code: [Select]

Private Sub TextBox1_KeyDown(sender As Object, e As KeyEventArgs) Handles TextBox1.KeyDown
    If e.Control AndAlso e.KeyCode = Keys.V Then
        TextBox1.Paste()
        e.Handled = True
    End If
End Sub
This ensures that Ctrl+V still works even if you're filtering other keys.
⚠️ Avoid blocking default behavior
If you're setting e.Handled = True or KeyCode = 0 for all keys, make sure you're not doing that for Ctrl+V or Ctrl+C unless you intend to block them.

</Copilot>

HTH

Ricardo

7

Scripts and Plugins / Re: MophMuse V 1.0.0.0 (Pre-release)

« on: October 07, 2025, 02:57:55 am »

Don't worry about it, David. Over the eleven years I've been occasionally following this forum, I've developed a good sense of how things work — and how they don't. The collaboration here is fantastic and ends up making up for the lack of documentation (that's what I was referring to).

8

Scripts and Plugins / Re: MophMuse V 1.0.0.0 (Pre-release)

« on: October 06, 2025, 03:53:43 am »

Hey, David

I don't know how the mesh is constructed,

Actually, the idea is quite simple—the hard part is all the apparatus needed to make it work.

but Andy falls on the same problem with the conversion of STEP data to mesh depending of both the units and the real size of the object, and He add a STEP resolution property in the options to allow to set the resolution suitable for the job you want to do. Maybe you can use this setting as a way to define a suitable resolution for your mesh, so the user can define what is suitable for is usage ?

I think this problem is actually simpler than the one Andy faced, because we're in the opposite situation—working with well-defined curves and corners. The vertex must be placed exactly at the corner, and nowhere else.

CamBam.CamBamConfig.STEPresolution (double)

I use STEP resolution = 0.05 for mm.

That sounds like a great solution to the problem. I'm working on automating all of this, but it might turn out to be more complex than expected—and yet users might still want to make manual adjustments.

PS: STEP resolution is missing in the configuration page of the english doc. It is only described in "what's new - Revision rc-1 changes - 2019-09-11 - [10] STEP File mesh resolution setting"

A valuable bit of info that was tucked away in a corner is now finally out in the open—on the forum!

I'm publishing the code on GitHub, but the directory and the code there are a mess, and everything might change drastically at any moment: https://github.com/rymaeda/MorphMuse

Cheers to a new week—let’s make it a good one!

9

Scripts and Plugins / Re: MophMuse V 1.0.0.0 (Pre-release)

« on: October 03, 2025, 02:18:17 am »

Hi!

Here's a quick workaround for the resolution issue. Since the resolution is calculated from the diagonal of the bounding box of the closed polyline, there are still some cases where it can be problematic. I think a custom method to generate points along the curve could help fix that. I was a bit hesitant to share this, but coming up with a solid solution might take some time.

Thanks again for your time and the awesome examples!

I'll delete the older versions and keep just the two most recent ones.

Regards!

10

Scripts and Plugins / Re: MophMuse V 1.0.0.0 (Pre-release)

« on: October 01, 2025, 04:40:50 am »

Bug fixes, measurement unit handling, and a new user manual. The x86 version was not tested—sorry for the inconvenience.

Edit: Removed outdated files.

11

Scripts and Plugins / Re: MophMuse V 1.0.0.0 (Pre-release)

« on: September 25, 2025, 03:11:25 am »

Ralf and David, thank you for the feedback and encouragement. I've already run into a problem — I tested everything during development using a polyline provided in another conversation by Bubba, but it turns out the dimensions were in inches. Today I tried with a file in millimeters, and the result was an absurdly refined, heavy surface. The internal parameters, tuned for inches, created an impractically large file. I'll fix this soon, but not today — time to sleep. Thanks to both of you.

PS: Thanks a lot for the polyline, Bubba!

12

Scripts and Plugins / MophMuse V 1.0.0.0 (Pre-release)

« on: September 24, 2025, 00:03:09 am »

MorphMuse lets you build surface geometries in CamBam by combining one open curve with one closed outline. It automatically  generates a smooth surfaces"
Just for Cambam V1...

Edit: Removed outdated files.

13

Scripts and Plugins / Re: Streamlines plugin V 0.01

« on: August 28, 2025, 01:02:11 am »

Hello,

Thanks   tested on V1.0 32 bits and works OK ...

Fine tks!

but is there a way to define the resolution of the streamlines ? they are very "angular" close to the objects.

Let's dig into it. There is one refinement process and on the other side one simplification process

plugin webpage updated.

Thanks!

14

Scripts and Plugins / Re: Streamlines plugin V 0.01

« on: August 28, 2025, 00:53:53 am »

I've been following this thread and plug-in development, and I have a question.  What is the purpose? 

I'm not asking to be sarcastic or cheeky.  Is it a cosmetic thing?  Does it solve a problem? What is the use case? 

As in post one (1) "it was made to some learn and for fun" does it serve no other purpose than as a learning exercise?

To be honest, I was precise with that phrase. But of course, I believe it could be useful in some CamBam users' toolbox—for creating signs, for example, for a seafood restaurant or a fishing bait company. 😉

On a more serious note, I believe it could be applied in the design of fluid dynamic devices to reduce pressure losses. It might even be useful for academic research—not through CamBam, of course, but the method's source code is attached somewhere around here.

Looking back, on the personal front, I was locked inside during the height of the COVID-19 quarantine—just four months into marriage, with two feisty stepdaughters and a newborn baby girl, and no access to my shop toys... what a time to be alive!

15

Scripts and Plugins / Re: Streamlines plugin V 0.01

« on: August 26, 2025, 00:51:09 am »

Hello

Hi!

Thanks for this update

It's a honor

seems it is not working on the 32 bits version of CamBam (assembly compiled for another CPU) .. not tested on 64 bits version.

Sorry about that, my x64 version install uninstalled the x86 version... so I forget it. And the plugin had problems with 'AnyCPU'.

so there's no version available for CamBam 0.98 just for 1.0

not really a problem

That's great to know!