| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
Does anybody know, or have a feel for, how much data can be used for
the prop_data parameter of the XChangeProperty procedure? Is there
a limit on this?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 698.1 | STAR::BRANDENBERG | Si vis pacem para bellum | Fri Apr 28 1989 12:07 | 10 | |
The data in a single XChangeProperty call must be less than the maximum
request size (and a bit less) or 16Kbytes for the VMS V1.0 server. But
with clever use of the 'mode' argument in the call, you could create
larger property values. It may be that Xlib already has the logic to
break a single XChangeProperty call into several ChangeProperty
requests (Jackie?).
m
| |||||
| 698.2 | wishlist | DECWIN::JACKIE | Jackie Ferguson | Mon May 01 1989 17:39 | 2 |
no it doesn't but it sounds like a good idea. | |||||