Re: Cygwin Tk for X?
Harold L Hunt II huntharo at msu dot edu wrote: Jeffrey C Honig wrote: Is it just because no-one has taken the time to build it? Yes, that is sort of it. In other words, people are open to the idea of adding an X11 version of Tk, but it needs to be done in a way that allows both the X11 and Win32 versions to be installed at the same time. This sort of splitting, renaming, and script foo will take about 60 hours. So, it isn't just that people are lazy, it is that it will take a significant amount of time to complete all of the tasks, test it, and fix errors in the packaging scheme. I've thought about doing this at times, but I haven't got time for it at the moment. I do not have that kind of time either. Is it a project we can outline and have people work on a bit at a time? Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml
Cygwin Tk for X?
I'm curious why the only Tk for Cygwin opens Windows windows, why isn't there one that opens X11 windows? I'd like to be able to use send between apps running other hosts. Is it just because no-one has taken the time to build it? Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml
Re: How to get my auto repeat back?
-25 has fixed autorepeat for me. Thanks to everyone! Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml
Re: How to get my auto repeat back?
You got this version: http://cygwin.com/ml/cygwin-xfree-announce/2003-11/msg6.html If so, remove all flags that you have added (e.g. -kb, +kb, etc.) and stop using your config file if you were not using it before. I think you should be back to normal. Already have it. I've removed all keyboard related options. And I have never installed a config file. Still no auto-repeat. :-( My arguments to Xwin are: -clipboard -fullscreen -emulate3buttons -nowinkill -unixkill -engine 1 Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml
How to get my auto repeat back?
As happened to many people, the recent changes to the server disabled the windows autorepeat and left it up to X. I'm using ``fullscreen'' mode with ``-engine 1'', no XF86Config-4 file and am unable to get autorepeat to work. I tried the ``+kb'' argument to Xwin, with and w/o that ``xset r rate 200 40'' says that there is not an extension present for handling rate. I really miss auto-repeat. How can I find it again? Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml
Tight loop in Xwin startup under Win2k
I'm using Windows 2000 on a Dell C-600 laptop. After upgrading from 1.3 to 1.5 I've stared having my X startup go into a tight loop. This loop is so tight that I can not get the attention of the task manager or really do anything else except power-cycle the system. I've tried running a Cygwin bash shell w/o X and can not get any response out of that either. I can exit Xwin, but whatever is looping keep running. I'm using a derivative of the .xinitrc that I use on Linux and BSD which starts fvwm2 a xterms with tcshs and an emacs and a bunch of programs to figure out what to start and where. I've pretty much disabled starting of any remote programs. Anyone have any ideas here? Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml
Re: Tight loop in Xwin startup under Win2k
Jeffrey C Honig [EMAIL PROTECTED] wrote: I'm using Windows 2000 on a Dell C-600 laptop. After upgrading from 1.3 to 1.5 I've stared having my X startup go into a tight loop. This loop is so tight that I can not get the attention of the task manager or really do anything else except power-cycle the system. I've tried running a Cygwin bash shell w/o X and can not get any response out of that either. I guess I need to clarify. If I start a Cygwin bash shell and run top to see what is going on, it hangs when I start Xwin. The loop happens about 80% of the time. I'm not sure if it is Xfree86 related or not. Considering that I can kill Xwin (CTL-ALT-Backspace, or right clicking the system tray icon) and the problem does not clear up it is probably more of a cygwin issue than an xfree issue. I plan to post there also. As to why I use .xinitrc and not startxwin.bat. I'm sharing my configuration with multiple Unix machines. It's a bunch easier to copy files around than try to do the same thing in both a .xinitrc and a DOS BAT file. Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml
Re: XFree86 goes into stasis when NetMeeting is running
Using -engine 1 solves my problem with NetMeeting. Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml
Re: XFree86 goes into stasis when NetMeeting is running
Try adding -engine 1 to the XWin command line which should use GDI calls instead of DirectX calls to draw. NetMeeting probably grabs the surface and doesn't release it until you quit. I'll try it. What are the pros and cons of using GDI instead of DirectX? Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml
xwinclip dies with select failure
I have found that xwinclip dies if I try to put it into the background:
msp-arjuno 398: xwinclip
UnicodeSupport - Windows NT/2000/XP
Suspended
msp-arjuno 399: bg
[1]xwinclip
Call to select () failed: -1. Bailing.
The most likely reason is that the EINTR return from select() is not
being ignored. This diff should fix it, but I do not have a development
environment loaded:
--- xwinclip.c.~1~ 2003-01-12 20:27:22.0 -0500
+++ xwinclip.c 2003-03-23 16:26:39.0 -0500
@@ -439,7 +439,10 @@
NULL); /* No timeout */
if (iReturn = 0)
{
- printf (Call to select () failed: %d. Bailing.\n, iReturn);
+ if (errno == EINTR)
+ continue;
+ fprintf(stderr, Call to select () failed: %s. Bailing.\n,
+ strerror(errno));
break;
}
Thanks.
Jeff
Re: xwinclip dies with select failure
Most people are using the -clipboard command-line parameter for XWin.exe now... which provides the functionality of xwinclip.exe running in a seperate thread in XWin.exe. I don't know that I will ever make any new releases of the stand-alone xwinclip.exe. D'oh! I guess I didn't see that feature come through. Works great! Thanks. Jeff
