[comp.windows.open-look] XView: XVPM lies about TEXTSW_MEMORY_MAXIMUM?

warsaw@nlm.nih.gov (Barry A. Warsaw) (04/13/91)

Well after much hacking, I've been able to get text of more than 20000
bytes to insert into a TEXTSW.  The XVPM says that 20000 bytes is the
default maximum TEXTSW size, and inserting more characters than that
does indeed produce an error notice.  However, the XVPM also says that
I should be able to set the attribute TEXTSW_MEMORY_MAXIMUM either at
xv_create() time or just after a textsw_reset(). If I'm trying to put
20515 bytes into the TEXTSW, I would set this attribute to 25000, but
I still get the error notice, whether I set the attribute at create
time or after a textsw_reset.

Also, the error notice indicates that I could set the resource
Text.MaxDocumentSize to the maximum number of bytes for a TEXTSW, but
this also does not work.

Finally I went to the XView2 source code and searched around. I found
some indication that I could set TEXTSW_MEMORY_MAXIMUM to 0 and it
would put any size document into the TEXTSW. Well this only works if
you do it at xv_create time, but it *does* work.

Of course, this workaround is totally undocumented, and the documented
features don't work, so I'd have to assume this is a bug in XView2,
right?  Or have I missed something (perhaps not so) obvious?  Sun,
tell me "fixed in 3.0" (but only if you *really* mean it :-).

-Barry

NAME:  Barry A. Warsaw         INET: warsaw@nlm.nih.gov
TELE:  (301) 496-1936          UUCP: uunet!nlm.nih.gov!warsaw