Path: utzoo!utgpu!watmath!att!cbnewsh!wolf
From: wolf@cbnewsh.ATT.COM (thomas.wolf)
Newsgroups: comp.windows.x
Subject: Why don't my widgets work as expected?
Summary: More questions
Message-ID: <2925@cbnewsh.ATT.COM>
Date: 8 Aug 89 14:12:48 GMT
Organization: AT&T Bell Laboratories
Lines: 48


In a recent posting I mentioned a problem I seem to be having with
keyboard translations when exeuting Doug Young's simple "one-line
edit-field" example program.  For some reason, some of the letters I
typed weren't displayed in the text-field (when I pressed the letter 'b',
for instance, it caused the field-widget's caret to backspace.)  In addition,
I would get a warning message from the toolkit telling me that previous
translation manager actions were overridden - when the widget was realized
for the first time.

Some folks suggested that I look at the order in which Young's example did
the translation manager overrides.  I went one step further:  I took out all
translation manager calls....but to no avail.

I figured, hey, maybe its the 386's implementation of the HP widget set that
is to blame, but found that to be unlikely as I just had the same problem
with an OpenLook program:

main(argc, argv)
	int argc;
	char **argv;
	{
	Widget toplevel, fieldwidget;

	toplevel = OlInitialize("top", "Top", NULL, 0, &argc, argv);

	/* TextField widgets are basically one-line edit widgets */
	fieldwidget = XtCreateManagedWidget("afield", textFieldWidgetClass,
		toplevel, NULL, 0);

	/* No call-backs, no translation manager overrides, no nothing */
	XtRealize(toplevel);
	XtMainLoop();
	}


This program (if I transcribed it correctly :-) compiles fine.  During
execution, it also exhibits the symptoms described above.

I am doing something stupid, I'm certain, but beats me what it is.  Can
someone help?

Any info would be appreciated,

Tom

P.S.  I did get rid of my .Xdefaults file - so I didn't "accidentally"
override key bindings by setting resources there.