Re: Updated: XFree86-xserv-4.3.0-22

Re: Updated: XFree86-xserv-4.3.0-22

[=?unknown-8bit?Q?Ga=EBl?= Gueguen]

Alexander Gottwald wrote:

> We were previously using two auto-repeat schemes at the same time:
> 
> 1) xkb
> 
> 2) Win32's auto repeat layer
> 
> Convince me why it is good to have two layers handling auto repeat by 
> default and I will accede to your request.

Not sure it will convince anybody, just my point of view.
I'm using Cygwin/XFree to connect to some HP-UX and AIX boxes, and I 
can't use xkb because of this CDE/AltGr/whatever problem. (If I use xkb, 
I don't have access to |, @, etc...)
So I launch X via "X -kb" and then load my own .xmodmap.
This was working perfectly, but without Win32 autorepeat nor xkb 
autorepeat, I have no autorepeat at all :-(
My suggestion: is it possible to enable Win32 autorepeat only if X 
is launched with the -kb switch ?

Thanks for the very good job you all do,
Gael.

Re: Updated: XFree86-xserv-4.3.0-22

[Harold L Hunt II]

Might be a good idea.

Gaël Gueguen wrote:

> Alexander Gottwald wrote:
> 
> 
>>We were previously using two auto-repeat schemes at the same time:
>>
>>1) xkb
>>
>>2) Win32's auto repeat layer
>>
>>Convince me why it is good to have two layers handling auto repeat by 
>>default and I will accede to your request.
> 
> 
> Not sure it will convince anybody, just my point of view.
> I'm using Cygwin/XFree to connect to some HP-UX and AIX boxes, and I 
> can't use xkb because of this CDE/AltGr/whatever problem. (If I use xkb, 
> I don't have access to |, @, etc...)
> So I launch X via "X -kb" and then load my own .xmodmap.
> This was working perfectly, but without Win32 autorepeat nor xkb 
> autorepeat, I have no autorepeat at all :-(
> My suggestion: is it possible to enable Win32 autorepeat only if X 
> is launched with the -kb switch ?
> 
> Thanks for the very good job you all do,
> Gael.

Re: Updated: XFree86-xserv-4.3.0-22

[Alexander Gottwald]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 512 bytes --]

On Wed, 19 Nov 2003, Harold L Hunt II wrote:

> Might be a good idea.

I've a patch ready, but no buildsystem to test it. Harold, can you
please take a look?

Changelog:
 2003-11-19  <Alexander.Gottwald@s1999.tu-chemnitz.de>

   * InitOutput.c (ddxProcessArgument): Keep track of the -kb parameter
   * winwndproc.c (winWindowProc): Only discard the windows autorepeat 
       messages if the XKB layer is not disabled.
-- 
 Alexander.Gottwald@s1999.tu-chemnitz.de 
 http://www.gotti.org           ICQ: 126018723

[-- Attachment #2: Type: TEXT/PLAIN, Size: 1480 bytes --]

Index: InitOutput.c
===================================================================
RCS file: /cvsroot/xoncygwin/xc/programs/Xserver/hw/xwin/InitOutput.c,v
retrieving revision 1.5
diff -u -r1.5 InitOutput.c
--- InitOutput.c	8 Nov 2003 20:18:59 -0000	1.5
+++ InitOutput.c	19 Nov 2003 16:31:16 -0000
@@ -1237,6 +1237,15 @@
       return 1;
     }
 
+  /*
+   * Look for the '-kb' argument
+   */
+  if (IS_OPTION ("-kb"))
+    {
+      g_cmdline.noXkbExtension = TRUE;  
+      return 0; /* Let DIX parse this again */
+    }
+
   return 0;
 }
 
Index: winwndproc.c
===================================================================
RCS file: /cvsroot/xoncygwin/xc/programs/Xserver/hw/xwin/winwndproc.c,v
retrieving revision 1.4
diff -u -r1.4 winwndproc.c
--- winwndproc.c	8 Nov 2003 20:18:59 -0000	1.4
+++ winwndproc.c	19 Nov 2003 16:31:17 -0000
@@ -905,9 +905,15 @@
       if (wParam == VK_LWIN || wParam == VK_RWIN)
 	break;
 
