I haven't looked into your code, but if "Export FBX" is your own operator you could set a global flag variable in the modal operator indicating that it started. In the calling procedure you could write a loop to wait that the modal operator resets the flag when it ends and then move the object back. It's just an idea, don't know if that works for you or if I understood the problem right.

As I wrote in the code example above: You can either use a poll parameter which returns itself a true/false state, you can create a function for that in the class of the property and call it with lambda or you can define an independent function outside of the property class and specify it's name only in the "poll"-parameter. This only want to have a bool decision back. If poll=True then it is enabled, otherwise not. So you need to compare the selection mode with the attribute you want to display and with the variable which checks if it is visible or not currently - same logic.

Seems that the poll function does only work for PointerProperties - sorry. https://docs.blender.org/api/current/bpy.props.html#bpy.props.FloatProperty (search for "poll" here) I only used it here so I only expected that the other props have this, too... :) You could do that using the "enabled" property of layout/row in the "draw" method, like so: def draw(self, context): layout = self.layout # define condition is_enabled = context.object is not None # example # Draw Property row = layout.row() row.enabled = is_enabled row.prop(context.scene, "my_float_property") I have asked Claude to generate a quick example and it returned this one (see attachment): Copy that into the script window in Blender and start it. It will create three selection mode icons in a new panel named "misc". Depending on which you select it shows all you have selected. It is independent of the selection mode of the 3D editor. So if you are in face mode and select one face of a cube, and in the panel in vertex mode it also shows that 4 vertices are selected. Not bad, Claude! Maybe of help for you? You could use that as template to only show the attributes of the object belonging to the same domain.

You should check if the module is installed (should be the case by default - but who knows). On my computer it's in: C:\Program Files\Blender Foundation\Blender 4.4\4.4\scripts\modules\bpy_extras And, like with bpy you should of course add "# type: ignore" behind the import. More than that is only the usual things: Don't use the "if...main" line, don't use any code other than register/unregister (only a direct call to "register()" if you want to start your addon without installing it which needs the toml file and the __init__.py"). And: You need to start VSCode with the folder where your file is in, not the file itself. Although VSCode would open it, the Blender VSCode addon is not able to use it in this case.

"# type: ignore" is a type comment which pylance is using to ignore a type problem in VSCode. If you use "import bpy" for example, VSCode has no idea what this is as VSCode works with your system's Python by default and Blender is using it's own. Your code runs always with the Python Blender uses, this the Blender addon in VSCode makes sure. You can of course change the Python interpreter if you click on the Python version in the lower right corner of VSCode and then give it the link to the Python which is in Blender. If you don't do that because you want to work with the system's Python usually, the "# type: ignore" tells pylance that you are sure everything is OK and it should ignore problems with the code line (doesn't matter which one). On that way, "import bpy" is not shown as an error. You would also need it for example in Blender property definitions as these are also something which only Blender understands but not Python.

Possible answer can be found here: https://blenderartists.org/t/difference-between-context-object-and-context-active-object/551563/7

Ah, thanks, now I found it. If you open the spreadsheet window then you can see the additional attributes per vertex and how they change. Only thing which doesn't work: If you select more than one vertex not using Shift-Click but by drawing a rectangle then none of the vertices is an active vertex. In that case, changing attribute values in the menu doesn't change values in the spreadsheet. I personally tend to go away from Python whereever Blender has own possibilities to create the same especially using Nodes. They are written in C++ and are extremely faster than Python and already tested a lot more. In the screenshot you can see a tool created with Geometry Nodes in about half an hour which does nearly the same as yours: The Blend file also contains your script so you can easily compare it. To create something like that you need to switch the Geometry Nodes editor from "Modifier" to "Tool" in the upper right corner in the dropdown. Only in this mode you have the "Selection" Node which is not available in the Modifier Mode. To get the tool saved, right click on the name (here "AttributeTool" and select "Mark s asset". That creates the blue "bookshelf" icon at the right of the name and an "F" is added to the name in the dropdown which means "Fake User" so it's not lost when you save the file. As this is now no modifier but a tool and an asset you get a new menu in the "Edit" mode as you can see in the second screenshot. If you select some vertices of the object and call it you get a tool menu at the bottom left side as you can see in the third screenshot. Here you can select the names of the attributes, you can change the float values independent or together with holding the mouse button and drag down for all three at once, you can set which of these values should change using the "change" bools, you can also change a bool value. In the spreadsheet you can view how it works. As it is a tool it doesn't "remember" which names you used last time so it will always display the default names. But you can change it to an existing column (attribute) name to reuse that.

@Orange Flip The "Tool" thing is since Blender 4.0, but mostly people do not know that. You can setup your own tools and (depending on the kind of tool) you can also create own modifiers which are then reusable. You can also import such tools into other blender files.