Error with Joint Push Pull

[i5963c]

Re: [Plugin][$] JointPushPull Interactive - v4.8a - 30 Mar 24
I have the latest version of this plugin installed. I also have the required versions of LibFredo6 installed. I'm using Sketchup Make 2017.
On regular times, the plugin crashes. An example of the crash report is shown below:

***Date: 20-May-24 13:15:14 - SU2017.2
An error occurred in Joint Push Pull
Error in Analysis of model

wrong number arguments: 4 or 6 required

body_lib6g6.rbe: 3139 -- linear_combination
body_lib6g6.rbe: 3139 -- vector_exact_average
jointpushpullalgo.rbe: 1369 -- joint_compute_direction
jointpushpullalgo.rbe: 1315 -- block in block_prepare_vertices_J
jointpushpullalgo.rbe: 1315 -- each
jointpushpullalgo.rbe: 1315 -- block_prepare_vertices_J
jointpushpullalgo.rbe: 1200 -- block in block_prepare_vertices_all
jointpushpullalgo.rbe: 1200 -- each
jointpushpullalgo.rbe: 1200 -- block_prepare_vertices_all
jointpushpullalgo.rbe: 524 -- algo_prepare_calculation_exec
jointpushpullalgo.rbe: 504 -- algo_prepare_calculation
jointpushpulltool.rbe: 866 -- dragging_start
jointpushpulltool.rbe: 1574 -- onLButtonDown***

As I mentioned, this doesn't occur all the time. However, one process to trigger the error is as follows;

• Start Sketchup with a new file.
• Draw a circle in the origin
• Convert this circle into a cylinder with the standard Sketchup Push/Pull tool.
• Convert the cylinder into a group
• Activate the Joint-Push-Pull methods and try to increase the volume of the cylinder.....
• The error window pops-up...

From time to time, after doing some other actions, the joint push pull starts working again (even with the same cylinder!)
PS1: I also tried to downgrade to an earlier plugin version that I still had available on my system (4.6a). The same issue happens with that version.
PS2: The error happens on my 2 PC's where Sketchup is installed (Windows 10 and Windows 11).

Thanks to verify what' going on. Hopefully a fix can be provided.
In case more information would be required, please don't hesitate to ask.

[fredo6]

@i5963c

Thanks for signaling the problem, which is due to a side effect of a fix for FredoCorner introduced by LiFredo6 v14.4c.

I fixed it in LibFredo6 v14.4d, just published.

[i5963c]

@fredo6
Thanks a lot for the fast reply and solution.
Just installed the update and tested it. It works!
Up and running again.