> To start the discussion here is my idea: we can make not one > (+mouse_handling) but two mutualy exclusive options: +xterm_mouse_handling > and +gpm_mouse_handling. The first option would mean getting mouse events > from xterm and using X copy buffer, so it would allow copying/pasting > to/from other X apps. The second option would cause getting mouse events > from gpm and using gpm copy buffer. I'd like to see it use the ncurses routines for mouse support rather than GPM. GPM is a linux-only program. FreeBSD uses "moused" and I imagine other operating systems have their own console mouse implementations as well. > Compiling X and gpm support into tn5250 would require linking with > additional libraries, but we can add some configure options to turn mouse > support off and allow compiling without X or gpm. > What you think? I think we should work on making the GTK version of TN5250 into something that can be used instead of xt5250. It's not far from that now, some code to allow font changes, keyboard mapping, etc. I really don't think that xt5250 is the future of tn5250 -- it's too limited. For the console version, I don't know how to copy to or from the system clipboard. I know how to get mouse events, etc... but how to send the selected data to the clipboard is a mystery to me. I also know that it'll be hard to detect the difference between a paste and keyboard input. So, maybe for the console, your .tn5250sel file is the best bet? And, of course, using the ncurses routines for mouse info since we're no longer in an xterm.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.