|
Hi Joanie.
I was using gtk 3.22 until yesterday without problems. The problem appears after I upgrade to gtk 3.24. I can confirm that if I downgrade to gtk 3.22 I have no problems. Thanks. On 1/14/19 11:59 AM, Joanmarie Diggs
wrote:
Hey José. Thanks for the confirmation. What I'm trying to figure out before doing the next unstable release is if my sad hackaround for chattiness broke anything. Since the sad hackaround isn't in Orca 3.30.1, this seems like a different issue. If memory serves me, Peter reported something similar and said the problem went away if he used Gtk+ 3.22. Is there any way for you to confirm that? Thanks for testing, doubly-so given you're busy!! --joanie On 1/14/19 8:55 AM, José Vilmar Estácio de Souza wrote:Hi Joanie. The same behavior when I use orca 3.30.1. On 1/14/19 11:28 AM, Joanmarie Diggs wrote:Hey José. Does the problem go away if you are using the stable version of Orca? --joanie On 1/13/19 5:46 PM, José Vilmar Estácio de Souza wrote:Hi Joanie and all. Sorry for the delay of an answer, I'm very busy! After upgrading from gtk3 to version 3.24.2 + 7 + g43aeb52b73-1 , I encountered a small problem in the gnome-terminal. To reproduce try the following steps using orca. master. 1. Launch gnome-terminal. 2. Press alt+tab to switch to another application. 3. Press alt+tab again to switch back to gnome-terminal. 4. Type pwd and press the enter key. In my environment orca should announce the result of pwd but orca does not shows the result. 5. Press the f10 key to activate the menu bar and press the esc key. 6. Type pwd again and press the enter key. Orca announces the result of the pwd command as expected. I can capture a debug file to demonstrate the problem if necessary. On 1/11/19 3:34 PM, Joanmarie Diggs wrote:Thanks for asking the other "usual suspects". José would be another candidate. If we can do some serious testing over the weekend, then I'll roll the release on Monday. --joanie On 1/11/19 12:07 PM, Alex ARNAUD wrote:Le 11/01/2019 à 16:30, Joanmarie Diggs a écrit :Indeed you do. But yes, the hackaround in question (mentioned on the issue you cite above) is the one most likely to break something: In order to prevent occasional chattiness, I'm ignoring a key event that we normally don't want to ignore.As I've the reverted patches on my computer right now, I can't test reliably. I'll try to migrate my GTK3 version to give you a feedback next week. Maybe asking Peter, Kyle and other Arch users that are still on GTK 3.22 on the other thread could help, I'll do that.I try to keep the unstable releases relatively stable (i.e. can be used in production environments). And without feedback, I have no confirmation that this will be the case for the to-be-rolled release.It's very much to your credit. Best regards, Alex._______________________________________________ orca-list mailing list orca-list gnome org https://mail.gnome.org/mailman/listinfo/orca-list Orca wiki: https://wiki.gnome.org/Projects/Orca Orca documentation: https://help.gnome.org/users/orca/stable/ GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html Log bugs and feature requests at http://bugzilla.gnome.org-- Assinatura Informal José Vilmar, Telefones: 21 2555-2650 e 21 98868-0859, Skype: jvilmar-- Assinatura Informal José Vilmar, Telefones: 21 2555-2650 e 21 98868-0859, Skype: jvilmar _______________________________________________ orca-list mailing list orca-list gnome org https://mail.gnome.org/mailman/listinfo/orca-list Orca wiki: https://wiki.gnome.org/Projects/Orca Orca documentation: https://help.gnome.org/users/orca/stable/ GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html Log bugs and feature requests at http://bugzilla.gnome.org --
|