Hello,
Dave, is there some reason for having gpm code inside scr_real? It
seems to me that interactions with the actual screen reader basically
always pose questions. At least, the attached patch should probably
be applied to avoid getting the hightlight and getpointer support from
it, because it does not make sense in the atspi2 case at least (but I
actually wonder in which case it may make sense).
Samuel
diff --git a/Drivers/Screen/AtSpi2/screen.c b/Drivers/Screen/AtSpi2/screen.c
index 6dccc21..ade35c3 100644
--- a/Drivers/Screen/AtSpi2/screen.c
+++ b/Drivers/Screen/AtSpi2/screen.c
@@ -1281,6 +1281,16 @@ insertKey_AtSpi2Screen (ScreenKey key) {
}
}
+static int
+highlightRegion_AtSpi2Screen (int left, int right, int top, int bottom) {
+ return 0;
+}
+
+static int
+getPointer_AtSpi2Screen (int *column, int *row) {
+ return 0;
+}
+
static void
scr_initialize (MainScreen *main) {
initializeRealScreen(main);
@@ -1292,6 +1302,8 @@ scr_initialize (MainScreen *main) {
main->base.selectVirtualTerminal = selectVirtualTerminal_AtSpi2Screen;
main->base.switchVirtualTerminal = switchVirtualTerminal_AtSpi2Screen;
main->base.currentVirtualTerminal = currentVirtualTerminal_AtSpi2Screen;
+ main->base.highlightRegion = highlightRegion_AtSpi2Screen;
+ main->base.getPointer = getPointer_AtSpi2Screen;
main->processParameters = processParameters_AtSpi2Screen;
main->construct = construct_AtSpi2Screen;
main->destruct = destruct_AtSpi2Screen;
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: [email protected]
For general information, go to: http://mielke.cc/mailman/listinfo/brltty
