Just thought I'd blow off some steam........
lazarus / 8-Other

----------------------------------------------------------------------
SlackBrane · 2009-04-12 14:00

AND GRRRRRRRRRRRRRRRRRRRRRRRRRRRR

I dunno. I'm sure there is probably some... useless reason for it
but..........




Sigh... That's better.

Keith

----------------------------------------------------------------------
SlackBrane · 2009-04-12 15:09

Well... that's not going to work. My ultimate bore of the moment is..

OnKeyDown
OnKeyPress
OnKeyUp

Perhaps I'm just.... oh whatever. I don't know what is going on in the
background with this, grrrr I'll take a guess, but what is the point
of them AY?. Perm any one from whatever !P or !C is and then lose it
up the way the control is implemented?

I know I am a useless pile of '' and it might be something else and it
is also all so simple when you understand it but... NO IT IS
NOT!!!!!!!!! and I need it like I need a hole in the head. The hole in
the head might be preferable to having to meep meep meep meep meep.

Being paranoid I get the impression that some bright spark (present
company excepted, it's got to be legacy) invented that lot because he
wanted to implement some sort of esoteric waste your head and doom the
rest of the planet to misery forever more thing that no-one else would
want to bother about.

Well done mate.... you just consigned data integrity to the bin. I
mean.. If I have to go through some sort of extreme hoops just to sort
out that load of crumble then, if I was not me, like as not I just
would not bother.

Now, I'll get this wrong but. I'll assume me keyboard generates some
sort of scan code thing every time I slap on it. That might mean
KeyDown KeyUp and, maybe KeyPressed. At the end of the day I don't
give a monkeys. I'll be wrong but if KeyDown and KeyUp generate a Word
then the upper Byte might mean something and the lower Byte will mean
something.

If I am going to use these 'events' to do stuff then it might be
slightly obvious that I am going to write code to deal with it so I
don't need to get second guessed by something forking the event into
its own buckets for something else to deal with before, during or
after, I get a look and the chance to kill its sad face..... or have
to waste the local populace as I try to find out how to.

I therefore Want, Need, Desire an OnKey event that, if implemented,
overrides all that other rubbish and the controls response to it,
gives me the scan code and lets me deal with it.... along with some
words about keyboard scan codes so I know how to deal with it.

I'm sure it's not the right way to ask but this rubbish is just
general vomit I don't need to beat my head against.

RANTRANTRANTRANT

 



Keith

----------------------------------------------------------------------
Marc · 2009-04-13 23:11

Your point ?

You want some global kayboard bypassing ? (you could have asked that
in one line)

You could try to mess with Application.OnMessage, but not all
widgetsets will support this.

Next time, be nice (and be warned)