-      /* Discard presses generated from Windows auto-repeat */
-      if (lParam & (1<<30))
-	return 0;
+      /* 
+       * Discard presses generated from Windows auto-repeat
+       * ago: Only discard them if XKB is not disabled 
+       */
+      if (!g_winInfo.xkb.disable) 
+        {  
+          if (lParam & (1<<30))
+	    return 0;
+        }  
       
       /* Discard fake Ctrl_L presses that precede AltGR on non-US keyboards */
       if (winIsFakeCtrl_L (message, wParam, lParam))

Re: Updated: XFree86-xserv-4.3.0-22

[tulitanssi]

Hi all,

and thanks for the ideas.

Actually, I previously had problems with extraneous newlines from keyboard and somebody suggested 'xset r off', which was still there in my startup script. It didn't bother me with 4.3.0-21 but disabled the repeat with 4.3.0-22. Now I just removed xset from my startup, and repeat works OK.

Well, I still sometimes get extraneous newlines also with 4.3.0-22, but fortunately not so much.

Cheers,
Tuli

>> keyboard repeat does not work anymore with this new update. I think it worked with the
>> previous (4.3.0-21) release. Any ideas?

> The command 'xset r on' should enable auto-repeat on the
> X Window layer.  xset can set auto-repeat parameters in
> detail (please see 'man xset').



............................................................
Maksuton sähköposti aina käytössä http://luukku.com
Kuukausimaksuton MTV3 Internet-liittymä www.mtv3.fi/liittyma

Re: Updated: XFree86-xserv-4.3.0-22

[tulitanssi]

Sorry, I'm not familiar with Xinput. I have used cygwin as-is, i.e. not deliberately disabling any of the cygwin features :-)

How can I enable it?

Thanks,
Tuli

----------------
Yeah, this release discards repeats that come from Windows. It now relies on the Xinput layer to do the repeating. Are you disabling Xinput? I hope I have that terminology right... it might not be called Xinput.

Harold

tulitanssi@luukku.com wrote: 
Hi all,

keyboard repeat does not work anymore with this new update. I think it worked with the previous (4.3.0-21) release. Any ideas?

I'm using win2k.


Thanks,
Tuli


............................................................
Maksuton sähköposti aina käytössä http://luukku.com
Kuukausimaksuton MTV3 Internet-liittymä www.mtv3.fi/liittyma

Re: Updated: XFree86-xserv-4.3.0-22

[Danilo Turina]

tulitanssi@luukku.com wrote:
> Sorry, I'm not familiar with Xinput. I have used cygwin as-is, i.e. not deliberately disabling any of the cygwin features :-)
> 
> How can I enable it?

I had the same problem, then I discovered that in the custom script I 
used to start XFree, I had this parameter:

	-kb

passed to XWin.exe (i.e. I had something like:

	XWin :0 -nowinkill -unixkill -kb -screen 0 1280 1024
)

Removing the "-kb" parameter (i.e. changing to something like:

	XWin :0 -nowinkill -unixkill -screen 0 1280 1024
)

Solved the problem.

> 
> Thanks,
> Tuli
> 
> ----------------
> Yeah, this release discards repeats that come from Windows. It now relies on the Xinput layer to do the repeating. Are you disabling Xinput? I hope I have that terminology right... it might not be called Xinput.
> 
> Harold
> 
> tulitanssi@luukku.com wrote: 
> Hi all,
> 
> keyboard repeat does not work anymore with this new update. I think it worked with the previous (4.3.0-21) release. Any ideas?
> 
> I'm using win2k.
> 
> 
> Thanks,
> Tuli
> 
> 
> ............................................................
> Maksuton sähköposti aina käytössä http://luukku.com
> Kuukausimaksuton MTV3 Internet-liittymä www.mtv3.fi/liittyma
> 
> 

RE: Updated: XFree86-xserv-4.3.0-22

[tulitanssi]

Hi all,

keyboard repeat does not work anymore with this new update. I think it worked with the previous (4.3.0-21) release. Any ideas?

I'm using win2k.

Thanks,
Tuli


............................................................
Maksuton sähköposti aina käytössä http://luukku.com
Kuukausimaksuton MTV3 Internet-liittymä www.mtv3.fi/liittyma

Re: Updated: XFree86-xserv-4.3.0-22

[Harold L Hunt II]

