WineConsole & quick-edit mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



as reported by Sylvain, the wineconsole curses backend wasn't respecting the quick-edit configuration option. we do know.
however, this flag has to be turned on if one wants to be able to select and copy data from the console (otherwise, all mouse events will be converted to console mouse events and passed to the application)
there's no way in current curses backend to change this setting. you need either to use the user backend or use a text editor for registry editing

A+
--
Eric Pouech
Name:          wc_cqe
ChangeLog:     in curses backed, apply the quick-edit directive from registry
License:       X11
GenDate:       2003/03/01 08:11:06 UTC
ModifiedFiles: programs/wineconsole/curses.c
AddedFiles:    
===================================================================
RCS file: /home/cvs/cvsroot/wine/wine/programs/wineconsole/curses.c,v
retrieving revision 1.5
diff -u -u -r1.5 curses.c
--- programs/wineconsole/curses.c	14 Feb 2003 19:23:36 -0000	1.5
+++ programs/wineconsole/curses.c	1 Mar 2003 08:07:49 -0000
@@ -755,16 +755,24 @@
     intrflush(stdscr, FALSE);
     nodelay(stdscr, TRUE);
     keypad(stdscr, TRUE);
-    mousemask(BUTTON1_PRESSED|BUTTON1_RELEASED|
-              BUTTON2_PRESSED|BUTTON2_RELEASED|
-              BUTTON3_PRESSED|BUTTON3_RELEASED|
-              BUTTON_SHIFT|BUTTON_CTRL|BUTTON_ALT|REPORT_MOUSE_POSITION,
-              &PRIVATE(data)->initial_mouse_mask);
-    /* no click event generation... we just need button up/down events
-     * it doesn't seem that mouseinterval(-1) behaves as documented... 
-     * 0 seems to be better value to disable click event generation
-     */
-    mouseinterval(0);
+    if (data->curcfg.quick_edit)
+    {
+        mousemask(BUTTON1_PRESSED|BUTTON1_RELEASED|
+                  BUTTON2_PRESSED|BUTTON2_RELEASED|
+                  BUTTON3_PRESSED|BUTTON3_RELEASED|
+                  BUTTON_SHIFT|BUTTON_CTRL|BUTTON_ALT|REPORT_MOUSE_POSITION,
+                  &PRIVATE(data)->initial_mouse_mask);
+        /* no click event generation... we just need button up/down events
+         * it doesn't seem that mouseinterval(-1) behaves as documented... 
+         * 0 seems to be better value to disable click event generation
+         */
+        mouseinterval(0);
+    }
+    else
+    {
+        mousemask(0, &PRIVATE(data)->initial_mouse_mask);
+    }
+
     return TRUE;
 }
 

[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux