waashk/20ng huggingface dataset:
Ralph Seguin (rps@arbortext.COM) wrote: : > My question is this:  Is there a means of determining what the state : > of CapsLock and/or NumLock is?  : Alright.  Ignore this.  I have delved a bit deeper (XKeyEvent) and : found what I was looking for.  : ev->state   has a bunch of masks to check against (LockMask is the one : for CapsLock).  Unfortunately, it appears that the NumLock mask varies : from server to server.  How does one tell what mask is numlock and : which are for Meta (Mod1Mask, Mod2Mask, Mod3Mask, Mod4Mask, Mod5Mask). : eg, SGI's vendor server has Mod2Mask being NumLock, whereas Solaris : 1.0.1 OpenWindows 3.0 has Mod3Mask for NumLock.  Is there an : unambiguous means of determining NumLock's mask at runtime for any : given server?  Sorry for the wasted bandwidth and my appalling ignorance.  You'll have to check the keysym(s) on each of the keys for each modifier. The one with NumLock in its mapping is the modifier you want. A bit ugly perhaps but I think its currently the only way to do this (and it does have some precedent as keysyms are  used to differentiate CapsLock from ShiftLock for the Lock modifier).  I don't know of an accepted strategy for handling ambiguous assignments either. (ie. what if NumLock is mapped for more then one modifier). I suppose first found is as good as any.  X doesn't handle locking modifiers that well.   Hope that helps,  Dave Lapp
How can I capture ButtonPress/ButtonRelease events in multiple clients? I want to know if the user is still at the display before locking the screen. I can get  KeyPress/KeyRelease and Pointer motion events, but if the user is pressing the mouse button in the same location (the mouse doesn't move) I can't capture the events.    The O'Reilly Xlib Programming Manual (vol. 1) says on page 252;    "Only one client can select button events on any one window at one time,      due to the grab that automatically takes place."    Any help would be appreciated.
On 19 Apr 1993 23:00:15 GMT, masc0442@ucsnews.sdsu.edu (Todd Greene) said:  > Is there an Xt call to give me my application context? > I am fixing up an X/Motif program, and am trying to use XtAppAddTimeOut, > whose first argument is the app_context.  What call can I use > to give me this value?  I believe it's XtVaAppInitialize or something like that.  --
In article <C6wLIJ.L5K@bailgate.gpsemi.com> wilkinson_m@roborough.gpsemi.com writes: >Hi All, >       This is the first time I've posted to the net, so I hope this is >going to the right people. >  I'm looking for software packages that run on an IBM PC clone that >allows me to display Openlook and motif windows on the PC.  >  The idea is to use the PC as a cheap X windows terminal for use by >process Engineers at work.   May I humbly suggest DESQview/X? (Of course, I'm biased...)  DESQview/X is a multitasker for DOS computers, that uses a standard X11R4 server as it's display mechanism. DOS applications and Microsoft Windows standard mode are converted on-the-fly to X-protocol, allowing you to display them, or any R4 compatable X-program from any machine on the net to display to the PC's local display (or to any other display on the net).  Free tools are available for devloping X-applications for the DVX platform; many X-programs have been ported between DVX and UNIX with little or no modifications. (Often, you only need to create a new makefile!)  If you're interested in more details, you can check out the usenet group comp.os.msdos.desqview, or just email me directly at support@qdeck.com, and I'd be happy to fill you in.
Can someone recommend an inexpensive 19" monochrome X station, that is not PC software emulation based? Please tell me manufacturer, model, price and any other significant specs. Thanks.
Hi, netters:  We have a problem with 'makedepend': it doesn't know how to correctly process #if clause in C preprocessor statements. It evaluates everything to true no matter what the conditionals are. For example, makedepend chokes on one of X11 include files (as distributed by Sun) - namely Xos.h:  #if     !defined(SUNOS41) || defined(__STDC__) #       include <string.h> #       define  index   strchr #       define  rindex  strrchr #else   /* BSD && !__STDC__ */ #       include <strings.h> #endif  /* !SUNOS41 || __STDC__ */  Here 'makedepend' evaluates both #if and corresponding #else statements to 'true' and tries to open the file <strings.h> which doesn't exist under Solaris2. We also have a lot of #if statements in some of our legacy code. We got and built 'makedepend' off the net - it didn't fix the problem.  In all fairness it should be noted that 'makdepend' man-page (Sun's distribution) mentions this problem:  BUGS      If you do not have  the  source  for  cpp,  the  Berkeley  C      preprocessor, then makedepend will be compiled in such a way      that all #if directives will evaluate to  "true"  regardless      of  their  actual  value.  This may cause the wrong #include      directives to be evaluated.  Makedepend should  simply  have      its own parser written for #if expressions.  Has anybody come up with some solution/fix to 'makdepend' other than WriteYourOwnParser... and willing to share it with us?  Since we often experience delays in our newsfeed - please reply  directly to my e-mail address -> I'll post a summary.
|> (2nd posting of the question that just doesn't seem to get answered) |>  |> Suppose you have an idle app with a realized and mapped Window that contains |> Xlib graphics.  A button widget, when pressed, will cause a new item |> to be drawn in the Window.  This action clearly should not call XCopyArea()  |> (or equiv) directly; instead, it should register the existence of the new |> item in a memory structure and let the same expose event handler that handles |> "regular" expose events (e.g. window manager-driven exposures) take care |> of rendering the new image.  Using an expose event handler is a "proper" way |> to do this because at the time the handler is called, the Xlib Window is |> guaranteed to be mapped. |>  |> The problem, of course, is that no expose event is generated if the window |> is already visible and mapped.  What we need to do is somehow "tickle" the |> Window so that the expose handler is hit with arguments that will enable |> it to render *just* the part of the window that contains the new item. |>  |> What is the best way to tickle a window to produce this behavior?  If I understand your problem correctly, you want to have a way to send exposures to your manager widget when your app-specific code draws xlib graphics on the window.  It sounds like you might want to send an exposure using XSendEvent and specifying a region. If you know the region you need to send the exposure, generally you have the bounding rectangle of the objects, you can use XCreateRegion to create a region, XUnionRectWithRegion to add the new object polygons to the region, and then either use the region to clip your GC for the redraw or use XRectInRegion to test which of your other objects need to be redrawn. Keeping in mind that the stacking order of overlapping objects affects how they look.  Hope it helps  --  Brian Dealy                |301-572-8267| It not knowing where it's at   dealy@kong.gsfc.nasa.gov   |            | that's important,it's knowing !uunet!dftsrv!kong!dealy   |            | where it's not at...  B.Dylan
In article <1993Apr22.162016.5923@telesoft.com>, trevor@telesoft.com (Trevor Bourget @ignite) writes: |> In <sdennis.735423404@aa.cad.slb.com> sdennis@osf.org writes: |>  |> >I posted this a while ago and didn't receive one reply, and now we |> >have another bug report on the same subject. Can anybody help me out? |>  |> The problem is that Motif uses XGrabKey to implement menu accelerators, |> and these grabs are specific about which modifiers apply.  Unfortunately, |> the specification for XGrabKey doesn't allow AnyModifier to be combined |> with other modifiers, which is exactly what would be desired in this case: |> "Ctrl Any<Key>q". |>  |> >In ORA Vol. 6, in the section on accelerators it says "For information |> >on how to specify translation tables see Vol. 4...", this is so you |> >know what to put for the XmNaccelerator resource.  If you go to |> >Vol. 4 it says, "Likewise, if a modifier is specified, there is |> >nothing to prohibit other modifiers from being present as well. For |> >example, the translation: |> >	Shift<Key>q:	quit() |> >will take effect even if the Ctrl key is held down at the same time as |> >the Shift key (and the q key). |>  |> This is true for accelerators and mnemonics, which are implemented using |> event handlers instead of grabs; it's not true for menu accelerators.  If |> you're a Motif implementor, I'd suggest lobbying to get the Xlib semantics |> changed to support the feature I described above.  Otherwise, change the |> documentation for menu accelerators to properly set the user's |> expectations, because menu accelerators are NOT the same thing as |> translations. |>  |> >Is it possible to supply > 1 accelerator for a menu entry? |>  |> If you mean "menu accelerator", no it's not possible.  That's according to |> the definition of the XmNaccelerator resource in the XmLabel manual page. |>  |> >Keep in mind when answering this question that when using Motif you |> >can't use XtInstallAccelerators(). |>  |> I can't think of a reason why not. |>  |> >How can you ensure that accelerators work the same independent of |> >case?  What I want is Ctrl+O and Ctrl+o to both be accelerators on one |> >menu entry.  I find this thread on motif accelerators absoultly amazing.  If I were writing an interface to keyboard accelerators, I would have one resource called "accelerators" that took a translation table, period. I would also implement it so that programmer never has to do any work to get the accelerators installed.  As soon as the end-user specified one, it would be active and automatically installed.  To get multiple accelerators on a single menu item I'd do something like:  	*menuItem.accelerators: #override \n\ 		Ctrl<Key>M:	fire() \n\ 		Shift<Key>L:	fire() \n  The accelerators would work exactly like translations and you would automatically see a "Ctrl M" show up in your menuItem object.  Why in the world is the motif stuff so complicated with so many different special cases depending on what type of widget you're dealing with?  There has to be some reason.  Sorry for the political tone of this message...
herzog@dogwalk.Eng.Sun.COM (Brian Herzog - SunSoft Product Engineering) writes:  >I'm just guessing here, but I'd guess that X11R5 expects the CG3 to have >1152x900 resolution, and the version of the CG3 in the SPARCclassic is  >1024x768.  I've used X11R5 with classics set for both 1024x768 and 1152x900 (you can choose which resolution you want in the PROM monitor before booting).  One person had trouble with X11R5 that was fixed by using the multi-screen version.  Here's how our version was built. (You can just copy /usr/local/X11R5/bin/Xsun from farside.rutgers.edu if you just want to see whether this version will work.)    R5 distribution installed,         from pub/R5/mit-[1-4] and contrib-[1-3] on export.lcs.mit.edu   patches 1 - 23 installed, 	from pub/R5/fixes on export   R5 Xsun Multi-screen patches installed,  	from contrib/R5.Xsun.multi-screen* on export, 22-Mar-93   Solaris 2.1 patches installed, release 1/update 2, 	from contrib/R5.SunOS5.patch* on export, 22-Mar-93
Does anyone know of a source (book, file, etc.) of ALL the standard  resource names in X11R5? A small description of what the resource IS would also be helpful, but not vital. Any help in which direction to go would be greatly appreciated.  Thanks.  Robin Kinzy   ================================================================= | Office :                            |   Home :                  | |                                     |                           | | Brigham Young University            |                           | | College of Engineering & Technology |   Robin R. Kinzy          | | 270 Clyde Building                  |   1080 E. 700 N.          | | Provo, UT 84602                     |   Provo, UT 84606         | |                                     |                           | | Phone : (801) 378-7206              |   Phone : (801) 373-4657  | | Email : rrk@bones.et.byu.edu        |                           |  =================================================================
In article 1369@qdeck.com, support@qdeck.com (Technical Support) writes: >In article <1qtk84$rn5@picasso.cssc-syd.tansu.com.au> gpatapis@boyd.tansu.com.au writes: > >>What sort of traffic is generated with the X-calls?  I am curious to find >>out the required bandwidth that a link must have  if one machine running >>DV/X is supporting multiple users (clients) and we require adequate response >>time.  Anyone have any ideas ??   > >I expect the limiting factor will be your server machine, not the network >itself. To give you a real-world example, here at Quarterdeck we have >roughly 100 people using DVX to talk to a bunch of unix boxes, novell >file servers, and each other. It's not _too_ much of a load on our >Ethernet (with maybe 4 concentrators, so you have 20-30 people on each >segment). If you had a badly loaded net, or the apps you wanted to run >were very network intensive, you could run into some slowdowns. > >But the biggest problem would be the machine itself. Say you have a 486 >33 with plenty of ram and a fast hard disk and network card. If you have >10 people running programs off it, you're going to see some slowdowns >because you're now on (effectively) a 3.3 MHz 486. Of course, DVX will >attempt to see if tasks are idle and make sure they give up their time >slice, but if you have 10 working programs running, you'll know it. >  Well I can buy a bigger and more powerful server machine because of the  significant drop in price year after year.  The link I want to use  though (ISDN 64K) is costly and the bandwidth limited.  That's why my interest lies in seeing if such a link can be used and see what traffic  goes through it.   >Having said that, if you can tweak the programs being run (by adding >in calls to give up time slices when idle and that sort of >thing), you could probably run 15-20 people on a given machine before >you started seeing slowdowns again (this time from network bandwidth).  Hmmm.  Has anyone at your centre monitored the traffic at all?  Are you running any standard MS-Windows programs like Word ?  What sort of  packets go blazing through? What size link do you have (2Mb or 10Mb ?). What is the average traffic flow going through your network or do you have few high peaks and then many low points?   >It all really depends on what the programs are doing (ie. you're going >to see a slowdown from X-bandwidth a lot sooner if your apps are all >doing network things also...) >--   What do you mean by network things?  I vision using MS Windows and other Windows applications over the network were the processes are running on the server and all I am getting are the displays.  I am wondering how  good is the X and subsequently DV/X protocol in transferring these  images with X-calls and displaying them on a client's machine.   >       Quarterdeck Office Systems - Internet Support - Tom Bortels > Pricing/Ordering : info@qdeck.com  |  Tech Questions : support@qdeck.com >  BBS: (310) 314-3227 * FAX: (310) 314-3217 * Compuserve: GO QUARTERDECK >   Q/Fax: (310) 314-3214 from touch-tone phone for Technotes On Demand!
I'm going to be purchasing one of these soom for my SS2.  Does anyone have any experience with this card?  Positive or negative comments welcome!  Please respond immediately.  Thanks,    Joe
Is there aything available for X similar to QuicKeys for the Macintosh -- something that will allow me to store and playback sequences of keystrokes, menu selections, and mouse actions - directing them towards another application?  If so, could someone send me information on its availability -- and if not, how hard do we think it might be to send input to other X applications and, hopefully, deal with their responses appropriately?  (If an application is going to take a few seconds to process I probably have to wait  for it to complete before sending another command.)  thanks,
In article <C5qtKK.wp@cup.hp.com>, defaria@cup.hp.com (Andy DeFaria) writes: |> [ Article crossposted from hp.windows ] |> [ Author was Andy DeFaria ] |> [ Posted on Mon, 19 Apr 1993 18:08:38 GMT ] |>  |> For some reason the following code causes my X application to beep whenever I |> intercept a keystroke and change it's meaning.  The intent of this code it to |> allow "date" fields the following special keys: |>  |> 	[Tt]:	Insert today's date |> 	[+=]:	Bump day up by one |> 	[-_]:	Bump day down by one |>  |> I hardcoded some dates for this example.  Perhaps I shouldn't be using an |> XmText field for this. |>  |> //////////////////////////////////////////////////////////////////////////////  |> //  |> // For some reason the following code beeps whenever any of the special keys |> // of [Tt+=-_] are hit.  Why?  The idea of this code is to interpret these |> // keys having the special meaning implied by the code.  I would like to get |> // rid of the beeping but, as far as I can tell, I'm not doing the beep and  |> // am at a lose as to understanding who and why the beeping is occuring. |> //  |> //////////////////////////////////////////////////////////////////////////////    code deleted...  >From the XmTextField man page (during discussion of resources):     XmNverifyBell        Specifies whether a bell will sound when an action is reversed       during a verification callback.  You are setting doit to false in the callback, and Text[Field] is beeping as it should.  To turn off this behavior, set this boolean resource to false.
> pm860605@longs.LANCE.ColoState.Edu (Peter J. McKinney) writes:  > Price: > 		PC-Xview for DOS      $445.00 for 1  $1780.00 for 5   NCD just announced a new generation of PC-Xview. They changed the name a little though and I can't remember exactly... PC-Xsomething.
>> No, it isn't.  It is the "X Window System", or "X11", or "X" or any of >> a number of other designations accepted by the X Consortium.  In fact, >> doing "man X" on pretty much any X11 machine will tell you: >>  >>      The X Consortium requests that the following names  be  used >>      when referring to this software: >>  >>                                   X >>                            X Window System >>                              X Version 11 >>                      X Window System, Version 11 >>                                  X11 >>  >> There is no such thing as "X Windows" or "X Window", despite the repeated >> misuse of the forms by the trade rags.  This probably tells you something >> about how much to trust the trade rags -- if they can't even get the NAME >> of the window system right, why should one trust anything else they have  >> to say?  I used to think this way, and not just about X. For example, incorrect English constructs such as "its raining" or "it's window id" annoy me. However, there comes a time when popular usage starts to dictate the way things really are in the world. Indeed, the fact that X won out over NeWS was really down to popular opinion (I know, we all think it's(!) technically superior as well!).  On a related topic, who is to say that "color" is more or less correct than "colour" - being Irish, and hence using English English as opposed to American English, I always use the latter except, of course, for API terms such as "XAllocColor" and "colormap".  In a world that uses the term "Windows" to refer to Microsoft Windows, perhaps the time has come to accept "X Windows" as a valid term for X. I think that this is a more concise and uncluttered term than, say, "the X Window System" and, let's face it, almost everyone uses it. Ultimately, we all need product sales to more than just X-literate people. In this respect, product recognition is important and a short, snappy, descriptive title ("X" is positively obscure) will help when dealing with the average punter (it's sad - I thought I was a software engineer!). Indeed it is unfortunate that X did not become popularly known as Windows and let MS worry about whether it should be called "Microsoft Windows" or "the Microsoft Window System" or how about just plain "Microsoft"!  To summarise (or should that be "summarize") the point of this message: I think there are far more pressing issues facing the X community than worrying about subtle distinctions in the naming of the window system (or should that be "windowing system"). Whatever gets recognised is fine by me. I agree that one should be careful in interpreting what trade papers say. However, I would be reluctant to come to this conclusion purely on the basis of how they name the X Window System.
I posted this a while ago and didn't recieve one reply, and now we have another bug report on the same subject. Can anybody help me out?  How can you ensure that accelerators work the same independent of case?  What I want is Ctrl+O and Ctrl+o to both be accelerators on one menu entry.  In ORA Vol. 6, in the section on accelerators it says "For information on how to specify translation tables see Vol. 4...", this is so you know what to put for the XmNaccelerator resource.  If you go to Vol. 4 it says, "Likewise, if a modifier is specified, there is nothing to prohibit other modifiers from being present as well. For example, the translation:  	Shift<Key>q:	quit()  will take effect even if the Ctrl key is held down at the same time as the Shift key (and the q key).  This implies to me that setting XmNaccelerator to Ctrl<Key>o should do what I want, but it doesn't, it doesn't work if the user presses the control key, the shift key, and the o key.  Is it possible to supply > 1 accelerator for a menu entry? Keep in mind when answering this question that when using Motif you can't use XtInstallAccelerators().  I am using Motif 1.1.3 on a DECstation 5000 but I have also tried it on an HP using Motif 1.1.3 and 1.2.
How can I obtain public information (documentation and sources) about Xservers implemented with graphics processors?  I am specially interested in Xservers developed for the TMS34020 Texas Instruments graphic processor.
bernward@moepi.do.open.de (Bernward Averwald) writes:  >Yes. Don't confuse the mouse cursor with the text cursor in the xterms. >The latter is only controlled by the application. >Back in the days of X11.1 I did analyse the xterm code. The cursor  >was implemented by drawing a rectangle around the character. I doesn't >seem to be changed 'til now. >But if you have the sources you could add a blinking cursor via >XtAppAddTimeOut or similar :-|.  Xt(App)AddTimeout doesn't work in xterm, because, despite appearances  to the contrary, xterm is not really an Xt based application.  "Other sources" like timeouts and inputs are never checked in xterm's main loop. So don't be surprised when you try this and it doesn't work.  --
In article bjg@acsc.com, dev@hollywood.acsc.com () writes: > >Will there be any support for round or circular widgets in Motif's next >release?. I'd love to have a circular knob widget which could be used >instead of a slider.  How much support do you need?  I don't think there's anything that prohibits you from implementing such a widget, though you will have to write your own versions of the functions that draw the 3D shadow and traversal highlighting.
Hello Everybody!  I have a little question:  Due to more features (PEX, Drag&Drop) many applications when linked with for example Motif 1.2 instead Motif 1.1 need more memory in the Xserver. X-terminals only have limited memory (normally no swapping possible). So my question:  Is there a possibility to determine via X protocol calls the size of free memory available to the Xserver?  So one can determine for example whether to start a PEX application with the CSS on client side or on server side (when there is enough memory).  Please reply via e-mail, I'll summarize!  Sincerly,         Matthias