Yeah, this release discards repeats that come from Windows.  It now 
relies on the Xinput layer to do the repeating.  Are you disabling 
Xinput?  I hope I have that terminology right... it might not be called 
Xinput.

Harold

tulitanssi@luukku.com wrote:
> Hi all,
> 
> keyboard repeat does not work anymore with this new update. I think it worked with the previous (4.3.0-21) release. Any ideas?
> 
> I'm using win2k.
> 
> Thanks,
> Tuli
> 
> 
> ............................................................
> Maksuton sähköposti aina käytössä http://luukku.com
> Kuukausimaksuton MTV3 Internet-liittymä www.mtv3.fi/liittyma
> 

Re: Updated: XFree86-xserv-4.3.0-22

[Dr. Volker Zell]

>>>>> "Harold" == Harold L Hunt, <Harold> writes:

    Harold> Yeah, this release discards repeats that come from Windows.  It now
    Harold> relies on the Xinput layer to do the repeating.  Are you disabling
    Harold> Xinput?  I hope I have that terminology right... it might not be
    Harold> called Xinput.

I see the same, how can I reenable the repeats in the Xinput layer ?

    Harold> Harold

Ciao
  Volker

Re: Updated: XFree86-xserv-4.3.0-22

[Harold L Hunt II]

Are you using the -kb or -xkb parameters?  I don't remember what the 
name of the parameter is that disables the repeats, but the above seems 
close.

Harold

Dr. Volker Zell wrote:

>>>>>>"Harold" == Harold L Hunt, <Harold> writes:
> 
> 
>     Harold> Yeah, this release discards repeats that come from Windows.  It now
>     Harold> relies on the Xinput layer to do the repeating.  Are you disabling
>     Harold> Xinput?  I hope I have that terminology right... it might not be
>     Harold> called Xinput.
> 
> I see the same, how can I reenable the repeats in the Xinput layer ?
> 
>     Harold> Harold
> 
> Ciao
>   Volker
> 

Re: Updated: XFree86-xserv-4.3.0-22

[Dr. Volker Zell]

>>>>> "Harold" == Harold L Hunt, <Harold> writes:

    Harold> Are you using the -kb or -xkb parameters?  I don't remember what the
    Harold> name of the parameter is that disables the repeats, but the above
    Harold> seems close.

No, but I found the culprit. I once downloaded a XF86Config-4 file from the
net and placed it under /etc/X11
There was an entry

 Option "AutoRepeat" "500 20"

After changing it to "200 40" woooow, it works even better as before...

    Harold> Harold

Ciao
  Volker

Re: Updated: XFree86-xserv-4.3.0-22

[Dr. Volker Zell]

>>>>> "I" == Volker Zell <Dr.> writes:

>>>>> "Harold" == Harold L Hunt, <Harold> writes:
    Harold> Are you using the -kb or -xkb parameters?  I don't remember what the
    Harold> name of the parameter is that disables the repeats, but the above
    Harold> seems close.

    I> No, but I found the culprit. I once downloaded a XF86Config-4 file from the
    I> net and placed it under /etc/X11
    I> There was an entry

    I>  Option "AutoRepeat" "500 20"

    I> After changing it to "200 40" woooow, it works even better as before...


Actually I only tried setting AutoRepeat via

 xset r rate 200 40

and this works fine.

But when setting it in /etc/X11/XF86Config-4 it gets ignored for me.
Here are the relevant entries from XF86Config-4 and from /tmp/XWin.log.
Any hints ? is this supposed to work ?

>From XF86Config-4:

Section "InputDevice"

    Identifier	"Keyboard1"
    Driver	"Keyboard"

    Option 	"XkbRules"	"xfree86"
    Option 	"XkbModel"	"pc105"
    Option 	"XkbLayout"	"de"

    Option 	"AutoRepeat"	"200 40"

EndSection


