From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: Elijah Meeks <elijahmeeks@yahoo.com>,
Xconq list <xconq7@sources.redhat.com>
Subject: Re: Build List Limits and Hotseat
Date: Fri, 21 Nov 2003 01:09:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0311201736270.4415-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <1069367558.6833.15773.camel@odysseus.peterslan>
On Thu, 20 Nov 2003, Lincoln Peters wrote:
> I'm not aware of any support in Xconq for this kind of play. Although I
> would imagine that, at least on Linux, if you have a desktop environment
> and/or window manager that supports virtual desktops, you could put each
> player's respective window(s) on a different desktop. Of course, there
> is no security in such a setup.
I believe Jim revived the old Xt/Xaw Xconq as Xtconq for this very
purpose (not hotseat, but multiple human players potentially at
the same machine). But I could be wrong....
> If you really want to do this, and you want security, I'd imagine that
> the best solution would be for the screen to go blank when one player's
> turn ends, a message pops up saying whose turn it is and asks for that
> player's password. When the correct password is entered, the
> appropriate player's view would appear.
Strategic Conquest was like that.
Eric
next prev parent reply other threads:[~2003-11-20 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 21:22 mcdonald@phy.cmich.edu Elijah Meeks
2003-11-20 22:16 ` mcdonald@phy.cmich.edu Lincoln Peters
2003-11-20 22:18 ` hotseat Andreas Bringedal
2003-11-20 22:32 ` Build List Limits and Hotseat Elijah Meeks
2003-11-20 22:39 ` Lincoln Peters
2003-11-21 1:09 ` Eric McDonald [this message]
2003-11-21 1:13 ` Elijah Meeks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0311201736270.4415-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=elijahmeeks@yahoo.com \
--cc=sampln@sbcglobal.net \
--cc=xconq7@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).