(Continued from previous message)

BG> to do with the OS or its windows or session at all.

I KNOW that, and I was saying that in some situations when the apps
key definition stuff is inadequate, THEN it can be viable to patch up
its deficiencys with the key definition stuff with the *OS*s definition
stuff. Particularly that stuff you listed where the data isnt variable.

BG> But yeah, it's a bit more difficult assigning specific key
BG> functions to individual OS/2 sessions unless they are set
BG> up as objects first, but it's a piece of piss in VDMs, where
BG> you can use a different autoexec file for each session.

Thats still rather crude compared with how DV does it with a popup
key definer.

RS> Its more than a tad non orthogonal tho in that situation
RS> where you have both key definitions in the app and the OS
RS> task config. Its doable in OS2, just not so elegantly.

BG> Yeah, not worth fucking around with IMO.

Depends, in many cases you have no saw whatever in how the app does it, so
it can be handy to use the OS key definition stuff to fix some deficiencys.

BG> It's easier to stick it in the app itself,

Not if you dont have any say in how the app is done.

BG> which is why I suggested in in the first place.
BG> Should be quite doable too (but not by me).  |-)

Sure its doable, its just dinosaur stuff.

BG> The other alternative would be to allow user-input parameters to be
BG> accepted from function key macros by enclosing them in quotes, like so...

BG> function 1  \0x78,"list.exe",\0x000d

RS> Thats more than a tad too cryptic for the average user tho.

BG> Fuck 'em, that's why there are such things as docs.

Nope, thats a fucked user interface.

BG> Anyway, it certainly isn't too cryptic as far as I'm concerned.

We already know you have a severe problem between the ears |-)

BG> So waddya reckon?

RS> Dinosaur stuff.

BG> IYO, of course.  |-)

Nope, its the one true path to salvation for us all you fool.

BG> I personally happen to think think it would be a very useful
BG> feature myself,

Yeah, but you are a dinosaur.

BG> and a real advantage if coded into the native DOS
BG> version (and by extension, the OS/2 executable as well).

Nope, dinosaur stuff.

--- PQWK202