update for 9.0.1

and update install and build notes

Author: jcupitt

README.md

@@ -15,19 +15,77 @@ can watch pixels change as you adjust your equations.
 Because nip4 uses libvips as the image processing engine, it can handle very
 large images and only needs a little memory. It scales to fairly complex
 workflows: I've used it to develop systems with more than 10,000 cells,
-analyzing images of many tens of gigabytes. It has a batch mode, so you
-can run any image processing system you develop from the command-line and
-without a GUI.
+analyzing images of many tens of gigabytes.
+
+It has a batch mode, so you can run any image processing system you develop
+from the command-line and without a GUI.
 
 [![Screenshot](images/shot1.png)](images/shot1.png)
 
 [![Screenshot](images/shot2.png)](images/shot2.png)
 
 https://github.com/user-attachments/assets/6f7bdee1-183c-4554-9701-e0c30e75d58a
 
-## flatpak
+# Installing
+
+## Windows
+
+There's a zip for each version on the [releases
+page](https://github.com/jcupitt/nip4/releases). Download
+`vips-dev-w64-all-8.16.0-nip4.zip`, unzip somewhere, and run `bin/nip4.exe`.
+
+## macOS
+
+We hope to have a homebrew formula soon.
+
+## Linux-like systems with flatpak
+
+There's a PR to add nip4 to flathub here:
+
+https://github.com/flathub/flathub/pull/6166
+
+Once we get a stable release, nip4 will be added to flathub. You can install
+one of the test releases from that PR with eg.:
+
+```
+flatpak install --user \
+    https://dl.flathub.org/build-repo/165060/org.libvips.nip4.flatpakref
+```
+
+## From source
+
+Download the sources, then build and install with eg.:
+
+```
+cd nip4-x.y.x
+meson setup build --prefix /my/install/prefix
+cd build
+meson compile
+meson test
+meson install
+```
+
+Check the output of `meson setup` carefully.
+
+## From source for Windows
+
+Clone:
+
+https://github.com/libvips/build-win64-mxe
+
+Then see this PR:
+
+https://github.com/libvips/build-win64-mxe/pull/72
+
+Checkout that branch and build with eg.:
+
+```
+./build.sh --with-nip4 all
+```
+
+## Build from source for flathub
 
-Add the `flathub` repo:
+Add the `flathub` repo, if you don't already have it:
 
 ```shell
 flatpak remote-add --if-not-exists \

TODO

@@ -1,5 +1,3 @@
-- open test.ws, edit defs, "main = 12;", process, ws is not marked as modified
-
 - check all batch mode flags
 
 - try to save and restore image view scale and position
@@ -154,6 +152,9 @@
 
 	maybe do a separate pass at the end of recomp that sets label colours?
 
+	could use this to make parent/child colour change only show after a
+	while ... might look better
+
 - this fails:
 
 	im_insertset main sub x y
@@ -187,13 +188,6 @@
 
 - syntax error in startup .def stops nip4 loading
 
-- ctrl-bsp for delete selected rows?
-
-	we can't set accels on action menus, since the windiow won't know
-	what view to pass the action to, see mainwindow_view_action()
-
-	maybe action menus should be on the class, not the object?
-
 - should we support
 
 	A1.value + [1, 2, 3]

meson.build

@@ -1,6 +1,6 @@
 project('nip4', 'c',
   # ie. a major after nip2 8.9 for workspace save file versioning
-  version: '9.0.0-11',
+  version: '9.0.1',
   license: 'GPL',
   meson_version: '>=0.64',
   default_options: [

org.libvips.nip4.metainfo.xml

@@ -32,9 +32,10 @@ as you adjust your equations.
 Because nip4 uses libvips as the image processing engine it can handle very
 large images and only needs a little memory. It scales to fairly complex
 workflows: I've used it to develop systems with more than 10,000 cells,
-analyzing images of many tens of gigabytes. It has a batch mode, so you
-can run any image processing system you develop from the command-line and
-without a GUI.
+analyzing images of many tens of gigabytes.
+
+It has a batch mode, so you can run any image processing system you develop
+from the command-line and without a GUI.
 
     </p>
   </description>
@@ -50,13 +51,21 @@ without a GUI.
 
     <screenshot>
       <image>https://raw.githubusercontent.com/jcupitt/nip4/master/images/shot2.png</image>
-      <caption>Workspaces from older versions load correcty</caption>
+      <caption>Workspaces from older versions load correctly</caption>
     </screenshot>
 
   </screenshots>
 
   <releases>
 
+    <release version="9.0.1" date="2025-02-24">
+      <description>
+        <p>
+          First test release we distribute.
+        </p>
+      </description>
+    </release>
+
     <release version="9.0.0-11" date="2025-02-18">
       <description>
         <p>

src/workspacedefs.c

@@ -167,6 +167,8 @@ workspacedefs_clicked(GtkWidget *wid, Workspacedefs *workspacedefs)
 		text_view_get_text(GTK_TEXT_VIEW(workspacedefs->text));
 	if (!workspacedefs_set_text(workspacedefs, txt))
 		workspace_set_show_error(workspacedefs->ws, TRUE);
+	else
+		workspace_set_modified(workspacedefs->ws, TRUE);
 }
 
 static void