swick@ATHENA.MIT.EDU (Ralph R. Swick) (07/01/89)
**** NOTE to non-readers of the documentation **** If your application expects user input, then you had better set an appropriate value for the XtNinput resource per the ICCCM. For most applications, the appropriate value is True. There are more and more window managers coming on-line that will refuse to pass keyboard or mouse input to your application if you don't explicitly say you want it. This is documented (almost) in the Xt Intrinsics spec, in the ICCCM, and in the short "Converting Widgets from R2 to R3" paper. Note that the Xt spec has _always_ said that the default value was False (although it really wasn't in R2).
argv%eureka@Sun.COM (Dan Heller) (07/03/89)
In article swick@ATHENA.MIT.EDU (Ralph R. Swick) writes: > If your application expects user input, then you had better set > an appropriate value for the XtNinput resource per the ICCCM. > > For most applications, the appropriate value is True. > > Note that the Xt spec has _always_ said that the default value > was False . *soap box* Why?! You just said that for most applications, the value should be True. Yet the -default- value is false. I see no reasonable logic to that. Not only do you create rope, but you actually tie the knot and help the user up the tree. If nothing else, the intrinsics should make the default value True. The intrinsics could behave "intelligently", by checking to see if the widget contains a non-null translation table when it is realized and set the input hint to the window manager accordingly. > This is documented (almost) in the Xt Intrinsics spec, in the Almost? Doc, Shmoc. :-) This isn't a good bush to hide behind. I suppose now I have to go thru my entire toolkit and add yet more text: ... { XtNinput, XtN???, XtNBoolean, sizeof(Boolean), XtOffset(core.???), XtNImmediate, True }, ... (I'll have to look up what the values are for the ???'s) dan <island!argv@sun.com> ----- My postings reflect my opinion only -- When on the net, I speak for no company.