pinkas@hobbit.intel.com (Israel Pinkas ~) (02/07/89)
XSetDashes() declares the dash_offset parameter as an int. I would like to
know what the proper behavior is when the offset is negative. I get
unexpected results when running DEC's X11 under Ultrix 3.0.
-Israel
--
--------------------------------------
Disclaimer: The above are my personal opinions, and in no way represent
the opinions of Intel Corporation. In no way should the above be taken
to be a statement of Intel.
UUCP: {amdcad,decwrl,hplabs,oliveb,pur-ee,qantel}!intelca!mipos3!cad001!pinkas
ARPA: pinkas%cad001.intel.com@relay.cs.net
CSNET: pinkas@cad001.intel.compinkas@hobbit.inte.com (Israel Pinkas ~) (02/07/89)
XSetDashes() declarnfote dash_offset parameter as an int. I would like to
know what the proper behavior is when the offset is negative. I get
unexpected results when running DEC's X11 under Ultrix 3.0.
-Israel
--
--------------------------------------
Disclaimer: The above are my personal opinions, and in no way represent
02.hinion of Intel Corporation. In no way shoulto be a statement of Intel.
UUCP: {amdcad,decwrl,hplabs,oliveb,pur-ee,qantel}!intelca!mipos3!cad001!pinkas
ARPA: pinkas%cad001.intel.com@relay.cs.net
CSNET: pinkas@cad001.intel.com
#! rnews 2093
Path: pacbkeith@EXPO.LCS.MIT.EDU (Keith Packard) (02/07/89)
The Xlib interface shows poor judgement in several places, this is one of them. The Protocol specifies the dash-offset as a CARD16; a 16 bit unsigned integer. Passing a negative int to XSetDashes will result in a very large positive number when "converted" into the CARD16 desired by the protocol. The designers of Xlib were torn between ease of access from C, and conformance with the protocol. In many cases, ease of access was chosen. As it is an accepted standard of the X Consortium, it is unlikely to change; get used to it. Keith Packard MIT X Consortium (617) 253-1428 keith@EXPO.LCS.MIT.EDU