Hi,
hi all,
I'm working on a virtual keyboard for disabled people and I have some
problems with button press emulation.
I use XTestFakeButtonEvent to simulate button press events.
Every virtual key has a keysym and using XKeysymToKeycode I translate
virtual key Keysyms into keycodes.
On Wed, 1 Oct 2003, Kirk Haderlie wrote:
Is it possible to debug XFree86 using a dual monitor setup on a single
machine. I tried using -keeptty but this doesn't do what I would expect.
Can X be run on one monitor and a debug console on the other?
You need two video cards (as Andrew Bevitt
On Thu, Oct 02, 2003 at 10:33:58AM +0100, Dr Andrew C Aitchison wrote:
On Wed, 1 Oct 2003, Kirk Haderlie wrote:
Is it possible to debug XFree86 using a dual monitor setup on a single
machine. I tried using -keeptty but this doesn't do what I would expect.
Can X be run on one monitor and
David Dawes wrote:
On Tue, Sep 30, 2003 at 12:51:55PM -0500, Bryan W. Headley wrote:
David Dawes wrote:
On Mon, Sep 29, 2003 at 09:52:16AM -0500, Bryan W. Headley wrote:
David,
How is the work on the XF86Config parser coming? I ask because I noticed
that the 'Option Device /dev/input/event?'
On Thu, Oct 02, 2003 at 04:00:24PM +0100, Dr Andrew C Aitchison wrote:
On Thu, 2 Oct 2003, Sven Luther wrote:
BTW, how do you make it so that X doesn't blank the console on the other
head ?
My memory is going - it is a long time since I tried this, and
I'd forgotten about the that. It
Let me start by saying this is at least 5 years overdue. Glad to see David
addressing this problem.
I would like to suggest that a more aggressive approach be used that would
involve (or allow) driver changes. Using external tools to figure out
which graphics driver and input devices to use
On Thu, Oct 02, 2003 at 09:42:18AM -0500, Bryan W. Headley wrote:
My problem is, I can (easily) be drawn into a quick hack that isn't
inline with what you had in mind, both near-term and long-term. E.g.,
the above 'glob' hack.
Well, on FreeBSD, I can configure usbd to create a symlink from the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a few Millennium's and Milliennium II's I hoarded, if anyone
needs info from them, just let me know. I'd be glad to contribute to
the project in a small way if I can help.
Dr Andrew C Aitchison wrote:
|On Wed, 1 Oct 2003, Mike A. Harris wrote:
On Thu, 2 Oct 2003 11:18:11 -0700, Sottek, Matthew J wrote:
The Intel hardware used shared memory architecture and therefore
use the VideoRam option as a tunable parameter.
Is this right? The XFree86 Intel driver is able to reconfigure the system
RAM partitioning on the fly?
Color me
Sottek, Matthew J wrote:
The thing is, a unified device-configuring front-end would be better
than having every driver writer roll their own. (I mean, we can follow
Windows if we want, but why incur development risk by developing what
essentially is several versions of the same thing?)
You will never be able to create a GUI that covers everything
that is configurable across a wide variety of vendor products...
nor should you try.
Not true. Look at the limited vocabulary you presently have in
XF86Config: keywords, list-of-values, integers, bools. Bools map to
radio buttons,
Tim Roberts wrote:
On Thu, 2 Oct 2003 08:07:31 -0600 (MDT), Marc Aurele La France wrote:
On Wed, 1 Oct 2003, Marc Aurele La France wrote:
My goal is to disable this option by default in drivers which
correctly detect video memory on all supported cards, at least
for our shipped
Dr Andrew C Aitchison wrote:
On Wed, 1 Oct 2003, Mike A. Harris wrote:
If people (both other developers and end users) who _require_
the VideoRAM option in order for the proper amount of video
memory to be useable with their card, could send me privately
their: lspci -vvn or
Sottek, Matthew J wrote:
You will never be able to create a GUI that covers everything
that is configurable across a wide variety of vendor products...
nor should you try.
Not true. Look at the limited vocabulary you presently have in
XF86Config: keywords, list-of-values, integers, bools. Bools
On Thu, Oct 02, 2003 at 11:45:28AM -0700, Sottek, Matthew J wrote:
The public driver can reconfigure the amount of RAM just fine up
to 128MB (for 830M and greater)
The issue you are describing is with mode setting. The driver uses
the vbios to set modes, and the vbios has a preconfigured amount
On Thu, Oct 02, 2003 at 02:34:42PM -0500, Bryan W. Headley wrote:
Now, as to anyone who say, eww, it's Gtk, or it's Qt, or I hate
Tk, I have only one thing to say to them: Athena Widgets.
Jesus, no.
The point of this is that it's meant to be *easy* and *simple*. This means that
it should
On Thu, Oct 02, 2003 at 06:33:52AM -0700, Alex Deucher wrote:
you or christian should add this as a bug to bugzilla
(http://bugs.xfree86.org/). This is the new method for posting patches
to be accepted into cvs.
This isn't a patch to be accepted into CVS, only an idea; as it stands, it's an
dt: 03/oct
hi everybody,
i am a final year student of computer engineering, as part of
curriculam i am developing a driver of touch screen in linux. But even
On Thu, 2003-10-02 at 22:30, Keith Whitwell wrote:
Keith Whitwell wrote:
The problem seems to be that RADEONAdjustFrame() is designed to be
called from cursor handling routines that are executed outside the
Wakeup/Block handlers (perhaps this came in with SilkenMouse?) but is
being
John Dennis wrote:
[Note: this is cross posted between dri-devel and [EMAIL PROTECTED] ]
I'm trying to debug a hung X server problem with DRI using the radeon
driver. Sources are XFree86 4.3.0. This happens to be on ia64, but at
the moment I don't see anything architecture specific about the
Keith Whitwell wrote:
John Dennis wrote:
[Note: this is cross posted between dri-devel and [EMAIL PROTECTED] ]
I'm trying to debug a hung X server problem with DRI using the radeon
driver. Sources are XFree86 4.3.0. This happens to be on ia64, but at
the moment I don't see anything architecture
Keith Whitwell wrote:
I haven't deeply investigated this but two solutions spring to mind:
- Hack: Move the call to RADEONAdjustFrame() during initialization
to before the lock is grabbed.
- Better: Replace the call to RADEONAdjustFrame() during
initialization with something like:
[Note: this is cross posted between dri-devel and [EMAIL PROTECTED] ]
I'm trying to debug a hung X server problem with DRI using the radeon
driver. Sources are XFree86 4.3.0. This happens to be on ia64, but at
the moment I don't see anything architecture specific about the problem.
The symptom
23 matches
Mail list logo
