Aaron Lewis wrote:
> Hi ,
> i wanted to setup default window size for xconsole program ,
> although i'm on openbox , but still wanted to use Xdefaults file ,
> but how ?
XConsole.width: 640
XConsole.height: 480
-
each other.
Support for pixel buffers is indicated by the presence of
GLX_SGIX_pbuffer in the extension list. Whether a GLX visual is
double-buffered is indicated by the "db" column in the glxinfo output.
--
Glynn Clements
___
xorg@lists.fre
x11vnc
(acceleration requires local video hardware, limited by frambuffer
read speed, inter-client communication needs explicit handling, etc).
AFAICT, the only advantage is "rootless" operation.
--
Glynn Clements
___
xorg@lists.freedesktop.or
communicate with
the matching instance of client B, or just have the "primary" instance
of client A communicate with a single instance of client B?
Of the four programs in the paper, only Xmux got a "strong pass" for
supporting cut and paste.
--
Glynn Clements
__
ensure that the new X server will behave exactly like the old one, or
make the client adjust to the change. The former is somewhere between
ridiculously difficult and completely impossible, while the latter
requires significantly changing the protocol, libraries, toolkits, and
connects to a
specific X server which performs all rendering. You have the option to
forward rendered images to other systems for physical display.
2. Use GUI toolkits which offer an abstract, high-level interface to
the client. The toolkit has the ability reconstruct and clone windows
at will.
--
G
is
> #X11UseLocalhost yes in /etc/ssh/sshd_config
> commented out. Does changing that need a reboot?
It requires restarting sshd, either with "kill -HUP ..." or whatever
mechanism your Linux distribution uses for managing services (e.g.
something like: "/etc/init.d/sshd rest
r via X11UseLocalhost in sshd_config, but in the absence of
some form of firewall, that will allow other hosts on the network to
connect to the X proxy.
--
Glynn Clements
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.o
y to succeed than
one via TCP; X servers are often configured to ignore TCP connections
as a security measure. It's also more efficient.
> 3) is it possible to provide "hostname"=1.2.3.4. (which is an
> IP-address), instead of the name of the computer ?
Yes.
--
Glynn Clemen
s/minicom
--
Glynn Clements
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
and that's all.
One possibility is to run it under "screen", which allows arbitrary
remapping of keys, and remap the cursor keys to function keys (which
can then be rebound within minicom). Another possibility is to modify
minicom's source code. Yet another possibility is to
you want
large virtual desktops, the WM just needs to be creative.
--
Glynn Clements
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
_PATH if you
need to use a different version on a per-process basis (e.g. if
DISPLAY points to a remote display and the default libGL can't handle
that).
--
Glynn Clements
___
xorg@lists.freedesktop.org: X.Org support
Archives: http
Burton Samograd wrote:
> I was wondering if there was a standard way to create a window using
> Xlib and have it be non-resizable (like a dialog). Would this be
> through a window manager hint or something like window creation flags?
See XSetWMSizeHints.
--
Glynn
ify to obtain notification of changes, and it will
receive notification regardless of the override_redirect flag.
It's only the ability to "veto" changes via SubstructureRedirectMask
which is limited to one client at a time, and overriden by the
override_redirect flag.
, it may be impossible to
determine the resolution of the physical screen. This may not even be
a meaningful question, as there won't be a physical screen when no
viewer is connected, and there will be multiple physical screens when
multiple viewers are
LAY, or pass something other than NULL as the display
argument to XOpenDisplay(). Ideally, the program should provide a
-display switch to specify the display to connect to.
--
Glynn Clements
___
xorg@lists.freedesktop.org: X.Org support
Ar
Rashid wrote:
> is there a way to scale a pixmap / image / frame buffer content with
> native xlib-Code.
No. The core X protocol doesn't include this functionality. You need
to use an extension (e.g. XRender, Xv, GLX).
--
Glynn Clements
_
s don't show
> the same behavour and the whole thing somehow feels quite inconsistent
> :(
GCs aren't associated with a window. The drawable passed to XCreateGC
is used to specify the screen and depth, but has no significance
beyond that. A GC may
keeping record of prerequisite resources.
> >
> > Because it's ridiculously difficult.
>
> Something like Xpra ?
That's essentially Xvnc except that it uses Composite to do it
window-by-window rather than for the whole screen.
--
Glynn Clements
where it
disconnects from one server and connects to one with completely
different parameters.
--
Glynn Clements
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.freedesktop.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com
ask, &maskshade, NULL))
You have the parameters backwards; the pixmap comes before the mask.
Consequently, skullImage.clipmask contains the pixmap, while maskshade
contains the mask.
That causes this:
XSetClipMask(mainwindow->display, mainwindow->gc, skullImage.clip
XSetFunction(dpy, gc, GXor);
XCopyArea(dpy, image, win, gc, ...);
The image must have all background (transparent) pixels set to zero.
Also, you can use XPutImage() instead of XCopyPlane() and XCopyArea().
--
Glynn Clements
___
xorg@lists.fre
ore concurrent X servers than you have video cards), that the
hardware (and its driver) is capable of sharing the card between
multiple X servers.
--
Glynn Clements
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.
ch opens a
connection, runs an event loop then closes the connection is
indistinguishable from a more typical client. Successive calls to that
function would appear as distinct short-lived clients. The server only
sees connections; what happens on the client side of those connections
is irr
hanges, which can be
inefficient if the data is large and/or if there are many targets
(some of which may be computationally expensive to generate).
--
Glynn Clements
___
xorg@lists.freedesktop.org: X.Org support
Archives: http://lists.freedesktop.org/ar
tSet if the "international" resource is True
and font otherwise, while Motif uses fontList. Xt-based programs which
have had Xft support added (e.g. xterm) tend to use faceName and
faceSize.
Having said all that, there's no guarantee that CrossOver's font
configuration is i
ne and formerly known as "CrossOver Office", I wouldn't expect it to
support configuration via X resources. I suggest that you refer to the
CrossOver documentation for guidance.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
all XKeysymToString() on each KeySym.
You probably don't need to explicitly send Alt/Shift/etc events;
simply setting the state field in the XKeyEvent structure should
suffice.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
when it receives a particular key or
button event.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
things, being different is automatically a loss, so you
have to do better on the other aspects just to break even.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
implemented in Xmu.
AFAIK, libXt and libXmu are still part of the modular X.org
distribution (the editres client was removed in 7.4 onwards).
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
children for non-Composite widgets.
At some point, the Editres support in libXmu was changed to include
"associated" widgets (any resource of type XtRWidget whose parent is
the specified widget) along with the children. This is specific to
Editres, though; such widgets aren't considere
umLock,
> CapsLock or combinations of these) are active.
>
> Which one is the nicest way to catch Alt+F8
> irrespectively of the state of Lock keys?
Grab F8 with all combinations of lock modifiers in addition to Mod1,
i.e. 2^N separate grabs, where N is the number of lo
If your locale is for a Latin-based language, you should be able to
use dead keys and compose processing. For a UK keyboard, AltGr and the
rightmost keys (=[]#'/) normally act as dead keys, while Shift-AltGr
is Compose.
There is more information on the API in §13.5 of the Xlib manual.
Unless you're planning on spending the next few months learning how
text entry works for languages other than English, I'd recommend using
a GUI toolkit rather than trying to do it using bare Xlib. Or at least
steal the code from such a toolkit.
--
Glynn Clements
___
x, or
similar, it will be woken (changed from sleeping to running) when some
other process affects its state (e.g. writes to the other end of a
pipe), rather than in response to a hardware event.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
DELETE_WINDOW as the type atom,
rather than simply destroying the window. The application can simply
ignore the message.
However, like a lot of things in X, this relies upon the WM
cooperating. If the WM also provides a feature to "destroy" (as
opposed to "delete") a window, you
GDM specifically (I don't use it, and the
documenation is silent on this issue), but it's possible that either
GDM or the default startup scripts perform the equivalent of
"xhost +local:" or "xhost +inet:localhost".
--
Glynn Clements
_
d all other windows
would be hidden. The WM would revert the changes when the window is no
longer active or no longer exists.
There's a chicken-and-egg problem in that WMs aren't likely to support
this feature if nothing uses it, and until it's widely supported,
applications wanting fu
XF86VidModeSwitchToMode(dpy, DefaultScreen(dpy), best_mode);
XF86VidModeSetViewPort(dpy, DefaultScreen(dpy), 0, 0);
XFree(modes);
XCloseDisplay(dpy);
return 0;
}
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Alan Coopersmith wrote:
> > Does the X protocol use specific IP ports?
>
> TCP port 6000 + display id, i.e. :0 = 6000, :10 = 6010.
Also, UDP port 177 for XDMCP, but you probably don't need that (it's
mainly for "dumb" X
ft+2 is
"atsign" on a US keyboard but "quotedbl" on a UK keyboard).
XLookupString() etc can just look at the keysyms without worrying
about where they came from.
Modifiers not related to text entry don't affect the keysym, but are
simpl
_event field set unless the "Allow SendEvents" option is
enabled).
It may be possible to use the XTest extension (i.e. XTestFakeKeyEvent)
if you need to generate events which don't have the send_event field
set.
--
Glynn Clements
_
the application. Some inherently generate a lot of
traffic, others generate unnecessary traffic due to the author(s) not
understanding X.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
nder directly, but there's unlikely to be any
advantage to doing so).
The core X protocol doesn't support alpha blending; apart from
anything else, it's only meaningful with StaticGray and TrueColor
visuals.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
s
> similar to:
>
> void XGetResourceMaskAndBase(XID resource, XID *mask, XID *base);
Not quite; libXRes has:
typedef struct {
XID resource_base;
XID resource_mask;
} XResClient;
Status XResQueryClients(Display *dpy, int *num_clients, XResClient **clien
grab is made by a screensaver which requires a password to
unlock the display, it's rather important to ensure that someone can't
just walk up to the system and bypass the screensaver via WM hotkeys.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
solving this feature through other means is appreciated
> > (note that registering for events on every visible window doesn't count).
>
> Limiting events to the application windows doesn't seem that bad.
That would mean that menus persist until yo
ourmap, set linear ramps, then treat it as TrueColor.
The number of programs which break with a DirectColor visual suggests
that they're essentially a theoretical concept which doesn't occur in
practice.
--
Glynn Clements
___
xorg mailing list
x
e"
size only gives me 70 columns, a slightly smaller font would almost
certainly be preferable.
An obsession with physical size makes no more sense than an obsession
with pixel sizes. Actually, it makes less sense. At least the
historical fixation on pixel sizes had a rational basis: rescaled
bi
y?
Having said that, modern applications aren't exactly immune from
adjusting requirements according to ease of implementation. Try using
some on a remote display with 500ms lag.
[The "Clueless Idiot of the Year" award goes to the Py
to eliminate that requirement, the video palette will
disappear overnight.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
s takes a lot of time that someone trying to get a
> product out the door doesn't have.
Application programming documentation normally focuses on a specific
toolkit. The toolkit will hide most of the details, particularly if it
is cross-platform. The low-level documentation is of interest m
r lack of results.
IOW, you ask, people answer, you don't like the answer (probably
because you didn't ask the right question in the first place), then
claim that no-one answered.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Ross Burton wrote:
> I can't believe I'm feeding the troll, but in GNOME (and KDE I'm sure)
> there is a nice big "Antialiasing: off" button in the font
> configuration.
And where is the "Prefer legibility over getting the exact physical
size to within a
Xlib?
>
> Are there programming references for the various extensions, or do I
> need to work from protocol specifications and uncommented header
> files?
http://www.x.org/docs/
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
ything
else, it's possible that your changes will be discarded whenever the
application (or WM) updates the WM_HINTS property.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
kground, border styles,
> prompt frames background, etc. .
The overall layout of the login widget isn't configurable, although it
can be completely replaced using the DisplayManager.greeterLib
resource.
--
Glynn Clements
___
xo
ow a window is
divided up, let alone definite information.
Realistically, you are going to need to handle each toolkit
separately, possibly even modifying the toolkit.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
is a bug
> in the graphics driver?
Your findings suggest that something may be treating window IDs as
being unique globally rather than per-display.
If you're using a proprietary OpenGL driver, that would be a prime
suspect. Try forcing indirect rendering with AI
4
display:':2.0',screen: 0, root window id: 253, window id: 24
display:':2.1',screen: 1, root window id: 255, window id: 44
The most significant 11 bits of the XID indicate the client, leaving
21 bits for each client, giving each client 2^21 (= 2,097,152) XIDs.
In any case, I doubt that this has anything to do with your problems
with OpenGL.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Masaru Nomiya wrote:
> Subject: Re: xclock's problem
> Message-ID : <18855.23177.348554.585...@cerise.gclements.plus.com>
> Date & Time: Fri, 27 Feb 2009 03:14:17 +0000
>
> [Glynn] == Glynn Clements has written:
>
> Me>> I'm using xl
onversion to be done in hardware, look at OpenGL or
XRender. It's implementation-dependent whether either of these
supports a specific format (other than 24-bit RGB), so you still need
to provide a software conversion.
--
Glynn Clements
___
xorg
strftime "%Y年%m月%d日(%a)
> %H時%M分%S秒" &
I don't know if it's related to your problem, but you should probably
be using e.g.:
-xrm "*fontSet: -*-*-bold-r-normal--16-*"
instead of -fn.
Also, try using the -norender option.
--
Glynn
*has* the functions gtk_window_set_decorated() and
> gdk_window_hide(). I am not trying to do something out of the ordinary
> here. I'll thank you kindly to stop imposing your assumptions on me.
There's a big difference between using the standard APIs and what you
outlined in your original post.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
ation. Your
application makes requests which the WM may or may not honour,
depending upon competing requests from other clients, user
configuration, and a zillion other factors.
The best that you can do is to learn how to speak the WM's language,
so that you can ensure that y
rver but
isn't actively being used will get swapped out, allowing the physical
memory to be used for something else.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
U XtVaCreateWidget
U XtWindow
U XtWindowToWidget
XtOpenDisplay() calls XtDisplayInitialize(), so if it's getting the
Display* from there, it should work. If the Display* comes from
elsewhere (e.g. Gtk/Gdk), it probably won't.
--
Glynn Cl
ositing managers", I've yet to find a sufficiently detailed
> explanation of what compositing is doing and how it is invoked or
> configured for me to understand how I should be managing our
> application's windows to make use of it. Another pointer to a good
> reference would be appreciated.
I don't know enough about compositing to answer this one.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
this until the client has actually connected to an X server.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
r:
1. add a mechanism to indicate that the parameter has changed, and
ensure that applications allow for such changes, or
2. expose an interface which either the toolkit or the X server can
emulate in its entirety atop a dumb framebuffer, and eat the
(potentially huge) performance hit when
p, with the ability to enable and disable screens. Obviously,
windows would have to either be opened on the appropriate screen
(programs which need the 3D GPU on the screen which has one), or the
application/toolkit would need to explicitly provide migration.
--
Glynn Clements
u need to bear in mind that properties which may previously
have been regarded as constant (e.g. root window, available visuals,
default visual etc) will become variables if you start migrating
between screens. Also, I don't know if the above will automatically
reconstruct e.g. pixmaps fo
ither start the client on a proxy X server with "mobile" output
(e.g. Xvnc), or this sort of thing has to be done in the client.
--
Glynn Clements
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
; if that uses 100% CPU, then the problem is
with decoding the video rather than displaying it.
--
Glynn Clements <[EMAIL PROTECTED]>
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
nti-aliasing will either be using XRender (or
maybe OpenGL), or rendering client-side and blitting the end result.
--
Glynn Clements <[EMAIL PROTECTED]>
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
tion of the pixmaps than trying to control everything else.
A more fruitful solution would probably be to use a compacting
(relocating) allocator for pixmaps (at least for pixel data;
housekeeping structures don't really matter).
--
Glynn Clements <[EMAIL PROTECTED]>
_
this usage mode the memory
> asigned to X grows monotonically?
No. Most long-lived applications have memory "usage" which grows
monotonically, for the reasons outlined above. I put "usage" in quotes
because they won't necessarily be *
ly need to know the PID, but just want to be able
to distinguish one client from another, you can identify the client
from the Window's XID, e.g. using XResQueryClients().
--
Glynn Clements <[EMAIL PROTECTED]>
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
is a driver
for fbdev.
--
Glynn Clements <[EMAIL PROTECTED]>
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
C standard:
so that the compiler could optimise memory access as it saw fit, while
providing an opt-out for the cases where "intermediate" values are
significant (signals, interrupts, memory-mapped I/O, threads, etc).
--
Glynn Clements <[EMAIL PROTECTED]>
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
the desktop environment.
If you move between displays, any other clients which were on the
previous display will simply vanish. Even if identical programs are
running on the new display, it isn't likely to be feasible (especially
at the protocol or Xlib levels) to simply esta
be in use on the new
server, Atoms will have different numbers, etc.
--
Glynn Clements <[EMAIL PROTECTED]>
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
mation.
Also, bear in mind that a lot of software simply ignores the ICCCM.
The handling of Alt/Meta by certain GUI toolkits is a prime example.
--
Glynn Clements <[EMAIL PROTECTED]>
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
de
...
struct _XDisplay *priv;
...
priv = (struct _XDisplay *) dpy;
printf("self: %08x %08x\n", priv->resource_base, priv->resource_mask);
This will allow you to determine whether a particular XID refers to a
resource which the itself cl
sort to Alt-SysRq-K.
Unfortunately, that tends to leave the video card in a state where
consoles don't work, but I can at least use Ctrl-Alt-Del to trigger a
clean reboot.
--
Glynn Clements <[EMAIL PROTECTED]>
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
some effect related to whatever the
cursor is over, while the cross indicates "there's nothing here", i.e.
clicks will be ignored.
--
Glynn Clements <[EMAIL PROTECTED]>
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Due the fact that I'am not uptodate, what is the 'best' solution for the
> Mainstream cards at that time?
First, support Xv. Support for other rendering mechanisms depends upon
how important you consider fallbacks to be.
--
Glynn Clements <[EMAIL PROTECTED]>
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
it for the
> game?
If you request a direct rendering context, and the server supports it,
you should get it. Whether or not the server also accelerates indirect
rendering (i.e. AIGLX) isn't relevant.
--
Glynn Clements <[EMAIL PROTECTED]>
_
90 matches
Mail list logo
