Updated FLTK binding article with more bugfix notes

1 files changed, 23 insertions, 0 deletions

diff --git a/project/templates/fltkada.xhtml b/project/templates/fltkada.xhtml
index 4a4a85f..51b808e 100644
--- a/project/templates/fltkada.xhtml
+++ b/project/templates/fltkada.xhtml
@@ -18,6 +18,29 @@
 Estimated status: 80% complete</p>
 
 
+<h5>16/12/2022</h5>
+
+<p>Another year, another lot of bugfixes. Well actually the timing is pure coincidence, but it
+sounds kinda nice when I put it that way.</p>
+
+<ul>
+  <li>The Get_Value functions for Float_Input and Integer_Input widgets now won't crash if the
+  widget contains an empty string.</li>
+  <li>Menu widgets have had their internals reworked to properly take into account the extra
+  Menu_Item generated by adding a submenu to the widget.</li>
+  <li>Popup and Pulldown subprograms in Menu widgets now return an Index value instead of a
+  reference to a Menu_Item. This allows them to return a "Not Found" value without using any
+  exceptions.</li>
+  <li>Key bindings in Text_Editor widgets now bind properly again.</li>
+  <li>Selection related subprograms for Text_Buffers now ensure that out mode parameters keep their
+  values in bounds.</li>
+</ul>
+
+<p>The most vexing thing about all this is that some of the above fixes were needed due to my own
+oversights, and some were needed due to FLTK changing in subtle ways in the few point releases it
+has had since I made this binding. And I cannot tell which is which.</p>
+
+
 <h5>9/11/2021</h5>
 
 <p>A few noteworthy bugfixes have been applied to the binding.</p>