Our accessibility QA guys have tested these changes and find that they
do not impact the accessibility of gnome-terminal.
My reading of the vte code was that these signals were being emitted too
often. The signal will now be emitted once for every time
vte_terminal_process_incoming rather than at
=
g_malloc(priv-snapshot_text-len + 1);
273 memcpy(*old,
274 priv-snapshot_text-str,
275 priv-snapshot_text-len);
Padraig O'Briain wrote:
I have looked at profile data when
I have looked a bit closer and I see that the function
vte_terminal_accessible_text_modified would be called over 3000 times a
second if it was not doing so much work. Need to figure out why.
Padraig
On Wed, 2005-11-23 at 09:23 +, Padraig O'Briain wrote:
It looks to me that display_timeout
On Wed, 2005-11-23 at 07:33 -0700, Elijah Newren wrote:
On 11/23/05, Padraig O'Briain [EMAIL PROTECTED] wrote:
The problem seems to be that the function vte_terminal_process_incoming
causes the text-inserted signal to be emitted for what seems like
every character.
The attached patch
I have looked at profile data when accessibility is enabled and most of
the time is spent in
vte_terminal_accessible_update_private_data_if_needed.
I need to apply the patch to replace g_return_if_fail calls with
g_assert calls and see what improvement that makes.
Padraig
On Tue, 2005-11-22 at
John Rice wrote:
Lorenzo - thanks for the pointer.
Padraig Obriain had a look into using mcpp on Solaris, but in his
digging he trussed xrdb and found that on Solaris 10 its not exec'ing
the compiler to do the preprocessing. Someone appears to have already
hacked up a more light weight
