Re: Weird X start problem
Whats your SHELL variable? Rob
Re: problems with remote display
winCreateDefColormap - Deferring to fbCreateDefColormap () winScreenInit - returning winWindowProc - WM_*KEYDOWN - Closekey hit, quitting ^ Did you hit ctrl-c or alt-f4 ? i have closed the X-server whit alt-f4
Re: [Pending Review]: XFree86-Xaw3d-1.5
--- Harold L Hunt [EMAIL PROTECTED] wrote: Nicholas, I'll post this later tonight. Prepare a release announcement to send to both the regular list and cygwin-xfree-announce. I'll let you know when it is posted so you can send the announcements in. Use messages in the archive for cygwin-xfree-announce or cygwin-announce as a template for your announcement. Harold, Fogive me for asking, but when you say regular list, do you mean [EMAIL PROTECTED] or [EMAIL PROTECTED] I'm only asking because when I post a message to [EMAIL PROTECTED], it automatically reposts my message to [EMAIL PROTECTED] Is this not the same for [EMAIL PROTECTED]? Also, wouldn't it make sense just to leverage the existing [EMAIL PROTECTED]? I don't quite understand the necessity for a separate mailing list there. Cheers, Nicholas __ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com
[ANNOUNCEMENT] [New Package]: XFree86-Xaw3d-1.5-1
Xaw3d is the 3D version of the MIT Athena widget set for X11. RELEASE NOTES: I have used patches to the SuSE Linux version of this library to fix security and UI bugs. Also, some patches have been added by me to address Cygwin building and to bring this library into the 21st Century. Therefore, most of the bugs in the Official README no longer apply. Given this is the first release, unknown bugs may still exist, so YMMV. Otherwise, enjoy! DESCRIPTION: This is Release 1.5 (14 May, 1998) of a set of 3-D widgets based on the R6.1/R6.3/R6.4 Athena Widget set. The Three-D Athena may be used as a general replacement for the Athena (Xaw) Widget set. In general, you may relink almost any Athena Widget based application with the Three-D Athena Widget set and obtain a three dimensional appearance on some of the widgets. Top and bottom shadow colors, shadow width, top and bottom shadow contrast should be self explanatory, and may be set via the usual and customary methods, e.g. app-defaults, .Xdefaults, programmatically, with editres, etc. The user data resource may be used to hang application specific data on a widget, and is only settable programmatically. You should install Xaw3d if you are using applications which incorporate the MIT Athena widget set and you'd like to incorporate a 3D look into those applications. Xaw3d includes the header files and shared libraries for developing programs that take full advantage of Xaw3d's features. You should install Xaw3d if you are going to develop applications using the Xaw3d widget set. INSTALLATION: 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. Save it and run setup, answer the questions and pick up 'XFree86-Xaw3d' from the 'XFree86' category. Cheers, Nicholas *NOTE* that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update. In the US, ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/ is a reliable high bandwidth connection, and already up to date. In Japan, use ftp://ftp.u-aizu.ac.jp/pub/gnu/gnu-win32/ . In Denmark, http://mirrors.sunsite.dk/cygwin/ is already up-to-date. If one of the above doesn't have the latest version of this package you can either wait for the site to be updated or find another mirror. Please send questions or comments to the Cygwin/XFree86 mailing list at: [EMAIL PROTECTED] If you want to subscribe go to: http://cygwin.com/lists.html. I would appreciate if you would use this mailing list rather than emailing me directly. This includes ideas and comments about the XWin server or Cygwin/XFree86 in general. If you want to make a point or ask a question the Cygwin/XFree mailing list is the appropriate place. *** CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO *** To unsubscribe to the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED]
[ITP] FreeCiv-1.12.0-1 for X (using libXaw)
The following message is copied from message wrongly sent to [EMAIL PROTECTED] Now Nicholas Wourms has ported libXaw3D so maybe I should do a 1.12.0-2 to use it... or maybe two separate binary packages are better? One for libXaw (that is default) and one for libXaw3D? I think one binary package can be sufficient. Maybe I'll do a different binary package using GTK+, as soon as it's ported, as ilbXaw version looks much worse. My first try, it uses libXaw, which is not as good-looking as GTK (but is GTK available as a cygwin package?). I've seen the client crash one time, dunno if it's normal or usual, I'll do more tests. Please notice that when the client hangs the server is still up so the play can continue opening a new client and reconnectiong. This package needs zlib as it includes support for compressed savegames and/or scenarios. This package needs libintl2 as it already includes support for many languages. http://www.lapo.it/tmp/freeciv-1.12.0-1.tar.bz2 2.32Mb http://www.lapo.it/tmp/freeciv-1.12.0-1-src.tar.bz2 3.93Mb @ freeciv sdesc: Freeciv is a multiplayer strategy game ldesc: Freeciv is a free turn-based multiplayer strategy game, in which each player becomes the leader of a civilization, fighting to obtain the ultimate goal: To become the greatest civilization. Players of Civilization II® by Microprose® should feel at home, since one aim of Freeciv is to have compatible rules. Freeciv is maintained by an international team of coders and enthusiasts, and is easily one of the most fun and addictive network games out there! category: Games XFree86 requires: cygwin XFree86-base libintl2 libiconv2 zlib curr: 1.12.0-1 -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP X.509 keys available) http://www.lapo.it (ICQ UIN: 529796)
Re: [ITP] FreeCiv-1.12.0-1 for X (using libXaw)
--- Lapo Luchini [EMAIL PROTECTED] wrote: The following message is copied from message wrongly sent to [EMAIL PROTECTED] Now Nicholas Wourms has ported libXaw3D so maybe I should do a 1.12.0-2 to use it... or maybe two separate binary packages are better? One for libXaw (that is default) and one for libXaw3D? I think one binary package can be sufficient. There is the fact that libXaw3d is less then 1/2 of MB. Just use it, as it looks much nicer then plain old libXaw. Besides, libXaw3d is shared whereas libXaw is not. Maybe I'll do a different binary package using GTK+, as soon as it's ported, as ilbXaw version looks much worse. My first try, it uses libXaw, which is not as good-looking as GTK (but is GTK available as a cygwin package?). I've seen the client crash one time, dunno if it's normal or usual, I'll do more tests. Please notice that when the client hangs the server is still up so the play can continue opening a new client and reconnectiong. This package needs zlib as it includes support for compressed savegames and/or scenarios. This package needs libintl2 as it already includes support for many languages. http://www.lapo.it/tmp/freeciv-1.12.0-1.tar.bz2 2.32Mb http://www.lapo.it/tmp/freeciv-1.12.0-1-src.tar.bz2 3.93Mb @ freeciv sdesc: Freeciv is a multiplayer strategy game ldesc: Freeciv is a free turn-based multiplayer strategy game, in which each player becomes the leader of a civilization, fighting to obtain the ultimate goal: To become the greatest civilization. Players of Civilization II® by Microprose® should feel at home, since one aim of Freeciv is to have compatible rules. Freeciv is maintained by an international team of coders and enthusiasts, and is easily one of the most fun and addictive network games out there! category: Games XFree86 requires: cygwin XFree86-base libintl2 libiconv2 zlib --You'll want to make this XFree86-xserv curr: 1.12.0-1 Looks good, but why not relink against my library? It really does look nicer. :-) Otherwise, you have my vote. Cheers, Nicholas __ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com
Re: [ITP] FreeCiv-1.12.0-1 for X (using libXaw)
There is the fact that libXaw3d is less then 1/2 of MB. Just use it, as it looks much nicer then plain old libXaw. Besides, libXaw3d is shared whereas libXaw is not. That is a REALLY good point: total file size should be roughly the same, Xaw3D included... Compiling it... -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP X.509 keys available) http://www.lapo.it (ICQ UIN: 529796)
Re: [ITP] FreeCiv-1.12.0-1 for X (using libXaw)
It is -1, the old relase I posted ni cygwin-apps -2 is on its way =) on its way was a bit optimistic.. the simple --with-xaw3d configure switch leads to some problems... things defined twice. Strange as configure detects everything correctly. /usr/X11R6/lib//libXt.a(Intrinsic.o)(.text+0x10):Intrinsic.c: multiple definition of `XtIsSubclass' /usr/X11R6/lib//libXaw3d.a(d000327.o)(.text+0x0): first defined here /usr/X11R6/lib//libXt.a(Intrinsic.o)(.text+0x714):Intrinsic.c: multiple definition of `XtRealizeWidget' /usr/X11R6/lib//libXaw3d.a(d000359.o)(.text+0x0): first defined here /usr/X11R6/lib//libXt.a(Intrinsic.o)(.text+0xa08):Intrinsic.c: multiple definition of `XtCreateWindow' (and so on) Its the configure that incorrectly includes libXt or libXaw3d that incorrectly exports them? I eat with friends this night... i'll investigate that this evening. -- Lapo 'Raist' Luchini [EMAIL PROTECTED] (PGP X.509 keys available) http://www.lapo.it (ICQ UIN: 529796)
Scrollbars patch
Jehan, Implementing a scrollbar patch is quite a bit more complex than you had initially thought. I have done a ton of work on the patch and I've got things much more complete now. I haven't got time to describe all the changes I made, but here is the patch against current CVS for you to look over: http://www.msu.edu/~huntharo/xwin/shadow/xwin-scrollbars-20020710.diff.bz2 (12 KiB) Okay, I'll give a few highlights: 1) You were passing FALSE for the fRedraw flag to SetScrollInfo in almost every call that you made to the function. This had multiple effects, including causing the thumb position to lag behind the actual scroll location, causing the thumb size to not update when you changed the page size, etc. 2) The code for WM_VSCROLL and WM_HSCROLL made about 8 sets of calls each to the same functions with slightly different parameters. I changed the code to calculate the parameters first, then make one set of calls to SetScrollInfo and ScrollWindowEx, etc. 3) I added a flag for fUserGaveHeightAndWidth to indicate that the user explicity passed a height and width for a given screen. Now when we are creating a default-sized window, with -scrollbars, we make the window as large as possible, and we shrink the underlying X visual to fit within the client area of the Windows window, without displaying the scrollbars. We show the scrollbars if/when the user ever shrinks the window. 4) When a user does specify a visual size with -scrollbars, we make the initial window as large as possible and make the visual the same size as the specified size. We show the scrollbars only if necessary (i.e. we hide them if the user passes -screen 0 800 600 -scrollbars on a 1024x768 display). 5) You no longer have to specify a width and height for a ``-screen scr_num [width height]'' parameter, which allows you to do: XWin -scrollbars -screen 0 -screen 1 This would create two full-sized screens that are resizable but that will not initially display scrollbars. 6) I added processing for WM_GETMINMAXINFO, in which we update the maximum tracking size for the window. The processing in WM_SIZING attempted to do the same thing, but in actuality it never did anything because it would never see sizes larger than the initial window size. The max tracking size is the largest size that the window is allowed to have when it is not maximized. We let the user make the window large enough to display the whole visual, even is this means that the window will be larger than the current display (just think, they can move the window around to see the part that they are interested in... I'm not going to argue with someone that wants to do that). This should allow multi-monitor users to create one huge window and stretch it across a couple of monitors, if they so desire. 7) I added a check to make sure that specified screens are numbered consecutively from 0. Screens do not have to be described in order, but there cannot be any gaps in the screen number sequence once all parameters have been processed. This prevents a user from doing ``XWin -screen 1 -scrollbars'' and then wondering why the window does not have scrollbars (or resizing support). This fixes an existing, but subtle, bug that no one seems to have stumbled across yet. 8) I added WM_MAXIMIZE to the window style when -scrollbars is passed. This allows one to maximize the Cygwin/XFree86 window. However, there are a few problems here... such as, what is a maximized 800x600 window on a 1024x768 screen? I dunno... try it, it is weird. 9) WarpCursor is messed up when you use mwm to switch to another virtual desktop inside of a Cygwin/XFree86 window that is smaller than the underlying visual and has scrollbars displayed. In this case, WarpCursor will blast the cursor to the location on the Windows display where the X location should be... but that location may actually be scrolled off the Cygwin/XFree86 window. In those cases I would like to be able to scroll the warp destination into the Cygwin/XFree86 window, then warp accordingly. Figuring out how to get the warp destination into the current scroll viewport may be difficult. Ah... that's enough for today. I'm tired. Harold
RE: cygwin1.dll 1.3.12-2 and attempt to install xfree
First: Do *not* email me directly. I am not helping you. The project is helping you. Second: Reread what I wrote you the first time. You should not be trying to run Xinstall.sh, nor should you be trying gunzip extract.exe.gz. Everything is done via Cygwin's setup.exe. It this making any sense to you? It seems like you didn't even read what I wrote the first time. Harold -Original Message- From: J. W. Ballantine [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 2:28 PM To: Harold L Hunt Subject: Re: cygwin1.dll 1.3.12-2 and attempt to install xfree Thanks. As I indicated in my note, one of the issues, and more than likely the more important one, was what causing the weird (at least for me) error messages and results that were being generated. The secondary problem was really the install. Once I resolved the Invalid argument issues the install would be a piece of cake. -- In Response to your message - Date: Wed, 10 Jul 2002 14:07:46 EDT To: James Ballantine [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] From: Harold L Hunt [EMAIL PROTECTED] Subject: Re: cygwin1.dll 1.3.12-2 and attempt to install xfree James, First: wrong mailing list. Use [EMAIL PROTECTED] I have redirected this email to the appropriate list, but please be careful to remove [EMAIL PROTECTED] if you hit ``reply to all''. Second: the Cygwin/XFree86 User's Guide is out of date. Cygwin/XFree86 is n ow entirely installed via Cygwin's setup.exe. Just rerun setup.exe, expand the XFree86 category, and select at least the XFree86-base package. Harold James Ballantine [EMAIL PROTECTED] said: Hi all, I'm trying to install xfree and I'm getting strange error messages/results before the install starts. I've downloaded and installed the most current cygwin bits (as of 7/9/02), and downloaded the must current xfree bits. When I try to gunzip extract.exe.gz I get the error message : gunzip: extract.exe.gz: Invalid arguement When I look in the dir, the gunzipped file is there, with a permission of rw--- . When I try and run the Xinstall it tells me: checking which OS you're running... uname reports 'CYGWIN_NT-5.0' version '1.3.12(0.54/3/2)' architecture 'i686'. chmod: changing permissions of 'extract': no such file or directory ./extract: not found extract doesn't work properly, renaming it to 'extract.bad' mv: preserving times for 'extract.bad' : No such file or directory mv: preserving ownership for 'extract.bad': No such file or directory mv: cannot unlink 'extract': No such file or directory mv: cannot remove 'extract': No such file or directory chmod: changing permissions of 'extract': no such file or directory ./extract: not found extract.exe doesn't work properly, renaming it to 'extract.exe.bad' The versions of 'extract and 'extract.exe' you have do not run correctly. Make sure that you have downloaded the correct binaries for your system. To find out which is correct, run 'sh ./Xinstall.sh -check'. This appears to me to be a problem with the setup of cygwin rather than a problem with xfree, which is why I've mailed to this list. I've checked the archives and either no one else has had this problem, or I've searched for the wrong key words. Any pointers to resolving this problem would be appreciated. Thanks Jim Ballantine -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Scrollbars patch
Harold L Hunt wrote: Jehan, Implementing a scrollbar patch is quite a bit more complex than you had initially thought. I have done a ton of work on the patch and I've got things much more complete now. I haven't got time to describe all the changes I made, but here is the patch against current CVS for you to look over: http://www.msu.edu/~huntharo/xwin/shadow/xwin-scrollbars-20020710.diff.bz2 (12 KiB) Okay, I'll give a few highlights: 1) You were passing FALSE for the fRedraw flag to SetScrollInfo in almost every call that you made to the function. This had multiple effects, including causing the thumb position to lag behind the actual scroll location, causing the thumb size to not update when you changed the page size, etc. Actually, I set FALSE in all cases. If not, then I forgot :). If I did that, it because on my machine it was working well that way, so I didn't want to force Windows to paint the scrollbar twice. 2) The code for WM_VSCROLL and WM_HSCROLL made about 8 sets of calls each to the same functions with slightly different parameters. I changed the code to calculate the parameters first, then make one set of calls to SetScrollInfo and ScrollWindowEx, etc. I thought about doing something like that and then I forgot. And I didn't look at the example in MSDN, I understood the message well enough and usually their examples suck if they compile at all!! (and this one isn't perfect either: they call UpdateWindow in one case but not the other, tsss!!!) 3) I added a flag for fUserGaveHeightAndWidth to indicate that the user explicity passed a height and width for a given screen. Now when we are creating a default-sized window, with -scrollbars, we make the window as large as possible, and we shrink the underlying X visual to fit within the client area of the Windows window, without displaying the scrollbars. We show the scrollbars if/when the user ever shrinks the window. 4) When a user does specify a visual size with -scrollbars, we make the initial window as large as possible and make the visual the same size as the specified size. We show the scrollbars only if necessary (i.e. we hide them if the user passes -screen 0 800 600 -scrollbars on a 1024x768 display). Hiding the scrollbars, that was already the case, wasn't it? 5) You no longer have to specify a width and height for a ``-screen scr_num [width height]'' parameter, which allows you to do: XWin -scrollbars -screen 0 -screen 1 This would create two full-sized screens that are resizable but that will not initially display scrollbars. This has nothing to do with the scrollbar, does it? But still a good feature :) 6) I added processing for WM_GETMINMAXINFO, in which we update the maximum tracking size for the window. The processing in WM_SIZING attempted to do the same thing, but in actuality it never did anything because it would never see sizes larger than the initial window size. The max tracking size is the largest size that the window is allowed to have when it is not maximized. We let the user make the window large enough to display the whole visual, even is this means that the window will be larger than the current display (just think, they can move the window around to see the part that they are interested in... I'm not going to argue with someone that wants to do that). This should allow multi-monitor users to create one huge window and stretch it across a couple of monitors, if they so desire. I didn't know this message, or actually I forgot. That's more elegant for sure. 7) I added a check to make sure that specified screens are numbered consecutively from 0. Screens do not have to be described in order, but there cannot be any gaps in the screen number sequence once all parameters have been processed. This prevents a user from doing ``XWin -screen 1 -scrollbars'' and then wondering why the window does not have scrollbars (or resizing support). This fixes an existing, but subtle, bug that no one seems to have stumbled across yet. Same comment as 5). :p 8) I added WM_MAXIMIZE to the window style when -scrollbars is passed. This allows one to maximize the Cygwin/XFree86 window. However, there are a few problems here... such as, what is a maximized 800x600 window on a 1024x768 screen? I dunno... try it, it is weird. I wanted to but I can't compile for now (missing xf86openConfigFile, xf86readConfigFile, xf86closeConfigFile at link timeand I don't have time to look at that yet) But, a wild guess, isn't ptMaxSize in WM_GETMINMAXINFO for that? (MSDN, MINMAXINFO: ptMaxSize | when a window is maximized or resized, ...) 9) WarpCursor is messed up when you use mwm to switch to another virtual desktop inside of a Cygwin/XFree86 window that is smaller than the underlying visual and has scrollbars displayed. In this case, WarpCursor will blast the cursor to the location on the Windows display where the X location should
