Hi All:
What I need to do is to shell out to another program [GNUpg] and allow the user
to
interact with it (enter a pass phrase).
I have tried all the FpExec routines, the Shell routines etc. They ALL
execute gpg
correctly, with the proper command-line args, I see gpg's response on the
c
Hi, Can anyone check this prj to see it's happening the same than me?
Hi,
I have a little program working with Crt units without problem. I have
change the print way form, I have pushing Crt Commands inen Fifo (GotoXY,
ClrScr, ClrEol, Write,...) and I have created a Thread class to pop this
comm
> What I need to do is to shell out to another program [GNUpg] and allow the
> user to
> interact with it (enter a pass phrase).
> I have tried all the FpExec routines, the Shell routines etc. They ALL
> execute gpg
> correctly, with the proper command-line args, I see gpg's response on the
Marco van de Voort wrote:
>
> Do you use units or libraries that might put the terminal in raw mode?
> Ncurses,crt, video?
I am using "crt" for the readkey function in one of my procedures. No ncurses,
no video. I
am also smart-linking, so the only function compiled in from crt SHOULD be
readk
On 15 feb 2006, at 20:30, Bob Richards wrote:
Do you use units or libraries that might put the terminal in raw
mode?
Ncurses,crt, video?
I am using "crt" for the readkey function in one of my procedures.
No ncurses, no video. I
am also smart-linking, so the only function compiled in from
> Marco van de Voort wrote:
>
> > Do you use units or libraries that might put the terminal in raw mode?
> > Ncurses,crt, video?
>
> I am using "crt" for the readkey function in one of my procedures. No
> ncurses, no video. I
> am also smart-linking, so the only function compiled in from crt SHO
Jonas Maebe wrote:
>
> No, because the crt unit contains initialisation code, and
> initialisation code of a unit is obviously always linked in and
> executed. This initialisation code puts the terminal in raw mode...
Thanks Jonas! That was the issue. So, I will just have to write my own readkey
Marco van de Voort wrote:
> Try, - for testing purposes - to remove crt and use more basic input
> (readln), and see if it makes the problems disappear.
Indeed! Problem gone! now to hide the user's typying from the screen. I was
using readkey
and echowing back a "*" during password input. I will
