[Octave-bug-tracker] [bug #64985] make 'windowstate' property do what it is supposed to do

[Nicholas Jankowski]

Follow-up Comment #5, bug #64985 (project octave):

ok. easy enough to update on a case by case basis then.  I was thinking adding
a note to the top of the generated properties pages would be worthwhile, but
I'm not as familiar with generating texi from the m file (linebreaks, escape
characters, etc).  What would be the right way to format/break the long line
in the sprintf here:



diff -r 189360f2a7e0 doc/interpreter/genpropdoc.m
--- a/doc/interpreter/genpropdoc.m      Mon Dec 04 22:04:52 2023 -0800
+++ b/doc/interpreter/genpropdoc.m      Tue Dec 05 11:48:20 2023 -0500
@@ -634,6 +634,9 @@
 \n\n__fcnmsg__";
         s.valid = valid_fcn;
 
+      case "windowstate"
+           s.doc = doc_unused;
+
       case "windowstyle"
         s.doc = "The window style of a figure.  One of the following
values:\n\
 @table @code\n\
@@ -2250,7 +2253,7 @@
   elseif (is_prop_subset)
     ## Do nothing
   else
-    str = sprintf ("%s\n\nProperties of @code{%s} objects
(@pxref{XREF%s,,%s}):",
+    str = sprintf ("%s\n\nProperties of @code{%s} objects
(@pxref{XREF%s,,%s}).  Note that properties marked as unused are accepted and
stored by Octave but have no effect on the object:",
                    str, objname, objname, objname);
   endif
   str = sprintf ("%s\n\n@table @asis", str);




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64985>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/