On Wed, Mar 11, 2009 at 10:36:49AM +0800, gordony...@viatech.com.cn wrote:
I compared Xorg 1.5.99.3 with Xorg 1.5.2, xf86CursorSetCursor seems
to cause the problem. Xf86CursorSetCursor in Xorg 1.5.99.3 adds
judgement pDev != inputInfo.pointer .
For example: Xorg 1.5.99.3
Dear Matthias:
You mean that the driver should set the output mode if necessary when the
property changes. Maybe we can call the output.mode_set() in the function
output.set_property().
Thanks for your kind help!
Best wishes,
Gordon
-Original Message-
From:
2009/3/12 gordony...@viatech.com.cn:
Dear Matthias:
You mean that the driver should set the output mode if necessary when the
property changes. Maybe we can call the output.mode_set() in the function
output.set_property().
Thanks for your kind help!
Best wishes,
Gordon
Its driver
Dear Dave,
I know what you said. But I have another question now.
If the property depends on other factor, for example, the TV output
standard is related to mode size, if mode is 640x480, the supported values of
certain property are NTSC, PAL, 720P and 1080I etc; but if mode is 720x480,
Ben Gamari wrote:
On 03/11/2009 11:28 AM, Simon Thum wrote:
lshal | grep -10 x11_driver
might be valuable.
Your wish is my command:
info.callouts.add = {'hal-acl-tool --add-device'} (string list)
...
That an awful lot. on my system, only keyboard and pointer are listed.
Try booting an
On Thu, Mar 12, 2009 at 7:37 PM, gordony...@viatech.com.cn wrote:
Dear Dave,
I know what you said. But I have another question now.
If the property depends on other factor, for example, the TV output
standard is related to mode size, if mode is 640x480, the supported values of
Ben Gamari wrote:
be too difficult to implement. Am I wrong? If not, I could potentially
take a stab at it.
Oh, I overlooked that one earlier. In the docs to ptr accel I've
described how to detect whether the server is configured to do
predictable pointer accel. The job would be defeating
Assuming I did what you asked me to correcty (see previous reply),
still no luck. It crashed on me again.
X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
Current Operating System: Linux mercury
On Thu, 2009-03-12 at 20:29 +1000, Dave Airlie wrote:
If you can only expose certain modes you might have to limit the modes
based on the current option somehow.
Properties which affect the video mode (or list of available video
modes) should be marked as 'pending properties', whose effects
Can anyone tell me about the status of the backing store support these
days? I wonder:
* Should miInitializeBackingStore() be used? I've found the comment in
mibstore.c:
There is no longer an mi implementation of backing store. This function
is only for source compatibility with old
Hi all,
I am working on an onscreen keyboard, I want it can call itself when end-user
click an editable field such as editline or text field when focus leave
editable field keyboard can hide itself. what should I do, I think X can know
If user enter an editable field, but I don't how to deal
I am working with a (somewhat new-ish) touchscreen system which supports
Multi-touch reporting, based upon an eGalix controller. Unfortunately,
this is NOT currently supported under Linux (when will these vendors wake
up to the fact that the embedded world is moving away from Windows(tm)?)
I
Hi David,
Does anybody have a good suggestion as to where this support should
go?
My intuition is that adding the reporting to the kernel and hooking it
up through the standard evdev driver would be the right way to go; evdev
already has single-touch support working fairly well. I don't
marslee_suc wrote:
I am working on an onscreen keyboard, I want it can call itself when
end-user click an editable field such as editline or text field when
focus leave editable field keyboard can hide itself. what should I do,
I think X can know If user enter an editable field, but I don't
Le 12/03/2009 17:01, marslee_suc a ??crit :
Hi all,
I am working on an onscreen keyboard, I want it can call itself when
end-user click an editable field such as editline or text field when
focus leave editable field keyboard can hide itself. what should I do, I
think X can know If user enter an
I've reported it as a bug: https://bugs.freedesktop.org/show_bug.cgi?id=20634
On Thu, Mar 12, 2009 at 10:57 AM, Jamie Jackson myspa...@gmail.com wrote:
Assuming I did what you asked me to correcty (see previous reply),
still no luck. It crashed on me again.
X.Org X Server 1.5.2
Release
Hi David,
My intuition is that adding the reporting to the kernel and hooking it
up through the standard evdev driver would be the right way to go; evdev
already has single-touch support working fairly well.
Interesting, because the touchpanels I've used were NOT recognized by
evdev at all -
Hi,
Interesting, because the touchpanels I've used were NOT recognized
by evdev at all - attempting to use them with the evdev driver
resulted in no input at all to the X server.
That's odd; perhaps they didn't get the right HAL properties added.
The N-Trig (multi) touchscreen on the
That's odd; perhaps they didn't get the right HAL properties added.
The N-Trig (multi) touchscreen on the Dell Latitude XT and HP Touchsmart
TX2 works out of the box for touch with evdev GIT HEAD. (Clicking via
screen taps requires a patch to map BTN_TOUCH to BTN_LEFT, though.)
- Chris.
I hate to say it, but it is the only usable compositing manager for me.
Compiz is close, but still is laggy in places (scrolling especially),
not to mention unstable and hard to configure. Don't even get me
started on KDE 4's KWin, because half the time, its compositing doesn't
even work,
20 matches
Mail list logo