and from XWin.log:

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1024 h 768
winInitializeDefaultScreens - Returning
OsVendorInit - Creating bogus screen 0
(==) Using config file: "/etc/X11/XF86Config-4"
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (??) unknown.
(**) FontPath set to "/usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/local/share/emacs/fonts/,/dev/c/WINNT/Fonts/,/usr/local/share/fonts/"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
winDetectSupportedEngines - Windows NT/2000/XP
winDetectSupportedEngines - DirectDraw installed
winDetectSupportedEngines - Allowing PrimaryDD
winDetectSupportedEngines - DirectDraw4 installed
winDetectSupportedEngines - Returning, supported engines 0000001f
InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
winSetEngine - Using user's preference: 4
winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel
winCreateBoundingWindowWindowed - User w: 1024 h: 768
winCreateBoundingWindowWindowed - Current w: 1024 h: 768
winAdjustForAutoHide - Original WorkArea: 0 0 768 1024
winAdjustForAutoHide - Taskbar is auto hide
winAdjustForAutoHide - Found BOTTOM auto-hide taskbar
winAdjustForAutoHide - Adjusted WorkArea: 0 0 767 1024
winCreateBoundingWindowWindowed - WindowClient w 1024 h 767 r 1024 l 0 b 767 t 0
winCreateBoundingWindowWindowed -  Returning
winCreatePrimarySurfaceShadowDDNL - Creating primary surface
winCreatePrimarySurfaceShadowDDNL - Created primary surface
winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface
winAllocateFBShadowDDNL - lPitch: 4096
winAllocateFBShadowDDNL - Created shadow pitch: 4096
winAllocateFBShadowDDNL - Created shadow stride: 1024
winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32
winCreateDefColormap - Deferring to fbCreateDefColormap ()
winFinishScreenInitFB - returning
winScreenInit - returning
InitOutput - Returning.
(==) winConfigKeyboard - Layout: "00000407" (00000407) 
(==) Using preset keyboard for "German (Germany)" (407), type "4"
(**) Using keyboard "Keyboard1" as primary keyboard
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "de"
(**) XKB: layout: "de"
Rules = "xfree86" Model = "pc105" Layout = "de" Variant = "(null)" Options = "(null)"
winPointerWarpCursor - Discarding first warp: 512 383
winBlockHandler - Releasing pmServerStarted
winBlockHandler - pthread_mutex_unlock () returned

    I> Ciao
    I>   Volker

    Harold> Harold

Ciao
  Volker

Re: Updated: XFree86-xserv-4.3.0-22

[Alexander Gottwald]

On Wed, 12 Nov 2003, Dr. Volker Zell wrote:

> Actually I only tried setting AutoRepeat via
> 
>  xset r rate 200 40
> 
> and this works fine.
> 
> But when setting it in /etc/X11/XF86Config-4 it gets ignored for me.
> Here are the relevant entries from XF86Config-4 and from /tmp/XWin.log.
> Any hints ? is this supposed to work ?

No. The AutoRepeat option is not used yet. I'll change this.

bye
	ago
-- 
 Alexander.Gottwald@s1999.tu-chemnitz.de 
 http://www.gotti.org           ICQ: 126018723

Re: Updated: XFree86-xserv-4.3.0-22

[Alexander Gottwald]

Alexander Gottwald wrote:

> On Wed, 12 Nov 2003, Dr. Volker Zell wrote:

> No. The AutoRepeat option is not used yet. I'll change this.

Done.
    ago

NP: L'Âme Immortelle - 21. Februar
-- 
 Alexander.Gottwald@informatik.tu-chemnitz.de
 http://www.gotti.org           ICQ: 126018723

Re: Updated: XFree86-xserv-4.3.0-22

[Zbynek Winkler]

Alexander Gottwald wrote:

>Alexander Gottwald wrote:
>  
>
>>On Wed, 12 Nov 2003, Dr. Volker Zell wrote:
>>    
>>
>>No. The AutoRepeat option is not used yet. I'll change this.
>>    
>>
>
>Done.
>  
>
As it happens, I was completely happy with the old behavior. Now it 
defaults to something else than I have set in the win32 environment. 
Could the default be (when no config file is found) the autorepeat that 
was before the change? Thus this upgrade would hit only the users who 
really want to customise it.
Zbynek

-- 
http://zw.matfyz.cz/     http://robotika.cz/
Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic

Re: Updated: XFree86-xserv-4.3.0-22

[Harold L Hunt II]

We were previously using two auto-repeat schemes at the same time:

1) xkb

2) Win32's auto repeat layer

Convince me why it is good to have two layers handling auto repeat by 
default and I will accede to your request.

Harold

