Cutout Tool AttributeError: 'NoneType' object has no attribute 'bounds'

[Vincenzo Dello Iacovo]

Hi, when I try to createa freeform Geometry in Cutout tool, hi have this error

Traceback (most recent call last):
File "D:\1.DEV\FlatCAM_beta\appTools\ToolCutOut.py", line 1422, in bounds_rec
TypeError: 'NoneType' object is not iterable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "D:\1.DEV\FlatCAM_beta\appObjects\AppObject.py", line 131, in new_object
File "D:\1.DEV\FlatCAM_beta\appTools\ToolCutOut.py", line 711, in geo_init
File "D:\1.DEV\FlatCAM_beta\appTools\ToolCutOut.py", line 1433, in recursive_bounds
File "D:\1.DEV\FlatCAM_beta\appTools\ToolCutOut.py", line 1431, in bounds_rec
AttributeError: 'NoneType' object has no attribute 'bounds'

I use 8.993 version on windows 10, attach my files.

[Vincenzo Dello Iacovo]

Also in linux version I have the same error

[Marius Stanciu]

Hello Vincenzo,

This issue was fixed some time ago, after the release of version 8.993.
The fix will be available in version 8.994.

[Vincenzo Dello Iacovo]

Great, thx

[Cliff Biffle]

Which branch would we pull from to get this fix? Beta doesn’t seem to include it, but I don’t see branches with more recent commits than Beta. (This has rendered FlatCAM not-useful for me because I can’t cut my board out, so I’m happy to test an unstable commit.)

[Marius Stanciu]

There is no branch with the latest changes available right now, at least not in the FlatCAM repository.
My actual work is done in a private repository and when I think things are rather stable I push the working branch in the Beta branch of the FlatCAM repository.

I use a private repository due of personal preference (I don’t like people looking over my shoulder). Sorry for that, but that is the situation.
I expect to have a new release at the end of September, start of October.

Best,
Marius

‌

[Cliff Biffle]

I see. That sounds like it makes it hard for other people (e.g. me) to collaborate on improvements, is there a process for that?

[Marius Stanciu]

Hi Cliff,

For people that want to develop and therefore contribute, I can add them/you as a user to my private repository. For that I will need your email that is associated to your Bitbucket user.

Do you have anything in mind you want to work on? In any case I will start adding the issues I find to the Issues section.
Currently I just finished added almost everything that is required for autolevelling (including a mini GRBL GCode sender) all that is missing is the actual routine to process a GCode line and use the probing data to adjust the Cut Z. But we have someone that said he will work on it.
I also am trying to migrate all the Milling stuff out of the Geometry object to its own Tool: Milling Tool. But that’s a bit heavy as it needs to propagate all over the app.
I also saw some issues when plotting CNCJob objects when multiple tools are used. It needs debugging and see why the VisPy is protesting with warnings.
I just realized that some of the general parameters in Drilling Tool are not used in the GCode (perhaps NCC and Paint Tool too).

Best regards,
Marius

[Marius Stanciu]

Hi,

Can you check the latest version and see if we can close this issue? Let me know if FlatCAM beta 8.994 (just released) solves the issue.

[Vincenzo Dello Iacovo]

Great Marius, is all ok now! Many thanks for new release.

Il giorno sab 7 nov 2020 alle ore 16:52 Marius Stanciu <

[Marius Stanciu]

Solved in v 8.994