Re: xwinclip - update and motif clipboard
I thank you for putting so much time into developing xwinclip. It has been a pleasure anyway. I really appreciate that you got the long-awaited setjmp lngjmp functionality implemented so that we are not killed upon X Server shutdown and restart. It's cool, I've always wanted an excuse to use them (always used c++ exceptions instead). I don't know anymore about the CLIPBOARD than what I wrote in the xwinclip source comments, which was something to the effect of, ``help! can't find CLIPBOARD documentation, how does it work?'' Well according to the specs you're implementation is right. Own clipboard manager and grab the clipboard when it's been selected, then own it again. It doesn't seem to work with Motif though. No biggy, primary works v. well. I am going to integrate your changes into a future release of xwinclip, but I cannot tell you when that will be. However, a little schedule update: snip On the other hand, shit happens, so don't expect anything extraordinary. :) Like Chris said it's suprising you can reply at all, and much appreciated. As was suggested I'm going to look at implmenting a grab the selection only when the windows clipboard has changed addition to the code. It shouldn't make a great deal of extra code but it will definitely make a minor glitch go bye bye. I'll have a look at integrating it into XWin as well. When more than one XWin window are open it doesn't work properly and if the x windows clients become integrated with windows ala eXceed then it won't work at all. Cheer's, Chris _ Send and receive Hotmail on your mobile device: http://mobile.msn.com
RE: xwinclip - update and motif clipboard
Pille Geert (bkarnd) [EMAIL PROTECTED] said: -Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: donderdag 19 september 2002 4:38 To: [EMAIL PROTECTED] Subject: Re: xwinclip - update and motif clipboard On Wed, Sep 18, 2002 at 11:32:18PM -0400, Harold Hunt wrote: Chris, I thank you for putting so much time into developing xwinclip. I really appreciate that you got the long-awaited setjmp lngjmp functionality implemented so that we are not killed upon X Server shutdown and restart. I don't know anymore about the CLIPBOARD than what I wrote in the xwinclip source comments, which was something to the effect of, ``help! can't find CLIPBOARD documentation, how does it work?'' I am going to integrate your changes into a future release of xwinclip, but I cannot tell you when that will be. However, a little schedule update: I am taking 10 credits this semester in three classes (this is not much), I am working 30-35 hours a week at an Active Server Pages (blah :( ) job (but it pays really well), and I am working 6-8 hours a week at the National Superconducting Cyclotron Laboratory at Michigan State University (where I translate old Fortran program for VMS to Tru64 UNIX and Linux). Next week my ASP job is supposed to slow down because they haven't got another contract for me to work on, so I may, in theory, have a whole week to catch up on Cygwin/XFree86. On the other hand, shit happens, so don't expect anything extraordinary. :) Actually, given the above it is sort of extraordinary that you are answering email at all... cgf 168 - 43 = 125h minus the credits to write emails. ;-) What is a credit? Geert Geert, A credit is supposed to be one hour per week of class time for college courses. Thus, ten credits ~= ten hours of class per week. The rule of thumb for how much time to spend on your classes, is three times the number of credits that it is. Thus, I should be spending 30 hours per week on my classes, in theory. So, the calculation goes something more like this: 168 - 43 - 30 - (8h per night * 7 nights per week) = 39h for eating, washing, attending weddings (two last weekend), getting to class and work, going to doctors appointments (you wouldn't believe the number of these that I've got), attending to a fiance who got her wisdom teeth out last week, visiting family, etc. ~= 2h for answering emails :) For some reason the last few weeks have just been exteremely busy. I don't know why. Harold === This email is confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. You are explicitly requested to notify the sender of this email that the intended recipient was not reached.
Re: xwinclip - update and motif clipboard
Chris Twiner [EMAIL PROTECTED] said: I thank you for putting so much time into developing xwinclip. It has been a pleasure anyway. I really appreciate that you got the long-awaited setjmp lngjmp functionality implemented so that we are not killed upon X Server shutdown and restart. It's cool, I've always wanted an excuse to use them (always used c++ exceptions instead). I don't know anymore about the CLIPBOARD than what I wrote in the xwinclip source comments, which was something to the effect of, ``help! can't find CLIPBOARD documentation, how does it work?'' Well according to the specs you're implementation is right. Own clipboard manager and grab the clipboard when it's been selected, then own it again. It doesn't seem to work with Motif though. No biggy, primary works v. well. That's good to know, but why doesn't it work when we do it according to the spec? :) I am going to integrate your changes into a future release of xwinclip, but I cannot tell you when that will be. However, a little schedule update: snip On the other hand, shit happens, so don't expect anything extraordinary. :) Like Chris said it's suprising you can reply at all, and much appreciated. No problem, I don't want people to think that I have given up or anything. As was suggested I'm going to look at implmenting a grab the selection only when the windows clipboard has changed addition to the code. It shouldn't make a great deal of extra code but it will definitely make a minor glitch go bye bye. That was the way that the original code worked... the Windows loop became a member of the clipboard chain and ... well, it should have owned the X selection when the clipboard changed, but I don't remember if it did or not. The reason that we didn't pursue that route further was that we didn't have a way to always process the Windows message queue when a message was waiting, so we were freezing the clipboard chain and causing lots of problems for other Windows applications. Now that we call select () ourseleves we should be able to return to using the clipboard chain. I can dig up the old code, or you can just look at the notes in the Server Test Series Change Log and the xwinclip ChangeLog, then figure out which sets of source to download (the historical sources for the Server Test Series are mostly going to be in the XFree86 tree, which you can view via XFree86's cvsweb). Or, you could blindly reimplement the ClipBoard chain support... I'll have a look at integrating it into XWin as well. When more than one XWin window are open it doesn't work properly and if the x windows clients become integrated with windows ala eXceed then it won't work at all. It would probably be a good idea to allow the app to work with multiple XWin sessions. But, are you doing everything properly, such as giving each XWin window a different display number and telling each instance of xwinclip which display to connect to? Harold Cheer's, Chris _ Send and receive Hotmail on your mobile device: http://mobile.msn.com
Re: xwinclip - update and motif clipboard
Well according to the specs you're implementation is right. Own clipboard manager and grab the clipboard when it's been selected, then own it again. It doesn't seem to work with Motif though. No biggy, primary works v. well. That's good to know, but why doesn't it work when we do it according to the spec? :) Motif does some wierd clipboard antics and completely breaks the way it should work. Basically it stores all the entries under the root window as properties (xprop can show them). There is a kde app called klipper that handles the two properly but it involves making xwinclip an xt application for the xm stuff to work. Like Chris said it's suprising you can reply at all, and much appreciated. No problem, I don't want people to think that I have given up or anything. Like I said, it's much appreciated, I've been busy this week with various things but I've still checked the list so it's a very good feeling to see such a reply. which you can view via XFree86's cvsweb). Or, you could blindly reimplement the ClipBoard chain support... Honestly I'm tempted to do that, purely because it offers the oppurtunity to have a bit more of a play. The ultra2 that was going to occupy my time just blew a fuse so I'm back to the free time. It would probably be a good idea to allow the app to work with multiple XWin sessions. But, are you doing everything properly, such as giving each XWin window a different display number and telling each instance of xwinclip which display to connect to? I'm doing that properly (although a new app starts in the old display). The problem is I'm looking for a window that says Cygwin/XFree86 which of course they all will say. It may need code in XWin to provide a differentiation of window title mentioning the display number (and env variable) or something similar. Otherwise you don't know which XWin display has lost/gained focus and which to start the xwinclip operations on. I think that would also be usefull for XWin in multiple windows as well. The user would be able to see which goes where. Possibly a user additional title as well such as linux box or sun box etc. In short how do you know which Cygwin/XFree86 window is the one xwinclip is started for (x wise it's DISPLAY) but windows wise? Chris _ Chat with friends online, try MSN Messenger: http://messenger.msn.com
RE: xwinclip - update and motif clipboard
Chris, I thank you for putting so much time into developing xwinclip. I really appreciate that you got the long-awaited setjmp lngjmp functionality implemented so that we are not killed upon X Server shutdown and restart. I don't know anymore about the CLIPBOARD than what I wrote in the xwinclip source comments, which was something to the effect of, ``help! can't find CLIPBOARD documentation, how does it work?'' I am going to integrate your changes into a future release of xwinclip, but I cannot tell you when that will be. However, a little schedule update: I am taking 10 credits this semester in three classes (this is not much), I am working 30-35 hours a week at an Active Server Pages (blah :( ) job (but it pays really well), and I am working 6-8 hours a week at the National Superconducting Cyclotron Laboratory at Michigan State University (where I translate old Fortran program for VMS to Tru64 UNIX and Linux). Next week my ASP job is supposed to slow down because they haven't got another contract for me to work on, so I may, in theory, have a whole week to catch up on Cygwin/XFree86. On the other hand, shit happens, so don't expect anything extraordinary. :) Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Twiner Sent: Thursday, September 05, 2002 11:58 AM To: [EMAIL PROTECTED] Subject: xwinclip - update and motif clipboard Hi All, Quick update, got the signal working properly for ctrl-c or closing the windows command window. Solution (as the SIGINT handler is run in a seperate thread in windows) is to set a variable in the windows loop that sends the kill message that kill_xwinclip was doing. That means that all the kill_.. apps that I wanted to get rid of can be (and have). It also means that I don't need a window to handle turning on and off clipboard operations a simple close of the window would be sufficient. Also I believe that handling the xIO error as a thread within XWin should be possible but I'd still be tempted to run it seperately as xwinclip. It could work integrated if it was run as a seperate thread (would need to be anyway really), as such longjmp and setjmp should affect only that thread. Again I don't see how much sense this really makes. I do have a remaining issue that I'd like to solve, CLIPBOARD operations. The problem seems to be the application I'm using i.e. NEdit uses Motif programming interfaces (or lesstif) in the default distribution. This leaves four questions : 1) Should we try to get Motif clipboard operations (like klipper)? 2) If so how do we identify that what client owns the clipboard is a motif one (to use the motif mechanism for getting the clipboard data)? 3) Should we try to get motif clipboard before the X clipboard or after? 4) How exactly do we get the motif clipboard? I belive 1) should be a yes but as yet I'm at a loss to attempt the other 3 questions. I have read that the root window property CLIPBOARD holds the clipboard for Motif apps but xprop dumps when i do xprop -root CLIPBOARD. Either way I've have only just started looking at that issue and I'm just about to read http://www.ist.co.uk/motif/books/vol6A/ch-21.fm.html#649570 But any help would be nice from someone who knows the answers now :-) anywho, chris PS (Jehan and Harold, it was all tab characters that I was inserting, I'll change them to the two space's that Harold uses). _ Send and receive Hotmail on your mobile device: http://mobile.msn.com
Re: xwinclip - update and motif clipboard
On Wed, Sep 18, 2002 at 11:32:18PM -0400, Harold Hunt wrote: Chris, I thank you for putting so much time into developing xwinclip. I really appreciate that you got the long-awaited setjmp lngjmp functionality implemented so that we are not killed upon X Server shutdown and restart. I don't know anymore about the CLIPBOARD than what I wrote in the xwinclip source comments, which was something to the effect of, ``help! can't find CLIPBOARD documentation, how does it work?'' I am going to integrate your changes into a future release of xwinclip, but I cannot tell you when that will be. However, a little schedule update: I am taking 10 credits this semester in three classes (this is not much), I am working 30-35 hours a week at an Active Server Pages (blah :( ) job (but it pays really well), and I am working 6-8 hours a week at the National Superconducting Cyclotron Laboratory at Michigan State University (where I translate old Fortran program for VMS to Tru64 UNIX and Linux). Next week my ASP job is supposed to slow down because they haven't got another contract for me to work on, so I may, in theory, have a whole week to catch up on Cygwin/XFree86. On the other hand, shit happens, so don't expect anything extraordinary. :) Actually, given the above it is sort of extraordinary that you are answering email at all... cgf
Re: xwinclip - update and motif clipboard
Hi All, As promised an updated version of my xwinclip patch. Major changes: Now ctrl-c works properly, closes nicely, both the windows hook and the x display (and anything else after the event loop). Also a restart works for when the x server crashes/restarts/whatever so will xwinclip. This is done with setjmp and longjmp, so should work within a thread as part of XWin.exe. I've also made all my tab characters two spaces to be in line with Harolds original code and got rid of extra characters on the end of the line (due to NEdit's block operations, handy but I didn't realise they added spaces at the end of lines to the size of the block). There is still lot's of printf's every where for debugging, more so now (due to trying to get the motif clipboard working). Needless to say they don't affect the applications behaviour in XWin. Still outstanding: integration with motif? Not sure it's really worth my effort anymore. Had a go and got nothing more that hassle. It seems to use the motif functions you must only have an Xt app. As xwinclip is xlib alone the two like to cause av's when shoved together. I'm sure I can manage just to highlight text. handling of non windows clipboard change: if the windows clipboard doesn't change don't force the ownership of primary. Should not be much more hassle. Hope all works, let me know. Chris _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com xwinclip_chris_twiner.zip Description: Zip compressed data
Re: xwinclip - update and motif clipboard
Woohoo! So, when do we get to see the beautiful new code? Hi Brian, I can clean up what I have now, pre motif clipboard and do another post of it to the mailing list. Official release wise is down to Harold. I'll tidy it up tomorrow and send it out. Chris _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