Zbynek Winkler wrote:
> Alexander Gottwald wrote:
> 
>> Alexander Gottwald wrote:
>>  
>>
>>> On Wed, 12 Nov 2003, Dr. Volker Zell wrote:
>>>   
>>> No. The AutoRepeat option is not used yet. I'll change this.
>>>   
>>
>>
>> Done.
>>  
>>
> As it happens, I was completely happy with the old behavior. Now it 
> defaults to something else than I have set in the win32 environment. 
> Could the default be (when no config file is found) the autorepeat that 
> was before the change? Thus this upgrade would hit only the users who 
> really want to customise it.
> Zbynek
> 

Re: Updated: XFree86-xserv-4.3.0-22

[Zbynek Winkler]

I am not sure I know how the system worked internaly and I would 
cetrainly make no requests in that matter. I was just trying to point 
out the user point of view. You are (probably) saying that you have 
improved the software internaly (which is always good). However this 
improvement changed the original default behavior in such a way that in 
order to get it back I am going to have to browse the net for some 
XF86Config-4 file only to set it to same value I was perfectly happy 
with before I did the upgrade. Isn't it weird? And I know this will fix 
the problem only because I happend to subscribe a week ago to this list. 
Before that I didn't even know there was such an option. Could you make 
us all happy and use the win32 default unless told otherwise instead of 
pulling one out of thin air? Does it sound reasonable? We are talking 
here only about two numbers. I don't mean to be pain in the ... but I 
really think it is more logical to do it this way. Would it break anything?

Zbynek

Harold L Hunt II wrote:

> We were previously using two auto-repeat schemes at the same time:
>
> 1) xkb
>
> 2) Win32's auto repeat layer
>
> Convince me why it is good to have two layers handling auto repeat by 
> default and I will accede to your request.
>
> Harold
>
> Zbynek Winkler wrote:
>
>> Alexander Gottwald wrote:
>>
>>> Alexander Gottwald wrote:
>>>  
>>>
>>>> On Wed, 12 Nov 2003, Dr. Volker Zell wrote:
>>>>   No. The AutoRepeat option is not used yet. I'll change this.
>>>>   
>>>
>>>
>>>
>>> Done.
>>>  
>>>
>> As it happens, I was completely happy with the old behavior. Now it 
>> defaults to something else than I have set in the win32 environment. 
>> Could the default be (when no config file is found) the autorepeat 
>> that was before the change? Thus this upgrade would hit only the 
>> users who really want to customise it.
>> Zbynek
>>


-- 
http://zw.matfyz.cz/     http://robotika.cz/
Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic

Re: Updated: XFree86-xserv-4.3.0-22

[Alexander Gottwald]

On Tue, 18 Nov 2003, Zbynek Winkler wrote:

> As it happens, I was completely happy with the old behavior. Now it 
> defaults to something else than I have set in the win32 environment. 
> Could the default be (when no config file is found) the autorepeat that 
> was before the change? Thus this upgrade would hit only the users who 
> really want to customise it.

There were two changes recently. The first switched off the win32 
autorepeat, the second added support for a AutoRepeat option in the 
configfile. 

The second may have changed default values (but I am quite sure that I've
used exactly the values which were default before). But I think you missed 
the first change which changed the old behaviour.

If this is the case I can add code to use the windows default autorepeat 
settings to configure Xwin. But this will again change the old behavior
of Xwin and some users might be unhappy with it.

bye
	ago
-- 
 Alexander.Gottwald@s1999.tu-chemnitz.de 
 http://www.gotti.org           ICQ: 126018723

Re: Updated: XFree86-xserv-4.3.0-22

[Alexander Gottwald]

On Wed, 19 Nov 2003, Alexander Gottwald wrote:

> If this is the case I can add code to use the windows default autorepeat 
> settings to configure Xwin. But this will again change the old behavior
> of Xwin and some users might be unhappy with it.

Just a note to myself: Querying the parameters with 

SystemParametersInfo and SPI_GETKEYBOARDDELAY or SPI_GETKEYBOARDSPEED

-- 
 Alexander.Gottwald@s1999.tu-chemnitz.de 
 http://www.gotti.org           ICQ: 126018723

Re: Updated: XFree86-xserv-4.3.0-22

[Jack Tanner]

