tcl/tk, itcl, BLT - native X for TkDesk 2.0
Hi, I'm an old tkdesk fan. (shameless plug) I think it's power & flexibility would be a great addition to the cygwin environment on windows. I've been using it on cywin/X for over a week now. It's like coming home after a long voyage. I compiled & ran tkdesk with the cygwin tcl/tk, but there are differences between the X and windows version, some subtle and some not so subtle. Mostly, the X registry is implemented differently, so a tk app that depends on defaults in the registry for it's behavior would need to be redone. With a tip from http://wiki.tcl.tk/ I compiled tcl/tk, itcl and BLT as static libs for an undefined unix system. Tkdesk compiles and runs with exactly the same look & feel as native Unix. Even the same bugs. I'd like to digress here and say the Xlib compatibility, and cygwin API combo is one of the most amazing feats of compatibility I've ever witnessed. I'm still in awe. I checked back thru 2004 and all I can find are discussions about previous discussions about an X-based tcl/tk cohabiting the environment with the cygwin's tcl/tk windows version and not interfering with insight. Here's my quandry. My goal was to get tkdesk 2.0 working well in the cygwin environment, but that goal now has a certain dependency on resolving the issues surrounding X-tcl/tk and Win-tcl/tk. Would it be acceptable to the community to contribute a statically compiled tkdesk that included everything it needed in it's own directory? I've been doing this on linux for years now to keep an older version of tkdesk running using an outdated tcl/tk release. If not, I never thought of being a maintainer for something like tcl/tk and friends, and wouldn't even know where to start. It really is almost trivially easy to compile these apps as static native X unix apps, but I have no idea what kind of long term responsibilities that involves or what additional effort will be required to make dll's. So I'm not volunteering in this note. But if someone was to start maintaining an X tcl/tk, what would be an acceptable naming convention? Would static be OK? Is it going to be sufficient to change paths to find the X version before the windows version? Memory usage aside, there are some benefits derived by not searching for a shared dll. Is non-interference with insight the only issue of interaction with an X tcl/tk? There are a lot of X based tcl/tk applications that could be ported over without change if the X based tcl/tk existed. It just seems a waste to ignore that. Regards, Doug
RE: cygwin-xfree Digest - How do I change colours in Xterm etc.
On Wed, 29 Jun 2005, Baksik, Frederick (NM75) wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > > [EMAIL PROTECTED] Sent: Wednesday, June 29, 2005 1:23 PM To: cygwin-xfree@cygwin.com Subject: Re: cygwin-xfree Digest - How do I change colours in Xterm etc. Thanks. That works in .Xdefaults. I must have been doing something wrong. Even though the colours > are right I get strange messages when I open a new xterm (typing "xterm&" or "xterm") though. Like > this: perhaps your .Xdefaults has cr/lf line-endings rather than lf-endings. " is not defineding: Color name "black " to type Booleanonvert string "false " to type Intot convert string "10 " to type Booleanonvert string "true " is not definedame "green4 " is not definedame "#00E000 - Liam. I get these same errors if the .Xdefaults file happens to be in DOS ( LF/CR ) format and not Unix ( LF ) format. - Original Message: Hi, Here are the settings I've used in .Xdefaults: XTerm*background: black XTerm*foreground: orchid3 XTerm*internalBorder: 10 !This is for fixing the backspace not to do ^H but ^? XTerm.*.backarrowKey: false !This is for double clicking XTerm*charClass: 33:48,35:48,37:48,43:48,45-47:48,64:48,95:48,126:48 XTerm*cursorBlink: true XTerm*cursorColor: green4 XTerm*pointerColor: green4 !The default blue is too dark on my monitor XTerm*color4: blue1 _ eircom broadband is now up to four times faster than before. Phone 1850 73 00 73 or visit http://home.eircom.net/broadbandoffer -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
RE: cygwin-xfree Digest - How do I change colours in Xterm etc.
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > > [EMAIL PROTECTED] > Sent: Wednesday, June 29, 2005 1:23 PM > To: cygwin-xfree@cygwin.com > Subject: Re: cygwin-xfree Digest - How do I change colours in Xterm etc. > > > Thanks. That works in .Xdefaults. I must have been doing something wrong. Even though the colours > are right I get strange messages when I open a new xterm (typing "xterm&" or "xterm") though. Like > this: > > " is not defineding: Color name "black > " to type Booleanonvert string "false > " to type Intot convert string "10 > " to type Booleanonvert string "true > " is not definedame "green4 > " is not definedame "#00E000 > > - Liam. I get these same errors if the .Xdefaults file happens to be in DOS ( LF/CR ) format and not Unix ( LF ) format. > - Original Message: > > Hi, Here are the settings I've used in .Xdefaults: > XTerm*background: black > XTerm*foreground: orchid3 > XTerm*internalBorder: 10 > > !This is for fixing the backspace not to do ^H but ^? > XTerm.*.backarrowKey: false > > !This is for double clicking > XTerm*charClass: 33:48,35:48,37:48,43:48,45-47:48,64:48,95:48,126:48 > > XTerm*cursorBlink: true > XTerm*cursorColor: green4 > XTerm*pointerColor: green4 > > !The default blue is too dark on my monitor > XTerm*color4: blue1 > > > _ > eircom broadband is now up to four times faster than before. > Phone 1850 73 00 73 or visit http://home.eircom.net/broadbandoffer
Re: cygwin-xfree Digest - How do I change colours in Xterm etc.
Thanks. That works in .Xdefaults. I must have been doing something wrong. Even though the colours are right I get strange messages when I open a new xterm (typing "xterm&" or "xterm") though. Like this: " is not defineding: Color name "black " to type Booleanonvert string "false " to type Intot convert string "10 " to type Booleanonvert string "true " is not definedame "green4 " is not definedame "#00E000 - Liam. - Original Message: Hi, Here are the settings I've used in .Xdefaults: XTerm*background: black XTerm*foreground: orchid3 XTerm*internalBorder: 10 !This is for fixing the backspace not to do ^H but ^? XTerm.*.backarrowKey: false !This is for double clicking XTerm*charClass: 33:48,35:48,37:48,43:48,45-47:48,64:48,95:48,126:48 XTerm*cursorBlink: true XTerm*cursorColor: green4 XTerm*pointerColor: green4 !The default blue is too dark on my monitor XTerm*color4: blue1 _ eircom broadband is now up to four times faster than before. Phone 1850 73 00 73 or visit http://home.eircom.net/broadbandoffer
RE: Cygwin x windows working fine for 5 of our Solaris 2.8 boxes, but can't get CDE login screen up for one other box - can anyone help
Griffey Matthew wrote: > <> > > Hi, > > I am getting the attached log file produced in the Cygwin/tmp > directory on my PC when i try to run x against one of our > Solaris 2.8 boxes - although it > can connect fine to the other similar Solaris boxes. It opens a > window but doesn't get as far as the login box - just has a black and > white fuzz on the screen. > > Any ideas please? > > Many Thanks > Matt Griffey. did you give the solaris box in question permission to connect to the cygwin xserver? reid
Re: Cygwin x windows working fine for 5 of our Solaris 2.8 boxes, but can't get CDE login screen up for one other box - can anyone help
On Wed, 29 Jun 2005, Griffey Matthew wrote: > <> > > Hi, > > I am getting the attached log file produced in the Cygwin/tmp directory on > my PC when i try to run x against one of our Solaris 2.8 boxes - although it > can connect fine to the other similar Solaris boxes. It opens a window but > doesn't get as far as the login box - just has a black and white fuzz on the > screen. http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-xdmcp-no-valid-address http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-audit-client-rejected http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-firewall If this does not help you, I'm back tomorrow. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Cygwin x windows working fine for 5 of our Solaris 2.8 boxes, but can't get CDE login screen up for one other box - can anyone help
<> Hi, I am getting the attached log file produced in the Cygwin/tmp directory on my PC when i try to run x against one of our Solaris 2.8 boxes - although it can connect fine to the other similar Solaris boxes. It opens a window but doesn't get as far as the login box - just has a black and white fuzz on the screen. Any ideas please? Many Thanks Matt Griffey. XWin.log Description: Binary data
Re: Error when starting Cygwin on XP
Gert Kruger wrote: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.2.0-2 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: X :0 -multiwindow -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 800 h 600 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winCheckDisplayNumber - Cygwin/X is already running on display 0 Fatal server error: InitOutput - Duplicate invocation on display number: 0. Exiting. winDeinitMultiWindowWM - Noting shutdown in progress Please find our disclaimer at http://www.ukzn.ac.za/disclaimer <<<>>> http://x.cygwin.com/docs/faq/cygwin-x-faq.html#errors
Error when starting Cygwin on XP
Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.2.0-2 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: X :0 -multiwindow -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 800 h 600 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winCheckDisplayNumber - Cygwin/X is already running on display 0 Fatal server error: InitOutput - Duplicate invocation on display number: 0. Exiting. winDeinitMultiWindowWM - Noting shutdown in progress Please find our disclaimer at http://www.ukzn.ac.za/disclaimer <<<>>>
Re: Xfree covers "always on top" taskbar
On Wed, 29 Jun 2005, Tobias Polzin wrote: > Hi, > > I configured my win-taskbar to be "always on top" and other windows respect > this, but any Xfree window (e.g. an xterm) can be put above the taskbar, > which is quite annoying. Even more strange: the taskbar will hide if a Cygwin/X window has the focus. and other windows which were behind the taskbar before are now visible too. I'll have to take a closer look. Maybe this was once added as a feature to make areas visible which were hidden otherwise. > By the way: Is there a bug-tracking database for Cygwin-Xfree? If not, > wouldn´t it be good to have one? You can add bugs to https://bugs.freedesktop.org/enter_bug.cgi?product=xorg Component is DDX/cygwin and assign the bug to ago at freedesktop dot org. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Xfree covers "always on top" taskbar
Hi, I configured my win-taskbar to be "always on top" and other windows respect this, but any Xfree window (e.g. an xterm) can be put above the taskbar, which is quite annoying. I start XWin with: XWin -dpi 92 -multiwindow -clipboard -multiplemonitors -xkbvariant nodeadkeys -ac The "Maximize" Button works correctly, in the sense that it leave space for the taskbar. By the way: Is there a bug-tracking database for Cygwin-Xfree? If not, wouldn´t it be good to have one? Regards, Tobias -- 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail +++ GMX - die erste Adresse für Mail, Message, More +++
Re: Problems with ALT_GR and minimized multiwindow xterm
On Wed, 29 Jun 2005, Dan Bruhn wrote: > Hello Alexander > > Did you find any solution or workaround for this problem? Not yet. I was able to reproduce it at work, but not in a debugger. I hope I get a bit further after I've finished a test this week. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Problems with ALT_GR and minimized multiwindow xterm
Hello Alexander Did you find any solution or workaround for this problem? /Regards Dan On 09/06/05 14:16 +0200, Alexander Gottwald wrote: > On Thu, 9 Jun 2005, Dan Bruhn wrote: > > > I forgot to mention that you need to change Windows keyboard layout under > > regional settings for the problem to apear. Using "-kxblayout" se is not > > enough. > > > > The easiest way is to just add the swedish layout and switch to that with > > the language bar while starting the cygwin session. That way you don't have > > to have se layout for you other sessions. > > I could reproduce it with the installed german layout too. > > I does however seem to be related to something else too. I tried > with a separatly started server used for debugging and could not > reproduce this (latest CVS code, compiled for mingw) but I'm quite > I saw this too some time ago. Anyway, since I now can reproduce this > much more easily the chances are good I can find a solution. > > bye > ago > -- > [EMAIL PROTECTED] > http://www.gotti.org ICQ: 126018723
