docs: update README for v3.0, code comments

Author: BrendanParmer

docs/README.md

@@ -15,7 +15,7 @@ Blender's node-based editors are powerful, yet accessible tools, and I wanted to
 * interfacing with other parts of the software or properties of an object
 
 ## Supported Versions
-NodeToPython v2.2 is compatible with Blender 3.0 - 3.6 on Windows, macOS, and Linux. I generally try to update the add-on to handle new nodes around the beta release of each update.
+NodeToPython v3.0 is supported for Blender 3.0 - 4.0 on Windows, macOS, and Linux. I generally try to update the add-on to handle new nodes around the beta release of each update.
 
 ## Installation
 1. Download the `NodeToPython.zip` file from the [latest release](https://github.com/BrendanParmer/NodeToPython/releases)
@@ -35,33 +35,29 @@ Select the node group you want code for, and you'll be prompted with a **Script*
     * Doesn't include `import bpy` line
     * To keep NodeToPython cross-platform and independent of third-party libraries, to get it into your system clipboard you need to paste into the Blender text editor and recopy it currently
 * **Add-on** mode generates a zip file for you in the save directory specified in the NodeToPython menu. From here, you can install it like a regular add-on. The generated add-on comes complete with operator registration and creating a modifier/material for the node tree to be used in. 
-
-## Future
-### v3.x
-* Expansion to Compositing nodes
-* New Blender 4.0 nodes and changes
-
-### Later
-* Better asset handling
-* Auto-set handle movies and image sequences
-* Automatically format code to be PEP8 compliant
-* Automatically detect the minimum version of Blender needed to run the add-on
-
-## Potential Issues
-* As of version 2.2, the add-on will not set default values for
-    * Scripts
-    * IES files
-    * Filepaths
-    * UV maps
-* This add-on doesn't currently set default values in Geometry Nodes modifiers, just the node groups themselves
-* Currently when setting default values for the following, the add-on must be run in the same blend file as the node group was created in to set the default, otherwise it will just set it to `None`:
+    * The current default operator install location is in the Object menu
+
+## Future Plans
+* Investigate drivers and keyframes
+* A better default operator install location for generated add-ons
+* A development repository with useful scripts and tests
+* Better handling of more setting types, including
+    * Image sequences
+    * Movie clips
     * Materials
     * Objects
-    * Collections
     * Textures
-
-* In a future version, I plan on having the add-on adding all of the above to the Asset Library for reference
-* You may run into naming conflicts if your add-on shares a name with another Blender add-on or operator (see [#56](https://github.com/BrendanParmer/NodeToPython/issues/56))
+    * Text objects
+    * Scenes
+    * Particle systems
+    * Fonts
+    * Masks
+    * Cryptomatte entries
+    * Image format settings
+    * File slots
+    * Layer slots
+* Automatic detection of the minimum/maximum version of Blender compatible with a generated add-on
+* Autoformatting of generated code
 
 ## Bug Reports and Suggestions
 

utils.py

@@ -45,8 +45,8 @@ class ST(Enum):
     FONT = auto() #unimplemented
     MASK = auto() #unimplemented
     CRYPTOMATTE_ENTRIES = auto() #unimplemented
-    IMAGE_FORMAT_SETTINGS = auto()
-    FILE_SLOTS = auto()
+    IMAGE_FORMAT_SETTINGS = auto() #unimplemented
+    FILE_SLOTS = auto() #unimplemented
     LAYER_SLOTS = auto() #unimplemented
 
 class NTPNodeSetting(NamedTuple):