Alexander Gottwald wrote:
> If this is the case I can add code to use the windows default autorepeat 
> settings to configure Xwin. But this will again change the old behavior
> of Xwin and some users might be unhappy with it.

It would be consistent with other behavior to get autorepeat settings 
from Windows, not from X settings. For example, we try to use the 
Windows language settings, right?

Since Xwin is a Windows application, there's little reason for it to 
have its own autorepeat configuration.

-JT

Re: Updated: XFree86-xserv-4.3.0-22

[Takuma Murakami]

> keyboard repeat does not work anymore with this new update. I think it worked with the previous (4.3.0-21) release. Any ideas?

The command 'xset r on' should enable auto-repeat on the
X Window layer.  xset can set auto-repeat parameters in
detail (please see 'man xset').

Of course it is better to check -kb option or
XF86Config-4 file for more sophisticated configuration.

Takuma Murakami (murakami@ipl.t.u-tokyo.ac.jp)

Updated: XFree86-xserv-4.3.0-22

[Harold L Hunt II]

Announcement
============

The XFree86-xserv-4.3.0-22 package has been updated in the Cygwin
distribution.


Links
=====

Server source, direct link:
http://www.msu.edu/~huntharo/xwin/server/xwin-20031109-1622.tar.bz2 (130
KiB)

xc/programs/Xserver/hw/xwin (all files) diff against 4.3.0-20 source code:
http://www.msu.edu/~huntharo/xwin/server/xwin-4.3.0-20-to-4.3.0-22.diff
(17 KiB)


Changes
=======

1) win.h, winkeybd.c, winmultiwindowwndproc.c, winwndproc.c - Remove
winStoreModeKeyStates () function and stop storing mode key state
within the hw/xwin layer.  Instead, query the internal X Server mode
key state, when we know that no key press/release events are pending,
and send key press/release events to get that state in sync with the
Windows mode key states.  This removes the possibility that the
hw/xwin and internal X Server mode key state vectors would get out of
sync.  This is also a general cleanup that utilizes more existing code
and removes some Cygwin-specific code.  (Takuma Murakami)

2) winwndproc.c - Catch WM_ENDSESSION message and perform clean
shutdown.  (Takuma Murakami)

3) winwndproc.c - WM_*KEYDOWN - Discard key presses generated from
Windows auto-repeat (these sorts of auto-repeats are handled by X).
(Takuma Murakami)

4) winmouse.c - Remap mouse buttons here when XFree86Server and
XINPUT are defined, since this combination of flags prevents a lower
layer from performing such remapping.  The end result is that
remapping mouse buttons works for the first time.  (Takuma
Murakami)

5) winconfig.c - Load the US keyboard layout for Japanese keyboards.
This ensures that WM_KEYUP messages are sent for the Caps Lock
key.  (Takuma Murakami, Kensuke Matsuzaki)

6) win.h, winengine.c, winmultiwindowwindow.c, winmultiwindowwm.c,
winpfbdd.c, winshaddd.c, winshadddnl.c, winshadgdi.c, winwindow.h -
Add an engine-specific function that is called after a Windows-window
is created in -multiwindow mode.  This is a start for adding
DirectDraw support to -multiwindow mode.  However, I got a little
confused here and thought that one primary surface would need to be
created per window, which is not correct.  There will be one primary
surface with a clip list that causes blits to stay within the region
of all of our visible windows.  In any case, this is a step in the
right direction.  There code is currently disabled since the engine
setting code only allows the GDI engine when -multiwindow is being
used.  (Harold L Hunt II)


-- 
Harold Hunt

To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Once you've downloaded setup.exe, run it and select "XFree86"
and then click on the appropriate field until the above announced
version number appears if it is not displayed already.

If your mirror doesn't yet have the latest version of this package after
24 hours, you can either continue to wait for that site to be updated or
you can try to find another mirror.

Please send questions or comments to the Cygwin/X mailing list at:
cygwin-xfree@cygwin.com

If you want to subscribe go to:
http://cygwin.com/ml/cygwin-xfree/

I would appreciate if you would use this mailing list rather than
emailing me directly.  This includes ideas and comments about the setup
utility or Cygwin/X in general.

If you want to make a point or ask a question the Cygwin/X mailing
list is the appropriate place.