(FAIRLIGHT) sleep w/inkey, certain keys cause processing to pause

[Filepro List]

----- Original Message ----- 
From: "Fairlight" <fairlite at fairlite.com>
To: <filepro-list at lists.celestial.com>
Sent: Wednesday, April 13, 2005 11:29 PM
Subject: Re: sleep w/inkey, certain keys cause processing to pause

> With neither thought nor caution, Filepro List blurted:

Fairlight, What is this supposed to mean. Are you some kind of  wise ass or
what? I wrote in asking how to break out of processing that was using the
sleep command with a keystroke. Everyone said to use the inkey. Well you
know as well as me, that if the wrong key can be pressed eventually it will.
In this case using the inkey if the wrong key was pressed or bumped the
processing will freeze forever. I am asking for a solution to the problem
not rude comments.

If you are so damn intelligent, tell me, how to break out of a processing
using the sleep command where I don't have to worry about someone pressing
the wrong key and actually freezing the processing. Don't even start on
about timers, thats not what I asked. Keystrokes, are what I am looking for.

well
where is the solution
come on now
lets have it
must be simple
why would anyone have to write the list about this
it's just soooooo simple

If this is the kind of response is common of the Fileorp List I think it
SUCKS. I thought the list was to communicate and get help, NOT to receive
demeaning comments from someone like Fairlight, who, by the way, I don't
believe even answred the question that was asked.

Mike Fedko


> > I wrote in about breaking out of sleep command with a keystroke. The
inkey works great, Thanks. The problem I found using inkey is that some keys
actually pause the processing, until another key is pressed.
> >
> > I know these keys pause the processing (caps lock, screen lock, pause,
numlock, F11, F12,ctrl&", ctrl&:). Some of these are odd and not likely
pressed by accident but (numlock, caps lock) could be a problem.
> >
> > Is there any way to lock out the keys causing the pause?
>
> I strongly suspect that the processing is not actually pausing, so much as
> you're not generating anything INKEY understands, therefore it's still
> waiting.
>
> CapsLock and ScreenLock are both scankey-only.  They don't actually
resolve
> to a keysym.  The control codes...I would have to do the actual math, but
> offhand I'm guessing that mathematically they don't even work out to a
> valid character.
>
> F11 and F12 are a bigger mystery to me, as I know someone that used to map
> Save to F11, so I know fP knows about it.  I can't explain these two away.
>
> Sounds like you're using combinations that filePro is not designed to look
> for--mostly invalid control keys and scankey-only keys (caps-lock
shouldn't
> work any more than shift, alt, or control) that are really modifiers
> anyway, not real keys that resolve to a mapping.
>
> mark->
> -- 
>           *****   Fairlight Consulting's Software Solutions   *****
> OneGate Universal CGI Gateway:
http://onegate.fairlite.com/
> FairPay PayPal Integration Kit:
http://fairpay.fairlite.com/
> RawQuery B2B HTTP[S] Client & CGI Debugger:
http://rawquery.fairlite.com/
> Lightmail Mail Sending Agent:
http://lightmail.fairlite.com/
> FairView Image Viewer for Integration:
http://fairview.fairlite.com/
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list