From: "Marp" <marp AT 0 DOT 0 DOT 0 DOT 0>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Rhide and the Ctrl+C key sequence
Date: Thu, 14 Dec 2000 20:15:26 -0500
Organization: MindSpring Enterprises
Lines: 67
Message-ID: <91br78$jnj$1@slb3.atl.mindspring.net>
References: <91bf72$kn0$1 AT plutonium DOT btinternet DOT com>
NNTP-Posting-Host: 04.30.99.a3
X-Server-Date: 15 Dec 2000 01:13:12 GMT
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


"Tim Nicholson" <djgpp_mail AT gizzy DOT co DOT uk> wrote in message
news:91bf72$kn0$1 AT plutonium DOT btinternet DOT com...
> Hi,
>
> Having spent the last X years writing software using Window's GUI IDE's
such
> as Delphi I am finding Rhide a bit tiresome. In order to make it more
> friendly (IMHO) I decided to map the CUT, PASTE and COPY keys to Ctrl+X,
> Ctrl+V and Ctrl+C.

The default keypresses in rhide for those operations are also the same in
most windows programs, too. If you get used to using them instead (in both
windows and rhide), you might not find the CTRL+C issue to be much of a
problem. Many windows programs list only the CTRL+KEY shortcuts you
specified, but also support the key shortcuts used by default in rhide (for
cut./copy/paste that is).

More...

>
> The problem is this...
>
> Rhide detects Ctrl+C as a 'break request' and thinks that I want to
> interrupt the program.

Yes that's usually what you use CTRL+C for in dos and console windows
programs, especially when a bug in the program prevents it from being
terminated normally, but you wouldn't want it to terminate rhide itself
which is why it has code to handle that event. The default behavior would
terminate both child and parent (rhide) programs.

More...

>
> Is there any easy way to disable this behaviour in Rhide so that I can
> detect the key sequence?
>

You can invoke rhide with the -C switch, but you loose the ability to use
CTRL+C and CTRL+BREAK to interrupt a program you're working on within rhide.
I suggest you try to get used to the default keypresses instead.

> I have all the source files and can add a bit of code in the
initialisation
> routine - problem is, I have no idea how to do it!

That may not be necessary. Try using the -C switch first to see if it solves
your problem. If you find this unacceptable, you can try adding
__djgpp_set_ctrl_c(0) which will disable a SIGINT signal for CTRL+C, but you
will still be able to use CTRL+BREAK to interrupt a program within rhide.
That may be the behavior you're looking for ;-)

Hope this helps.

Marp

>
> Thanks
>
> Tim Nicholson
>
>
>
>