'FeaturePython' object has no attribute 'SquareGrid'

[mfraser]

After the recent update I'm now getting the above error when loading an existing model into FreeCAD.
Squeezebox.FCStd

[mfraser]

I've tried adding a line to Document.xml for SquareGrid, but then the file doesn't even load.

[mwganson]

Thanks for the report. I will fix it in an update. In the meantime, select the object in the tree, press ctrl+shift+p, and then paste this into the python console:

obj.addProperty("App::PropertyBool","SquareGrid","Honeycomb","Whether to make honeycomb grid or square grid").SquareGrid = False

[mfraser]

Fixed in version 0.2024.08.27.

I've also noticed that since this was created using the old macro released in 2022, it doesn't have a version number either so it isn't triggering these lines:

if not hasattr(fp,"Version") or fp.Version != __version__:
        FreeCAD.Console.PrintError(f"Version mismatch.  Version of Honeycomb.py is outdated.  New version is {__version__}.  You can delete Honeycomb.py from your macro folder, delete the newly created Honeycomb object, and re-run Honeycomb.FCMacro to recreate a new version.  Then save your file and restart FreeCAD to complete the update.\n")

[mwganson]

They should all have a version in the source, I think. Notice also the line says if not hasattr, so any older version without the Version property should trigger that code.

When 0.22 / 1.0 becomes the stable version I'll be able to transition all the macros over to .py files and it will no longer be necessary for the user to deal with this. In 0.21 and earlier versions the addon manager renamed all macros to get the .FCMacro extension, which doesn't work well at all with feature python objects.

[mfraser]

They should all have a version in the source, I think. Notice also the line says if not hasattr, so any older version without the Version property should trigger that code.

When 0.22 / 1.0 becomes the stable version I'll be able to transition all the macros over to .py files and it will no longer be necessary for the user to deal with this. In 0.21 and earlier versions the addon manager renamed all macros to get the .FCMacro extension, which doesn't work well at all with feature python objects.

I was previously using this version of honeycomb.py 
__version__ = "0.2022.02.14"
#Honeycomb macro -- creates a feature python parametric honeycomb object for Part Design workbench
#2021, by <TheMarkster> LGPL2.1 or later
import FreeCAD, FreeCADGui, Part
class Honeycomb:
    def __init__(self,obj):
        obj.addExtension("Part::AttachExtensionPython")
        obj.addProperty("App::PropertyFloat","Radius","Honeycomb","Circumradius of the hexagons").Radius = 1
        obj.addProperty("App::PropertyFloat","Separation","Honeycomb","Separation between hexagons").Separation = .5
        obj.addProperty("App::PropertyFloat","Length","Honeycomb","Length of grid").Length = 10
        obj.addProperty("App::PropertyFloat","Width","Honeycomb", "Width of grid").Width = 15
        obj.addProperty("App::PropertyFloat","Height","Honeycomb","Height of grid").Height = 3
        obj.addProperty("App::PropertyBool","EllipticalGrid","Honeycomb","If True, make an elliptical grid of minor diameter = Width, Major Diameter = Length").EllipticalGrid = True
        obj.addProperty("App::PropertyFloatConstraint","XAdjust","Honeycomb","Adjust hexagons in the X direction").XAdjust = (0,-10e4,10e4,.1)
        obj.addProperty("App::PropertyFloatConstraint","YAdjust","Honeycomb","Adjust hexagons in the Y direction").YAdjust = (0,-10e4,10e4,.1)
        obj.addProperty("App::PropertyFloat","BorderOffset","Honeycomb","Offset for border (0 = no border) -1 for inward offset").BorderOffset = 1
        obj.addProperty("App::PropertyFloatConstraint","BorderHeightOffset","Honeycomb","Height Offset for border (0 = same as Height)").BorderHeightOffset = (0.1,-10e4,10e4,.1)
        obj.addProperty("App::PropertyLink","Profile","Honeycomb","Profile, e.g. sketch, to use in place of hexagon, should have radius = 1, centered on origin")
        obj.addProperty("App::PropertyInteger","CountXAdjust","Honeycomb","default: 0 -- amount to add to number of hexagons on X axis")
        obj.addProperty("App::PropertyInteger","CountYAdjust","Honeycomb","default: 0 -- amount to add to number of hexagons on Y axis")
        obj.setEditorMode("Placement",0)
        obj.Proxy = self
        self.fpName = obj.Name

There is no version info showing in the file and I don't see a warning when I open it.

[mwganson]

That code is for checking for mismatches between the .FCMacro file version and the .py file version. In newer versions of the macro I have done away with the .FCMacro file altogether, which is now supported by the addon manager since 0.22. It is not intended for checking against the version used to create legacy objects.

FreeCAD requires the class definition for the feature python objects be available in order for these objects to function correctly- Otherwise they will be broken when the document is reopened -- the object will not respond to property changes and the icon will be a default part solid icon. This class information must be contained in a .py file because python does not recognize .FCMacro as a python extension and will not import classes from the .FCMacro files. In previous versions of the addon manager every macro was renamed on installing to get the .FCMacro extension, hence the requirement for version checking and for managing the .py file after installation.

If the legacy object still works, then I would not be concerned about its version information or lack thereof. If it fails to function properly I might be able to fix that with code revisions, otherwise it would be necessary to delete it and make it again with the new version. Ideally, macro updates should not break existing objects, but sometimes I make a mistake and break them, as I did previously.