waashk/20ng huggingface dataset:
In article <1993Apr16.093209.25719@fwi.uva.nl>, stolk@fwi.uva.nl (Bram) writes:  > I am using an X server that provides 3 visuals: PseudoColor 8 bit, > Truecolor 24 bit and DirectColor 24 bit.  Lucky dog... :-)  > A problem occurs when I try to create a window with a visual that is > different from the visual of the parent (which uses the default > visual which is TC24).  > In the Xlib reference guide from 'O reilly one can read in the > section about XCteateWindow, something like: >     In the current implementation of X11: When using a visual other >     than the parent's, be sure to create or find a suitable colourmap >     which is to be used in the window attributes when creating, or >     else a BadMatch occurs.  > This warning, strangely enough, is only mentioned in the newer > editions of the X11R5 guides.  It applies with equal force to earlier versions.  Presumably only recently did the author(s) decide it was important enough to mention. The necessity it refers to has always been there, but it's been implicit in the way CreateWindow requests default some attributes of the new window.  > However, even if I pass along a suitable colourmap, I still get a > BadMatch when I create a window with a non-default visual.  >   attr.colormap = cmap; >   win = XCreateWindow( [...] >           CopyFromParent,       /* border width */ >           8,                    /* depth */ >           InputOutput,          /* class */ >           vinfo.visual,         /* visual */ >           CWColormap, >           &attr >         );  This is because the warning you read is incomplete.  You have to provide not only a colormap but also a border.  The default border is CopyFromParent, which is not valid when the window's depth doesn't match its parent's.  Specify a border-pixmap of the correct depth, or a border-pixel, and the problem should go away.  There is another problem: I can't find anything to indicate that CopyFromParent makes any sense as the border_width parameter to XCreateWindow.  Your Xlib implementation probably defines CopyFromParent as zero, to simplify the conversion to wire format, so you are unwittingly asking for a border width of zero, due to the Xlib implementation not providing stricter type-checking.  (To be fair, I'm not entirely certain it's possible for Xlib to catch this.)  					der Mouse
In article AA16720@ntep2.ntep.tmg.nec.co.jp, cerna@ntep.tmg.nec.co.JP (Alexander Cerna (SV)) writes: >I need to write an application which does annotation notes >on existing documents.  The annotation could be done several >times by different people.  The idea is something like having >several acetate transparencies stacked on top of each other >so that the user can see through all of them.  I've seen >something like this being done by the oclock client. >Could someone please tell me how to do it in Xt? >Thank you very much.  The oclock widget was written using the SHAPE extension. You can do the same in your widgets.  Few current widgets support SHAPE, so you'll have to subclass them to add that functionality.
In article <1993Apr15.155255.27034@thunder.mcrcim.mcgill.edu> mouse@thunder.mcrcim.mcgill.edu (der Mouse) writes: >In article <C5DuHC.71p.1@cs.cmu.edu>, das+@cs.cmu.edu (David Simon) writes: > >>Can some one please explain to me why the following piece of code >>causes twm (or tvtwm) to dump core [...] > >>In particular, I am interested in knowing whether this behavior is >>caused by a bug in my reasoning, or if it is a bug in twm. > >If *anything* a client does causes twm to dump core, it's a bug in twm. >Window managers should never *ever* crash.  Would if only it were true ...  If only MIT would fix the !@&$^*@ twm "InstallWindowColormaps()" crash bug once and for all, then I could say that I've (almost) unable to crash either "twm" or "tvtwm", which would be a remarkable feat - and most desirable to boot.  I mean, this bug has only been reported, oh, a zillion times by now ...  Now *servers*, on the other hand ... (want to crash an OpenWindows 3.0 "xnews" server at will?  Just do an 'xbiff -xrm "XBiff*shapeWindow: on"'.  Blammo.)
In article <1quh74$r71@irz401.inf.tu-dresden.de>, beck@irzr17.inf.tu-dresden.de (Andre Beck) writes: |>  |> In article <C5oL74.3B1@aeon.in-berlin.de>, thomas@aeon.in-berlin.de (Thomas Wolfram) writes: |> |> >Hey guys! |> |> >I work on many stations and would like this name and current logname |> |> >to be in a title of Xterm when it's open and a machine name only |> |> >when it's closed. In other words, I want $HOST and $LOGNAME to appear |> |> >as a title of opened XTerm and $HOST when XTerm is closed. |> |> >How can I do it? |> |>  |> |> Almost all window managers (twm, mwm, olwm and their derivates) support |> |> escape sequences for it. For your purpose put following into your |> |> .login (if you're using csh or tcsh), for sh you have to modify it. |> |>  |> |> if ( "$term" == "xterm" ) then |> |> 	echo "^[]2;${LOGNAME}@${HOST}^G^[]1;${HOST}^G" |> |> endif |> |>  |>  |> 1) This is NOT a feature of the Window Manager but of xterm. |> 2) This sequences are NOT ANSI compatible, are they ? |>    Does anyone know IF there are compatible sequences for this and what they |>    are ? I would think they are DCS (device control sequence) introduced, |>    but may be a CSI sequence exists, too ? |>    This MUST work on a dxterm (VT and ANSI compatible), it may not work |>    on xterms.  It works on xterms. At least I have no problem with it. - Back to the original question:  I usually start new xterms by selecting the proper menu entry in my desktop menu. Here is a sample command:  	xterm -sl 999 -n ls12i -title ls12i -e rlogin ls12i &  The -n and -title options give the text for window and icon. As I use the tcsh (a wonderful extension of the csh), I can do the following:  I have an  	alias precmd echo -n '^[]2\;${HOST}:$cwd^G'  in my ~/.tcshrc. This is a special alias for tvtwm. It is executed each time before printing the prompt. So, I have the current host name and the current directory path in the title bar of my xterms.  ------------------------------------------------------------------------------       ____                                                                       UniDo  /  Ingolf Markhof  University of Dortmund, LS Informatik XII           ___/   /                   P.O. Box 500 500, D-4600 Dortmund 50, F.R. Germany  \  \  /                    Phone: +49 (231) 755 6142, Fax: +49 (231) 755 6555     \__\/                     Email: markhof@ls12.informatik.uni-dortmund.de
The following problem is really bugging me, and I would appreciate any help.  I create two windows:  w1 (child to root) with event_mask = ButtonPressMask|KeyPressMask; w2 (child to w1) with do_not_propagate_mask = ButtonPressMask|KeyPressMask;   Keypress events in w2 are discarded, but ButtonPress events fall through to w1, with subwindow set to w2.  FYI, I'm using xnews/olvwm.  Am I doing something fundamentally wrong here?
Check out a program called PC-Xview. I've used it before, and from what I can tell, it's exactly what you're looking for. Last I checked, you should be able to find it for about $160 a copy.  -Eric
Extract from the color README file for Anthony's Icon Library. For Network discussion...  Color Coordination...      I tried to start a discussion in `comp.windows.x' at the start of the   year about some sort of `standard color table' that icons should follow   (say 16 to 32 colors including 5 colors for a small grey scale). but no   one responded at all.      The problem is that if the colors for icons are just used willy-nilly   you will soon find that the workstations color table, devotes itself   solely the window manager, icons and other `adminstrative tasks' instead   of applications that actually require the colors for proper working.   ``Color needful applications'' such as :  Picture and graphic displayers,   Animation, Real Time video, Raytracers, etc... .      The following is a suggested color table for icons, and general use.   Icons, Window Managers, and general applications, should follow this   table or something like it, UNLESS the application is ``color needful''.       * for each primary color (red,green,blue) three colors              EG: values   0, 128 and 255.        This results in  3 ^ 3  colors (27) representing most of the        standard colors for use in icons.       * two extra shades of grey              EG: vales    (black) 0, 64, 128, 196 and 255 (white,red,...)       * 3 other colors -- probably of some primary color to provide shading        a and 3-D look to buttons and titlebars in the window manager.      This table represents 32 colors and represents a large range of   posibilities for the above ``administrative services'' of the   workstation.     Anthony Thyssen - (SysProg @ Griffith University)     anthony@cit.gu.edu.au ------------------------------------------------------------------------------   A Gods idea of amusement is a Snakes & Ladders game, with greased rungs.                                            - Terry Pratchett   "Wyrd Sisters"
In article <C5JJIG.Doy@acsu.buffalo.edu>, lusardi@cs.buffalo.edu (Christopher Lusardi) writes: |>  |> What is the directory .X11-unix for in /tmp? When I start |> x, it is created by the system. This directory wasn't created  |> by root, and it contains an empty file (X0) that is owned by me.  |>   It's the Unix Domain Socket (local connection) to your XServer. Try to rm it :)
In article <1993Mar31.181357.28381@sierra.com> dkarr@sierra.com (David Karr) writes: <I might have a need in the future to display rotated text.  I noticed the <"xvertext" package on the net.  It looks very good, but it has one slight <problem.  The API to it assumes you have a font name, not an already loaded <font.  It shouldn't be too difficult to split up the function into two <interface routines, one with a font name, and one with an XFontStruct, but <I thought I would ask the author (Alan Richardson <(mppa3@uk.ac.sussex.syma)) first in case he was planning this already. <Unfortunately, his email address bounced.  Does Alan R. or the current <maintainer of "xvertext" see this?  The e-mail address you mentioned above is for use with the U.K.  As you know, the Brits do everything backwards :-)  So, the real address from the states is:  	mppa3@syma.sussex.ac.uk  Give it a try.
I'm not familiar at all with the format of these "X-Face:" thingies, but after seeing them in some folks' headers, I've *got* to *see* them (and maybe make one of my own)!  I've got "dpg-view" on my Linux box (which displays "uncompressed X-Faces") and I've managed to compile [un]compface too... but now that I'm *looking* for them, I can't seem to find any X-Face:'s in anyones news headers!  :-(  Could you, would you, please send me your "X-Face:" header?  I *know* I'll probably get a little swamped, but I can handle it.  	...I hope.
Hi,     We have a requirement for dynamically closing and opening different display servers within an X application in a manner such that at any time there is only one display associated with the client.     Assumming a proper cleanup is done during the transition should we anticipate any problems.
Does anyone know how I can obtain information about the ICS widget data book? I only have their email address, and they don't seem to be reading (or  replying) to their mail.    --------------------------------------------------------------------------  ! Jan-Olav Eide, Software Engineer / Systems Administrator                 ! ! snail mail :                      ! email :                              ! ! Nordic Offshore Systems           ! olav@nordic-offshore.no              !   ! Drilling Information Services     ! voice :                              ! ! Ringsveien 3, Box 185             ! (+47) 67125580 ext. 211              ! ! 1321 Stabekk                      ! fax   :                              !  ! Norway                            ! (+47) 67125401                       ! ! "I don't believe in astrology.  But then I'm a Capricorn, and            ! ! Capricorns don't believe in astrology"                                   !  --------------------------------------------------------------------------   --
In article <1993Apr30.084145.20953@cv.ruu.nl>, rvloon@cv.ruu.nl (Ronald van Loon) writes: } In <46464@sophia.inria.fr> muller@mafalda.inria.fr (Christophe Muller) writes: }  }  } |"> It is interesting to look at the change(s) of mind that John has had. } |" } |"Very interested indeed! This is against this kind of "changes" that the GNU } |"COPYLEFT is protecting us. } |" } |"Anyway, at SIMULOG, we will abandon xv. We were using it mostly for slide- } |"shows because of its "-loop" feature that display does not have (display } |"from the *wonderful* ImageMagick package! :-D), but I think I will implement } |"it myself (even a shell-script should do the job) and forget xv.  We too will have to stop using it. Shame really - it was rather nice. Still, I have no objection to the owner claiming money for legit.  work he's put in. We'll just go back to the older versions of Xv.
Are there any widgets, function  	librarys for drawing networks,  	graphs etc ? (Not tree views)  	Freeware, shareware, comercial... 	Like this, for instance:                                                                                           O                           |                           |                 O---------O=======>O                / \        |               /   \       |         O----O.....O      O             / \            /   \            O     O  	* Just by giving the associations  	  between the nodes. Automatic 	  layout generation.  	* It would be nice if any node  	  symbols could be used. Maybe  	  even to insert widgets as nodes.  	* Using different line styles etc. 	  for describing associations.  	Any information would be appreciated, 	thanks in advance,
In article <1r3th9INNdtp@tom.rz.uni-passau.de> rank@winf.uni-passau.de (Christian Rank) writes: >I've installed X11R5 with patches for Solaris 2.1 on our SPARCstation LX / >SPARCclassic pool. On the LX, X11R5 runs fine, but on the classics, >after giving the command startx, Xsun prints the following messages: >	WARNING: cg3_mmap: can't map dummy space! >	Mapping cg3c: No such device or address >and exits. > >Does anybody know how to fix this problem?  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.  --
Yesterday I changed the US-Keyboard of my Sparc10 with a german keyboard. And now I cannot get any "Alt Graph" characters ('tilde' usw.). When I exit from X I can get the characters, but not under X.  Can anybody give me some hints, where to check for the correct installation of the keyboard.
OK, many people emailed me asking for information on Congruent Corporation's product which allows X/Motif unix applications to function on Windows NT. Today I was sent a telephone number by a kind person by the name of Sam (I'd give better attribution, but the mail is in a different application on VMS :-()  The number to call in New York City is (212)431-5100  The email address is info@congruent.com  The product is NTNIX.  Other details I do not know.  They said they'd send me email info, but as yet it has not arrived. More as I get it. Cheers Folks! --  snail@lsl.co.uk
The short answer seems to be: "I don't". The particular package (wscrawl) seems to reset *all* its defaults if *any* of them are missing from the .Xdefaults file.  Once I added the missing ones to the .Xdefaults file, the problem goes away.  -Kevin
>>>>> Regarding Re: SUMMARY: virtual mouse in ol{v}wm; >>>>> euamol@eua.ericsson.se (Mats Larsson) adds: : VirtualGrabKeys is not an OW resource. It belongs to olvwm(1).  Not only that, the olvwm(1) (version3.3) man-page says it's called
markw@pspmf3.gpsemi.com (Mark Wilkinson - Ext 3443) 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.   If you already own all the "clone" equipment then there are lots of such programs (see a current copy of Unix World Magazine).  *BUT*  your performance WILL suck lemons running an Xserver on a clone. (From experience).  You would be much better off with an Xterminal if this is a new install.  The performance will be at least four times better. In addition it would be MUCH easier to install and use.  On top of that they will cost about the same (price a clone with 4MB RAM, ethernet card, very high performance graphics card, GOOD monitor, server software, TCP/IP for clone software, mouse, keyboard, etc, etc, etc.... you spend a whole lot of $$$$).  I can get 15" Tektronix XP11 terminals for under $900, and the performance is over 80000 Xstones.....
Megan Grenenger (megan@cs.uq.oz.au) wrote: : I'd appreciate any feedback on capture/playback tools for use with X clients.  : Any comparisons/comments on regression testing tools would be great - : particularly XTM, XRunner, Autotester, and SRI's CAPBAK, SMARTS and EXDIFF.  How about starting where I could find ANY of these.  For the commercial ones, at least a phone number would be appreciated.
In article ( ), wsmart@tay.mcs.dundee.ac.uk (Bill Smart) writes: > To get the number back, the other client does: > >  AppAtom = XInternAtom(display,"ApplicationWindow",True); >  XGetWindowProperty(display,DefaultRootWindow(display),AppAtom,0,8192, >                     False,XA_WINDOW,&return_type,&return_format, >                     &nitems_return,&bar,&return_place); > > and appears to get back something valid (just not the right number). > It always seems to return the same number, regardless of the window > number stored in the property.  "return_place" is probably incorrect.  It should be a pointer, not an integer.  XGetWindowProperty() allocates memory, copies the data there, and returns a pointer to the memory.  You should free the memory when you're done.
(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.
According to the OSF/Motif Style Guide, one should use cursor shapes to give the user a visual clue of what is happening or what is expected of him. So a "hourglass" cursor should be shown when the application is busy, or a "caution" cursor should be shown over an area when input is expected in another. Defining cursors for widgets has to be done at rather low level. So defining a cursor for all widgets in an application but not for a certain subpart of it, is a rather complicated matter. When cursors have been defined for some windows, e.g. a "crosswire" cursor for a DrawingArea, things get even more complicated. My intuition says that things should be easier, but is this so? If anyone has a solid and complete solution to my problem, please let me know. The topics on "busy cursors" in the several FAQ's are not helpful, since they only work for applications where all windows have the cursor window attribute set to 'None'.
Xsun won't come up in color w/ this framebuffer! I am trying to use xkernel on some of these 4/110s I have a freshly built Statically linkes copy of Xsun that works just fine on cg6, cg4, bw2 type of framebuffers, but on the 4/110 that have this type of frame buffer all I get is Mono.  cgtwo0 at vme24d16 0x400000 vec 0xa8  cgtwo0: Sun-3 color board, fast read  Here is what I've tried.  removing all the other /dev/cg* , /dev/bw , and /dev/fb and then selectivly recreating /dev/cgtwo0. Xsun comes up mono. recreating /dev/fb, comes up mono,  I've tried Xsun & Xsun -dev /dev/cgtwo0.  PS Xnews will come up in color but it's not statically linked, and the dynamically linked Xsun comes up in mono also.  PPS Xsun was compiled on w/ gcc 2.3.3 on a system running 4.1.3 and the 4/110 is also running 4.1.3.  Thanks n advance --  - ..  the HIGHWAY is made out of LIME JELLO and my HONDA  is a barbequeued OYSTER!  Yum!
I posted about this a while ago but without code excerpts noone was  able to help me.  The problem is that main_win.win is doing fine, but when I create  detail_win.win, it does not receive it's initial expose events until  main_win.win receives an event. Here are the relevent calls:  main_win.win = XCreateSimpleWindow (mydisplay, DefaultRootWindow(mydisplay),                 myhint.x, myhint.y, myhint.width, myhint.height,                 main_win.line_thick, fg, bg); XSetStandardProperties(mydisplay, main_win.win, main_win.text,                 main_win.text, None, argv, argc, &myhint); main_win.gc = XCreateGC (mydisplay, main_win.win, 0, 0); XMapRaised (mydisplay, detail_win.win); XMapSubwindows (mydisplay, main_win.win); The event mask for main_win is: 	PPosition | PSize | StructureNotifyMask | ExposureMask| KeyPressMask |  	EnterWindowMask | LeaveWindowMask; The flags are 	PPosition | PSize  I then create detail_win.win with the following calls (hints has new values): detail_win.win = XCreateSimpleWindow (mydisplay, DefaultRootWindow(mydisplay),                 myhint.x, myhint.y, myhint.width, myhint.height,                 detail_win.line_thick, fg, bg); XSetStandardProperties(mydisplay, main_win.win, detail_win.text,                 detail_win.text, None, argv, argc, &myhint); detail_win.gc = XCreateGC (mydisplay, detail_win.win, 0, 0); XMapRaised (mydisplay, detail_win.win); Event Mask and flags are identical to main_win's flags and event mask.   If anybody has any idea why the initial expose events of detail_win.win  are not received until main_win.win receives an event I'd love to hear  from them. Other that that everything works great so there must be some  detail I'm overseeing.
[again, poseted for a friend]  Okay, I got such great response from my last question (thanks, everyone),  lets try again:  How can I tell if a colorcell is read-only?  I want to use any read-only cells that are already in my colormap once I start running out of allocatable cells, using some arbitrary nearest color matching scheme to get those cells that come closest to a requested color.  Once I determine if a cell is read-only, I assume I can then just request an XAllocColor() with the exact same color specifications and it will  then be flagged as 'used' by my application so that it doesn't later get freed by someone else and allocated again as read-write to another application.  So far, the only way I've figured out to do this is to write my own error handler and just go ahead and request the cells colors, once my colormap is all full up.  It should error out if the cell is non-shareable. But life would be much easier if I could just detect the read-only/shareable stuff directly...  Any ideas?