Michael Schnell wrote:
Any Linux Desktop software uses an X interface as a display. Hence an X server is running.
This would probably be a good place to point out (for the benefit of less experienced users) that X's terminology is a bit odd: an "X server" provides graphics services to programs (in the same way that an SQL server provides database services).
So the X server is typically running on the machine on your desktop with the physically-attached screen/keyboard/mouse, even if you've logged into a headless host (e.g. a "server" in a 19" rack) where your programs and source are stored.
The exception to this is when you're running VNC in which case the X server is embedded in the VNC server (i.e. they're linked together into a single binary), and you're talking to this using a VNC client. In this scenario, c&p events have to be sent over the VNC protocol and injected into the X server, hence hopefully into your program.
If you're not running VNC, you can have any number of programs on different hosts but all the UI interaction comes through the single X server on your desktop system. My experience is that things like c&p are seamless /but/ there can be performance problems and on occasion I've seen a debugger getting confused, however if you don't see one of these cases it's to be preferred over VNC.
-- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues] -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
