[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

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

2787.0. "progamming problem" by LDPBS2::SYSTEM () Fri May 18 1990 11:33

 Not sure if programming errors go here?
    
    
 I'm getting an error using the XCOPY planes command on an NCD monitor, but
the same program runs fine on my 3100 with a DEC monitor.  Both are 8 plane
monitors.  Anyone run into this?  It returns a 'bad para err' when running
    on the NCD monitor.   What are the gotcha's when moving DFECwindows
    applications to other monitors?

Thanks

T.R Title User Personal
Name Date Lines

2787.1 Only a couple legitimate errors here... DECWIN::FISHER Prune Juice: A Warrior's Drink! Fri May 18 1990 12:39 21

T.R	Title	User	Personal Name	Date	Lines
2787.1	Only a couple legitimate errors here...	DECWIN::FISHER	Prune Juice: A Warrior's Drink!	`Fri May 18 1990 12:39`	21
	When you say "monitor", most people in the workstation business think you mean "the thing with the picture tube", which has no relavence at all here. I am assuming that you are talking about the NCD X terminal. It could certainly be a bug in the NCD server, (or perhaps you have made a real error, and the bug is in our stuff). There is no "param" error in the X protocol. It should be either Value or Match. (Or perhaps the text translation in Xlib is strange, although I've never seen this one). In any case, the problems with copy plane are: Value: The bit-plane argument to CopyPlane must have exactly 1 bit set, and its value must be less than 2**<number of planes>. Match: The two drawables have to have the same screen (hard to imagine they would not on an NCD). Hmmm. I wonder if there is something funny about the way the NCD swaps the bits in bitplane (assuming that it has a different bit/byte ordering from us). Burns

When you say "monitor", most people in the workstation business think you mean
"the thing with the picture tube", which has no relavence at all here.  I am
assuming that you are talking about the NCD X terminal.

It could certainly be a bug in the NCD server, (or perhaps you have made a real
error, and the bug is in our stuff).  

There is no "param" error in the X protocol.  It should be either Value or
Match.  (Or perhaps the text translation in Xlib is strange, although I've never
seen this one).  In any case, the problems with copy plane are:

Value:  The bit-plane argument to CopyPlane must have exactly 1 bit set, and
  its value must be less than 2**<number of planes>.

Match:  The two drawables have to have the same screen (hard to imagine they
  would not on an NCD).

Hmmm.  I wonder if there is something funny about the way the NCD swaps the
bits in bitplane (assuming that it has a different bit/byte ordering from us).

Burns