Re: Cygwin Xstart problems also
You missed the point of installing using the Unix text type which ensures that you are mounting the font directory in binary mode. The URL is http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-error-font-eof Please remember to answer to the mialinglist instead of me directly Med venlig hilsen / Regards Franz Wolfhagen James L. Olds [EMAIL PROTECTED] on 12-06-2002 21:46:39 Please respond to James L. Olds [EMAIL PROTECTED] To:Franz Wolfhagen/Denmark/IBM@IBMDK cc: Subject:Cygwin Xstart problems also I've carefully read the FAQ and I still can't get X to start on my machine. It used to, that's the weird thing (using startxwin). My log file is enclosed. I'm wondering if you can point me in the right direction. I did have to reinstall W2K and X a few weeks ago and that's when things started not working. Jim Olds
RE: [PATCH] RE: Ghost cursors (was: RE: alt-tab: client window receives tab / pressing both...)
Nevermind, I just implemented the patch that I was talking about below. However, I'm getting a strange problem where if I pass any 0 argument parameters (e.g. -lesspointer) to XWin.exe and I start with 'start XWin' on Windows 2000 then my log file only contains two lines: ddxProcessArgument () - Initializing default screens winInitializeDefaultScreens () - w 1024 h 768 If I start with 'start /B XWin' then the log is normal. I don't understand what is going on here. Maybe I've just done too many compiles and I need to restart my computer. Or maybe I need to go to bed... Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Harold Hunt Sent: Thursday, June 13, 2002 2:15 AM To: cygx Subject: RE: [PATCH] RE: Ghost cursors (was: RE: alt-tab: client window receives tab / pressing both...) Stuart, Naturally, now that I have applied the -lesspointer patch I have remembered why we switched away from hiding the Windows mouse cursor when we were inactive. The reason goes like this: 1) User has a Cygwin/XFree86 window that is away from the task bar. 2) User activates the Cygwin/XFree86 window to bring it to the top, though the window is small (say 640x480 on a 1024x768 screen) so it doesn't cover all other windows. 3) Now the user activates another application via the taskbar, say a Cygwin bash shell. This other application does not completely cover the Cygwin/XFree86 window. 4) The user moves the mouse into the Cygwin/XFree86 window, without clicking, thus hiding the mouse cursor but not activating the Cygwin/XFree86 window. 5) A popup window from another application grabs the focus and either the popup window covers the area underneath the mouse or the user moves the mouse into the popup window in such a way as to not cross the non-client area of the Cygwin/XFree86 window. 6) At this point Cygwin/XFree86 should no longer be hiding the mouse cursor because a) we aren't active and b) the mouse cursor is not over our window. However, our only way of detecting that the mouse pointer has left our window when we are inactive is to watch for the non-client area mouse messages. In this test case we never see a non-client area mouse message so we never show the cursor. I can't remember if this actually causes the Windows cursor to not be shown for the popup window or not. It may depend entirely on the version of Windows, or it may depend on the popup window, etc. All I can say is that the -lesspointer parameter is your guy's baby and I'll send people to you if they complain about -lesspointer causing their cursor to disappear over other Windows windows. :) I think the very simple method to make -lesspointer more robust is to call TrackMouseEvent with the TME_LEAVE flag when we get our first client area mouse message. Then when the mouse leaves our client area (and I'm assuming that a popup covering the area underneath the mouse qualifies as leaving the client area) we will get a WM_MOUSELEAVE message. We can simply show the Windows mouse cursor if it is being hidden at that time. Simple, eh? Harold
Status of multi-windowed server
Hi, I was wondering what the status was of using the cygwin xfree server in a multi-windowed mode (ie Opening a MS-Windows window for each X client window instead of a single window for the X desktop). I've browsed the FAQ, website, and did a few searches of the archives for this list, but couldn't find anything recent or definitive on the status of this feature. Thanks. E.
RE: Status of multi-windowed server
http://cygwin.com/ml/cygwin-xfree/2002-06/msg00086.html -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of E Sent: Thursday, June 13, 2002 3:50 AM To: [EMAIL PROTECTED] Subject: Status of multi-windowed server Hi, I was wondering what the status was of using the cygwin xfree server in a multi-windowed mode (ie Opening a MS-Windows window for each X client window instead of a single window for the X desktop). I've browsed the FAQ, website, and did a few searches of the archives for this list, but couldn't find anything recent or definitive on the status of this feature. Thanks. E.
RE: How to start messing around with creating a rootless mode...
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Stuart Adamson Sent: Thursday, 13 June 2002 10:11 PM It does seem like this might get a bit complex (we would have to hold the hwnd of each window in the windows private and use that to decide what needs updating and when). Yes, but the X infrastructure for this is excellent. I had it mostly working, but looking crap due to the decorations, and not choosing which windows to show on the taskbar terribly cluefully. Alan has various patches from me. Unfortunately, my personal time completely dried up without much warning a couple of months ago, and I haven't gotten back to that. The windows message loop will need to do some demux'ing as well. Hmm, could do, but didn't seem to need it. Rob
RE: How to start messing around with creating a rootless mode...
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Alan Hourihane Sent: Thursday, 13 June 2002 11:04 PM To: [EMAIL PROTECTED] Subject: Re: How to start messing around with creating a rootless mode... On Thu, Jun 13, 2002 at 10:57:44PM +1000, Robert Collins wrote: Yes, but the X infrastructure for this is excellent. I had it mostly working, but looking crap due to the decorations, and not choosing which windows to show on the taskbar terribly cluefully. Alan has various patches from me. Unfortunately, my personal time completely dried up without much warning a couple of months ago, and I haven't gotten back to that. Unfortunately I didn't get the full set of patches which really did the rootless modes. If you want to create a full diff - I'm sure someone will look at them. I'll see what I can do shortly. Rob
RE: How to start messing around with creating a rootless mode...
Stuart, But on the overall, I don't think it's really the way to go. Again, I don't known much about X so it may not be reasonable but what about creating a Windows window for each X window? This would allow each X App to appear in the taskbar like any Windows application. This is how eXceed works and it makes more sense to me. When I'm working in rootless mode - typically I won't be running a window manager. Right. That is exactly why I described the method of getting started as I did: because everything you do for drawing in rootless mode will still be needed when you are drawing to individual windows. Say what? That's right, you're still going to have to have a method of drawing the root window as transparent and setting the clipping region of the root window to nothing when the server looses the focus. Once you've got it so that twm can draw windows that float above the Windows desktop, then you can start worrying about holding hwnd's to individual windows, etc. Harold
RE: How to start messing around with creating a rootless mode...
Robert, I totally forgot that you had worked on a rootless mode. I'd definitely be interested in seeing the patches. Thanks, Harold
RE: [ANNOUNCEMENT] Server Test 58
Alexander, Then you can download them just by running setup.exe and point to any mirror. Then you wouldn't need a separate setup.ini file. But the mirrors are not updated instantly. The test release would need about one day to spread to the mirrors. Chris was referring to the fact that, in addition to placing the test release stand-alone files (e.g., XWin-Test58.exe.bz2) on my msu.edu site and distributing them via the sources.redhat.com network, I have also been placing a modified XFree86-xserv-4.2.0-?.tar.bz2 for Cygwin's setup.exe in cygwin/xfree/release/XFree86/XFree86-xserv/. Chris was saying that instead of telling users to point setup.exe to that other directory I could just put the test package in the normal directory and mark it as 'test' in setup.hint. Hope that clears things up, Harold
RE: [ANNOUNCEMENT] Server Test 58
--- Harold Hunt [EMAIL PROTECTED] wrote: Chris was referring to the fact that, in addition to placing the test release stand-alone files (e.g., XWin-Test58.exe.bz2) on my msu.edu site and distributing them via the sources.redhat.com network, I have also been placing a modified XFree86-xserv-4.2.0-?.tar.bz2 for Cygwin's setup.exe in cygwin/xfree/release/XFree86/XFree86-xserv/. Chris was saying that instead of telling users to point setup.exe to that other directory I could just put the test package in the normal directory and mark it as 'test' in setup.hint. Hope that clears things up, Harold, Implementing the test-release in setup.exe is real easy. Take, for example, the setup.hint of GDB: sdesc: The GNU Debugger category: Devel requires: cygwin termcap test: 20020411-1 curr: 20010428-3 That's all there is to it :-). FWIW, I think CGF's suggestion is a good one, as it makes it much easier to deal with... Cheers, Nicholas __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com
RE: How to start messing around with creating a rootless mode...
Enjoy. YMWV, as this is against somewhat old sourceforge CVS. I'm also not sure what quality I left it in :}. At a minimum it should provide food for thought. Rob -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Harold Hunt Sent: Thursday, 13 June 2002 11:53 PM To: [EMAIL PROTECTED] Subject: RE: How to start messing around with creating a rootless mode... Robert, I totally forgot that you had worked on a rootless mode. I'd definitely be interested in seeing the patches. Thanks, Harold rootless.patch.bz2 Description: Binary data
Icons show normally at 32 bpp when RENDER, LAYER, and RANDR are disabled
I just built Cygwin/XFree86 with RENDER, LAYER, and RANDR disabled. I can log on to KDE 3.0 running on a remote machine with the Windows display set to 32 bits per pixel and all the KDE icons display correctly. It looks like Waldo was right-on about the alpha channel problems. I was intially trying to disable just RENDER, but then something it layer failed to build when I disabled RENDER, so I had to disable LAYER and RANDR as well. Now we just need to find out if RENDER is having a problem with our visuals and/or pixmap formats or whether Qt or KDE has some problem that causes alpha channel rendering with our visuals and/or pixmap formats to not work. I'll try to build Cygwin/XFree86 with RENDER but without LAYER and RANDR to see if that still fixes the problem. Harold
RE: Status of multi-windowed server
At 04:01 AM 13/06/02 -0400, Harold Hunt wrote: http://cygwin.com/ml/cygwin-xfree/2002-06/msg00086.html Thanks for that. I take it from the posting and follow-up threads that it certainly isn't working out-of-the-box for what you download using setup.exe. Do you know where it is priorities on the TODO list for the project? E. P.S. Apologies to Harold for initially replying directly to him instead of the list as seems to be proper etiquette in cygwin land. I hadn't realised he had posted his response to the list as well as directly to myself.
