Hi Folks;
I cannot attend at 21:00 UTC today, but would gladly attend at 21:00 UTC
Friday to discuss magnification.
Will, if the meeting goes ahead on Friday please forward the concall
number(s) if possible, thanks!
Bill
Willie Walker wrote:
Thanks Luke!
The turnout yesterday was amazing,
Hi Brian, all...
My time is a bit more limited than in the past, for reviewing email,
etc. However I would be honored to be part of the Committee in a 'less
than central' role. I'd try and stay out of the way of the movers and
shakers, but would be happy to lend suggestions on request.
Peter Korn wrote:
Hi Jason,
As someone working for one of those small number of companies working on
GNOME, Mozilla, etc. accessibility, I couldn't agree with you more. I
am appreciative of the contributions IBM has made to our work - perhaps
in the future we will see a resumption of
Henrik Nilsen Omma wrote:
Ariel Rios wrote:
I am not very familiar with the ATK/AT-SPI implementations but I am
aware that these implementations are not compatible with the KDE
architecture, and a general move to DBUS has been often mentioned.
The GNOME Mobile Embedded Initative could be
Hi Udayan and Evan;
In the case you mention below, the assistive technology should check for
the presence of the Accessibility_Text interface. In most cases (i.e.
other than text entry fields, for instance), the assistive technology
should expose the contents of the Text interface to the
Hi Peter;
This is really cool, thanks a bunch. I can hardly wait to try it (sorry
I didn't get a chance this week).
Bill
Peter Parente wrote:
Accerciser is an interactive Python accessibility explorer for the
GNOME desktop. It uses AT-SPI to inspect and control widgets, allowing
you to
Hi Tomas, all;
At this point in the conversation perhaps it would be useful to mention
the existing ATK , AT-SPI, and gnome-speech API features which might be
used to handle automatic language switching.
AtkDocument and AT-SPI's Document interface include a 'documentLocale'
property, which
Jason White wrote:...
Does Orca work in an X environment that falls short of a full Gnome desktop?
Hi Jason;
orca should work OK without having a gnome session already running.
However, with recent changes to at-spi there is one caveat. Since the
'atk-bridge' no longer uses bonobo-activation
George Kraft IV wrote:
From the Orca, OO writer and terminal thread regarding the java access
bridge for GNOME...
As far as I can tell, none of the distros are providing a package of the
java access bridge for GNOME. I believe some folks are running a JVM
that they have obtained from
Hi:
java-access-bridge is not required by recent OpenOffice versions. I
believe the dependency was phased out nearly a year ago.
You will need to update your gnome-session if you have updated at-spi
from CVS HEAD or the unstable 2.17 Gnome series, however.
HTH
Bill
Jan Buchal wrote:
WvdW
Willie Walker wrote:
if I run OO writer from terminal then OO writer is not accessible. If I
run OO writer from menu then works. Where is problem?
Sounds like the GTK_MODULES environment variable might not be set, which
is what is needed to enable accessibility in OOo. The GTK_MODULES
Brian Cameron wrote:
...
Rather than supporting magnifier,
supporting themes with larger fonts or being able to simply increase
and decrease the font in the current them via hotkey is probably
better than supporting the half-screen magnifier. This is because
gdmgreeter is not designed to
David Bolter wrote:
Hi Henrik,
Henrik Nilsen Omma wrote:
Brian Cameron wrote:
I suppose it might be possible to code an on-screen keyboard directly
into GDM, but this might be more work than you think. Note GOK supports
dwell mode so that it works for users who can only
Henrik Nilsen Omma wrote:
Hi all,
Another controversial post to g-a ...
I'm currently looking at GDM accessibility and it strikes me that there
is a strong case for doing this without using AT-SPI. The themed version
currently does not work properly with the AT-SPI features and on the
Lukas Loehrer wrote:
Willie Walker writes (Re: eSpeak support in Orca -- what is the best way?):
We recently looked at making a gnome-speech driver for eSpeak, but the
main problem is that the eSpeak libraries have no facilities for sending
samples to the audio device. Instead, it relies
Hi Henrik:
Perhaps the most expedient solution would be to write a basic driver
layer for eSpeak, initially with gnome-speech wrapper interfaces, with
the intention of moving it to Speech Dispatcher later on. The basic
APIs are I hope similar enough that only a modest amount of code would
David Bolter wrote:
Hi All,
Yelp has a function called timeout_update_gok. This sounds like a
temporary stop-gap that might have been forgotten. Ideally should the
fix should be in mozilla (if not already)?
http://www.google.com/codesearch?q=file%3Ayelp+timeout_update_gokbtnG=Search+Code
if this works for you. If it does, we can make it a
permanent part of Orca.
Will
On Thu, 2006-11-09 at 09:48 +, Bill Haneman wrote:
Makes sense, with the caveat that if we remap CapsLock to achieve this
(as we probably must, to avoid the latching behavior), then the end
user will no longer
lazzaro wrote:
I use the Capslock key as a modifyer instead of insert all the time with
Jaws on laptops, and I like how it's implemented there. It appears to
work with the capslock key latched or unlatched.
CapsLock always latches, in every keyboard I've encountered (i.e. that's
why it's
Ian Pascoe wrote:
Hi all
Some thoughts that have been kind of troubling me over the past.
There have been various postings in the past about compatability , or lack
of it, with various applications. The most notable being that of Firefox
just recently. In my ignorance, should the
Luke Yelavich wrote:
...
In Windows, Jaws manages to prevent the capslock key from being latched
or unlatched. To latch/unlatch, you press shift + Capslock, or press
capslock twice quickly.
I see. I expect that would be a hazardous and/or fragile thing to
attempt on X, especially if,
www.fullmeasure.co.uk http://www.fullmeasure.co.uk
On 11/8/06, *Bill Haneman* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Ian Pascoe wrote:
Hi all
Some thoughts that have been kind of troubling me over the past.
There have been various postings
Hi David, Steve:
I think there are two aspects to Steve's question. One aspect has to do
with the exact API call syntax that the client uses to access AT-SPI,
which I think is what you are referring to. The raw C CORBA bindings
are a bit ugly (while the python ones are elegant) but don't
affects the 'ShiftLock' modifier; in effect
CapsLock ceases to be available in such a scenario.
Best regards,
Bill
Benjamin Hawkes-Lewis wrote:
On 11/8/06, Bill Haneman [EMAIL PROTECTED] wrote:
I don't see that option in the preferences dialog - you can indeed alter
the way CapsLock works
Rich Burridge wrote:
Orca doesn't care what kind of key it uses for its modifier key. It
can be anything.
Yes, but I think there is some agreement that finding a reasonable
default modifier is a worthwhile goal.
Bill
If anybody wants to try using CapsLock to see if they are more
Thanks Will. That clarifies things somewhat - we're using the term
modifier key differently. Maybe I'll contact you offlist for info on
the internal details.
So does that basically mean this whole discussion of orca on laptops is
moot, or at least addressed fully via
Samuel Thibault wrote:
Bill Haneman, le Tue 07 Nov 2006 20:15:53 +, a écrit :
AltGr is one that often gets forgotten; what about that? It does appear
to be a modifier key on all the systems I am aware of.
Yes, but it's widely used for typing
Luke Yelavich wrote:
...
Well I don't think that will be an option, as some laptops don't have a
right Alt, as far as I am aware, or I could be getting that mixed up
with the right control key.
I think you might have that confused, yes. Any non-English laptop would
need AltGr for the
Joanmarie Diggs wrote:
Hi Bill.
I am not sure I understand your point - or perhaps you are
misunderstanding me.
I suspect it's the former, but we'll see. :-)
What I am suggesting is that we specifically _avoid_ using ShiftLock
And what I am suggesting is that we
Samuel Thibault wrote:
Bill Haneman, le Thu 19 Oct 2006 00:19:04 +0100, a écrit :
Sorry, following up on my own email:
The unicode methods we use (we need these or their functional equivalents):
(easy ones first)
g_ucs4_to_utf8
g_utf8_strlen
g_utf8_offset_to_pointer
g_utf8_get_char
Hi Ian!
Ian Pascoe wrote:
Secondly, and I think this relates to Gnupernicus as opposed to Orca
although by this stage we were getting quite confused, there are lots of
spin boxes relating to the different talk rates for different controls -
could this be hidden behind an Advanced tab and
Samuel Thibault wrote:
As discussed a few months ago, gnome-braille depends on
- libgobject for contraction/language module management
- libglib for tricky stuff like unicode handling.
I don't have any objection to reworking this to remove
GObject, but it makes no sense to do that without
Sorry, following up on my own email:
The unicode methods we use (we need these or their functional equivalents):
(easy ones first)
g_ucs4_to_utf8
g_utf8_strlen
g_utf8_offset_to_pointer
g_utf8_get_char
g_utf8_next_char
g_unichar_to_utf8
(now the hard ones...)
g_unichar_break_type
Luke Yelavich wrote:
On Tue, Oct 17, 2006 at 03:21:17AM EST, Bill Haneman wrote:
Hi Folks:
I just downloaded, built, and tested this OCR engine.
It is really pretty good, and it was very easy to build. At the moment
it is a bit limited (requires TIFF format, 8 bit depth, and doesn't
Krister Ekstrom wrote:
On Mon, 2006-10-16 at 15:26 -0400, David Poehlman wrote:
there is also GOCR and Ocrad
which are open source.
I haven't tested any of those, but at least as it sounded from the
description of GOcr, it didn't support columns nor fonts. I don't know
how this
That's interesting Tomas;
Will Walker of the orca team seemed to think the problem was in Speech
Dispatcher itself (as of last week). Perhaps you would contact him
about it?
Bill
Tomas Cerha wrote:
Bill Haneman napsal(a):
The SpeechDispatcher API has some limitations which make
Hi Folks:
I just downloaded, built, and tested this OCR engine.
It is really pretty good, and it was very easy to build. At the moment
it is a bit limited (requires TIFF format, 8 bit depth, and doesn't
understand columns etc.) but the limitations don't seem to be in the
engine, only in the
The SpeechDispatcher API has some limitations which make the user
experience with orca a little less nice - as I understand it,
SpeechDispatcher doesn't support completion/progress tags within an
utterance, it can only tell you when an entire utterance is complete.
While I hear that espeak's
Hi Daniel:
Colorblindness is certainly one of the more common issues that impact
the usability of our visual interfaces. It's great to have you onboard
to help make our desktops more usable.
Enhancements that support colorblindness usually work in one of two
ways; firstly, themes are
Hi Henrik:
What he said
You and Carlos put this very well. I agree with you both that this
sounds like a great thing to add to gnome-mag.
By the way, Carlos has recently done some very nice work to enable
fullscreen magnification without requiring two X screens, so based on
this new work
Peter Parente wrote:
Hi Anna,
Perhaps starting a page on the http://live.gnome.org wiki would be a
good idea?
I'd like to see an Accessibility wiki page (pages, but at least a
starting page), particularly for projects like this. Great idea, and
past time to do it I agree.
Bill
That way,
Hi Luca:
Sorry not to have replied sooner. Thanks very much for the bug report.
The Text interface in at-spi/idl had a couple of methods added. It
looks as though one of the new interface methods wasn't added to the
java bridge wrapper set.
A simple solution should be to add a no-op
Brian Cameron wrote:
Willie:
This agenda looks good, but here are some things I'd like to see more
focus on:
+ There are many a11y components, and it seems like not many people
understand some of them. java-access-bridge, the registry daemon,
etc. It would be nice to get an overview of
Willie Walker wrote:
Hi Roland:
Glad to hear the gnome-speech thing just worked itself out without
requiring mods to gnome-speech. :-)
Dynamic language detection/switching is definitely an interesting thing
to consider adding to Orca. Right now, however, it's not really on the
core team's
Roland Zitzke wrote:
Hi Bill,
In case someone gets motivated, I think the relevant AT-SPI methods (for
determining the language/locale of UI components), and gnome-speech
methods (for determining the locales/langs which a TTS engine can speak)
are these:
See bug http://bugzilla.gnome.org/show_bug.cgi?id=78291
The short answer is it isn't possible, mostly because no one can agree
on what the keyboard navigation sequence should be. Pretty much any key
sequence will clash with some terminal-based application.
However, AtkText's selection API
Mike/All:
I think audacity uses WxWindows and not gtk+ directly. Thus stock gtk+
widgets are not being used, as I understand it, and the app is not
accessible.
regards
Bill
Mike Pedersen wrote:
Hi all,
Audacity offers some higher end features and is written in gtk, so it
should be
Hi Krister:
I don't know why you would need or want OCR for reading your email
(unless you are talking about printed mail, through your letterbox).
Thunderbird ought to be fairly good for mail reading by the time Firefox
3 ships... I think evolution is already usable with orca.
best regards
Hi Henrik:
Regarding knot-2, did you pick up the recent new release of gok? We put
in some exception handling to catch the XInput device error (from the
wacom driver, apparently) that was making gok DOA in many 6.06
installations.
best regards
Bill
Henrik Nilsen Omma wrote:
Cheryl Homiak
Hi Aurelian
Although I am not aware of any big memory leaks in gnome-mag, this
sounds like a bug. Opening a bug in gnome bugzilla would be best, then
you can post your attachments.
For finding memory leaks on Linux, I highly recommend using valgrind.
If you can run gnome-mag in valgrind it's
Hi Chris:
Zero-conf is of course the ideal, glad you've achieved it for SOK.
I am hoping that by using Xevie (via at-spi-registryd - since Xevie only
allows ONE client per session :-( and at-spi-registryd needs XEvie for
its own purposes), we can change GOK so that the default out-of-the-box
On Thu, 2006-08-17 at 11:40, Olaf Jan Schmidt wrote:
[ Bill Haneman ]
Olaf implied that there was a concern with XEvie interfering with the
core pointer.
No, I meant to say that interfering with the core pointer is the intended
behaviour for most use cases of on-screen keyboards
On Thu, 2006-08-17 at 12:05, Olaf Jan Schmidt wrote:
[ Bill Haneman ]
Actually, my point is that this affects ALL use cases of on-screen
keyboards.
I don't see why this should be the case.
Imagine a case where an on-screen keyboard is used for entering text in
another language
Hi Olaf:
On Wed, 2006-08-16 at 21:23, Olaf Jan Schmidt wrote:
[ Bill Haneman ]
That strikes me as a surprising statement. Of course it depends on what
you mean by partially sighted.
The people I am familiar with for example have light allergy. Large bright
areas on the screen hurts
It's really great to have such broad interest in Accessibility at the
Summit. I'd love to include the lab visit.
I think it should be on a separate day, however, since it could take a
lot of time and lead to rather wide-ranging discussions. Looks like our
one day is already getting pretty full.
On Thu, 2006-08-17 at 13:06, Willie Walker wrote:
Hi All:
We need to choose a day for the meeting, and develop an agenda - please log
in to the wiki and add your suggestions.
One think that I'd really like to present, and which fortunately I have
extensive materials ready for, is a
Hi Olaf!
I appreciate that kttsd can have many useful applications. I differ
with your statement below, however:
But screen readers do not help partially sighted users, users with learning
difficulties, or people who simply love to have system notifications or IRC
messages spoken.
On Wed, 2006-08-16 at 20:44, Olaf Jan Schmidt wrote:
[ Bill Haneman ]
Actually in the Windows world all of those are frequent use cases for
screen readers. In conjunction with magnification or onscreen
highlighting, screen readers can be especially useful for partially
sighted users
Hi Jude:
Don't use twm or icewm as window managers - for best results you'll want
to install and run the Gnome desktop env which includes the metacity
window manager. Starting gnome-session after startx may work for
you.
regards
Bill
On Fri, 2006-07-28 at 01:00, Jude DaShiell wrote:
So far
Manish:
Please check the recent list archives for info on firefox work. There
is also a mozilla accessibility development mailing list,
[EMAIL PROTECTED]
Here's a quotation from a recent email thread on Firefox accessibility:
Yes.
Firefox 1.5 or 2.0 will work better if you set GTK_MODULES
On Mon, 2006-07-24 at 11:21, Henrik Nilsen Omma wrote:
Bill Haneman wrote:
Hi Petra:
In the most recent versions of Gnome, assistive technology support is on
by default. The access keys idea is a reasonable one, and I think it
would greatly improve the Ubuntu accessibility experience
On Mon, 2006-07-24 at 11:58, Henrik Nilsen Omma wrote:
Bill Haneman wrote:
The new onscreen keyboard does not meet the needs of many
mobility-impaired users. GOK should be bundled with the LiveCD - once
some configuration issues are dealt with.
Do you have any specific use cases
On Mon, 2006-07-24 at 12:41, Henrik Nilsen Omma wrote:
Our plan is to go ahead with the new
technology and deal with the problems as they arise.
If by this you mean that you will ship SOK in preference to GOK in
Ubuntu, I think you are making a mistake.
Bill
On Mon, 2006-07-24 at 13:42, Henrik Nilsen Omma wrote:
Bill Haneman wrote:
On Mon, 2006-07-24 at 12:41, Henrik Nilsen Omma wrote:
Our plan is to go ahead with the new
technology and deal with the problems as they arise.
If by this you mean that you will ship SOK
installing it by default.
I disagree - we went to a lot of trouble to make GOK work as well as
possible out of the box. That said, we felt we needed to warn end-users
of potential conflicts with the core pointer, thus the warning dialogs
(easily suppressed, as I have pointed out before).
Bill
Bill
with no choice.
- Hide quoted text -
On 24/07/06, Bill Haneman [EMAIL PROTECTED] wrote:
On Mon, 2006-07-24 at 15:10, Chris Jones wrote:
...
It is possible to detect when pointer grabbing occurs so work arounds
are quite possible I should think.
Not as far as I can tell. X just doesn't allow
On Mon, 2006-07-24 at 16:38, Chris Jones wrote:
Bill Haneman said:
I don't recall ever refusing to fix any corepointer
issues, for instance - at the time you asked, there were multiple
research efforts under way to try and address them.
Maybe I put that too strongly. You stated
On Mon, 2006-07-17 at 23:59, Brett Clippingdale wrote:
Linux Screen Reader (LSR) was presented at the Linux Desktop
Developers' Conference today as part of a talk titled Accessibility
Enablement and Usability for GTK Applications.
Of particular interest to all developers is a short
characters.
Bill
On 29/06/06, Bill Haneman [EMAIL PROTECTED] wrote:
Reading the gconf values isn't a fully robust solution, since the panel
is not the only thing that might use _NET_WM_STRUTS.
It's not apathy, it just that fixing this the right way would require
new WM API.
Bill
Hi Hynek, All:
I'm not sure I agree that speech engines should not do their own audio
output. While I think you have identified some real problems with that
approach, it's not clear that the .wav file approach has a low enough
latency. If tests show that latency is not a problem, then passing
Hi Chris:
There's no good solution to the share a dock area problem. We
recommend that you don't use both top and bottom panels when running an
onscreen keyboard, for this reason.
The straightforward solution is to remove either the top or bottom
panel, and then use that edge to dock your
, and the reason you
are warned not to use GOK via the system core pointer.
Bill
On 26/06/06, Bill Haneman [EMAIL PROTECTED] wrote:
On Mon, 2006-06-26 at 22:28, Henrik Nilsen Omma wrote
Chris Jones wrote:
...
In other words I cannot spend the summer making gnome-a11y suitable
for my needs
.
On 26/06/06, Bill Haneman [EMAIL PROTECTED] wrote:
On Mon, 2006-06-26 at 22:28, Henrik Nilsen Omma wrote:
Chris Jones wrote:
...
In other words I cannot spend the summer making gnome-a11y suitable
for my needs. What I need is a temporary work
On Tue, 2006-06-27 at 10:57, Olivier BERT wrote:
I'm currently working on Speech Dispatcher backend for Orca. This
bypasses the Gnome Speech layer completely. Since Speech Dispatcher
offers several speech synthesizers not supported by Gnome Speech,
Does Speech Dispatcher support something
method must be found to solve the issue.
We'll be able to help you better if you are a little more open to our
suggestions.
Bill
Bill Haneman said:
Bear in mind that ANY onscreen keyboard that uses the mouse will fail to
work properly when used to pop up menus, etc. via keyboard navigation
Hi Chris:
The answer is, don't implement sticky keys in your keyboard. You
should be using the system-wide StickyKeys settings and feature instead
(as GOK does).
Interfering with the normal operation of the system wide setting (i.e
clashing with it as your app does), is itself an accessibility
users.
best regards
Bill
On Mon, 2006-06-26 at 13:30, Ashu Sharma wrote:
On 6/26/06, Bill Haneman [EMAIL PROTECTED] wrote:
On Mon, 2006-06-26 at 08:19, Ashu Sharma wrote:
Hi,
There was discussion about making use of ATK on KDE, rather
than
on this aspect of gnome-a11y and
fix my program so it is not an accessibility violation.
I suggest you use the system gconf keys for sticky keys.
regards
Bill
On 26/06/06, Bill Haneman [EMAIL PROTECTED] wrote:
Hi Chris:
The answer is, don't implement sticky keys in your keyboard. You
should
On Mon, 2006-06-26 at 23:05, Henrik Nilsen Omma wrote:
Bill Haneman wrote:
On Mon, 2006-06-26 at 22:28, Henrik Nilsen Omma wrote:
Bill, is it an accessibility violation to have unusable accessibility
tools?
Are you going to say something helpful?
OK, I should
On Mon, 2006-06-26 at 22:28, Henrik Nilsen Omma wrote:
Chris Jones wrote:
...
In other words I cannot spend the summer making gnome-a11y suitable
for my needs. What I need is a temporary work around until after the
SoC when I could find time to work on this aspect of gnome-a11y and
Hi Everyone:
As a few of you may already be aware, I will be on a leave of absence
for two months, starting immediately after today. In my absence, please
direct questions regarding Gnome accessibility to the
gnome-accessibility-list@gnome.org, and questions specific to
accessibility development
Hi Satyam:
In the case of gnopernicus and orca (which are the two freely available
screenreaders for our graphical platform today), as Samuel said, not
every user prefers a given screen reader. One of the things which orca
provides, which gnopernicus does not, is comprehensive
Henrik:
I think Flite uses the same file format. ( Will, please correct me if
I'm wrong). It also requires a Java JRE, are you planning to include
Java in the live CD?
BTW, in the past, Java was required for OpenOffice.org accessibility,
but that's not true of the latest version.
Bill
On
On Fri, 2006-02-24 at 13:09, Henrik Nilsen Omma wrote:
Bill Haneman wrote:
Henrik:
I think Flite uses the same file format. ( Will, please correct me if
I'm wrong).
By same format you mean the same speech files? So what is the main
benefit of F-lite, a smaller memory footprint
On Tue, 2006-02-21 at 01:21, Davyd Madeley wrote:
Quoting Dana Olson [EMAIL PROTECTED]:
Will Gnome have some method to disable Slow Keys from constantly
popping up when you hold down a key for a few seconds?
You can turn this off from the Keyboard Accessibility preferences
dialog. As you
On Sun, 2006-02-12 at 22:27, Luke Yelavich wrote:
...
Did you specify the prefix for the gnopernicus configure script? For
example ./configure --prefix=/usr? if you didn't, I have a feeling that
is why it can't find the DECtalk server but test-speech can.
Luke/all:
gnopernicus doesn't use
Hi Don:
This certainly 'smells' like a permissions problem. I believe the
Festival gnome-speech server relies on the ability to write to a
particular port, perhaps 7000? I am sure someone else on the list can
provide that detail. My guess is that root has write access to that
port, but
Hi Ginn:
Thanks for answering Naveen.
Could you make sure he knows that the solution of removing GTK_MODULES
is a temporary one? We are still telling accessibility users to set
this variable in the environment, since they need it in order to make
other important applications accessible.
Hi Jude:
Are you sure you have gnome-common installed? Looks to me as though you
are missing the 'gnome-autogen.sh' script which I believe is provided
with gnome-common. Gnome-common is a dependency of ALL gnome cvs builds.
Bill
Jude DaShiell wrote:
After having checked gnopernicus and
Hi Pedro:
While I think this has been suggested before, I think that it is a good
idea; especially if it's designed to allow sending the output to a named
pipe, serial port, or perhaps even convert to HTTP and send output that
way. It would allow more ways to debug the speech output itself.
svs drozo wrote:
Hi,
I would need to set up an environment in which two different hosts have
the two parts of at-spi, I mean, the clients in one of them and the
server in the other, is that possible? How can I do it?
Hi:
If you only want the client to be on one host, and the applications
Henrik/All:
Sorry for re-posting the URI for the sanity-test documents, I see now
that you referenced them inline. Thanks a bunch! I look forward to
reading your test scheme.
Bill
___
gnome-accessibility-list mailing list
Henrik Nilsen Omma wrote:
Hi all,
I've written up a fairly detailed review of GOK here:
https://wiki.ubuntu.com/Accessibility/Reviews/GOK
It is meant partially as an introduction to those who don't know the
program, but mainly as a critical look that can hopefully stimulate
discussion and
Hi Henrik:
The reason that StickyKeys is needed is not only because of general key
combinations like the one you mention (Control-Alt-X) but also because
of the interaction with CapsLock, etc. In general the only way to
accurately reflect what the X server will do with key events is to ask
or
go through a process of killing them one by one.
Will
On Dec 7, 2005, at 11:25 AM, Bill Haneman wrote:
Janina's right of course, just restarting the X server (or logging
out!) should have solved the problem.
It's probably a good idea to log out and back in after replacing a
core
Janina's right of course, just restarting the X server (or logging out!)
should have solved the problem.
It's probably a good idea to log out and back in after replacing a core
component like the at-spi-registry anyway.
best regards,
Bill
Janina Sajka wrote:
Luke Yelavich writes:
On
Hi Alexandra and Cody:
Ada, I think there could be some confusing aspects to your answer, or
perhaps you misunderstood Cody... you said:
2. What is teh command to make gnopernicus work with gaim messenger?
A: There isn't a special command for your problem. Installing a new version
of
remus draica wrote:...
The other problem is that currently, unless I am mistaken, gnopernicus'
braille tables are 8 bit tables, and gnopernicus always assumes Latin-1.
That's right.
Latin-2 is also 8-bit, so in theory the current gnopernicus architecture
could handle this, but it
Hi Julian:
[EMAIL PROTECTED] wrote:
Good morning, We are developing an application that allows to manipulate
the main menu of GNOME desktop using some speech commands GERvoice.
After making a study of the possible tools that allow the communication
between two applications (the GERvoice
Hi Jason, Cody:
About Java and the bridges:
As Jason mentioned before, there are two 'java access bridges'. One is
for Windows, and if you are running on Windows you will need to make
sure your screen reader supports the Java Access Bridge for Windows in
order for it to work.
If you are
1 - 100 of 152 matches
Mail list logo
