![]() |
|
possible bug: dialogues do something weird with screen readers |
Michael Taboada
Member #14,161
March 2012
|
Hi, |
Michael Faerber
Member #4,800
July 2004
![]() |
With which dialogues does that happen? File dialogues or message boxes? Can you reproduce this behaviour? Can you give a minimal code sample? -- |
Michael Taboada
Member #14,161
March 2012
|
Hi, #include <allegro5/allegro.h> int main(int argc, char **argv) { Also one other thing I noticed is that when you alt tab back into the window, it still won't let you read the dialog with a standard "read window:" command in the screen reader until you focus a button like the yes/no button by tabbing. If you try, again it simply reads the task bar. However, when there's only an ok button, it's impossible to tab to the ok button because (I'm guessing) the window says you can't tab to something when there's only one button in the window. Perhaps there's a way to set focus to a button as well or something -- this is all speculation, of course. |
Peter Wang
Member #23
April 2000
|
Need some help from someone who knows Win32. We call MessageBoxW to open the message box. When we give the window handle of the display to MessageBoxW, the new window inherits(?) the window proc of the normal Allegro window. For some reason, due to the way the window proc handles the messages, the message box doesn't gain focus when it is created. Does that make sense? I think what we want to do is create the message box with the default window proc.
|
|