Dave,
Thanks - that's exactly the type of info I'm looking for.
I'm still a bit confused about placing the sys(602) calls in textbox
init and destroy methods? If you have a form that calls another form
modally, won't the modal form's textbox destroy() methods reactivate
sys(602) when the user returns to the calling form?
Did you mean to say the textbox's gotfocus/lostfocus vs. init/destroy
methods?
Malcolm
<snip>
From: "David T. Anderson" <davidtan .at. davidtanderson .DO.T com>
I was using OS(10) to tell me if TS was running, but that was a mistake.
As you mentioned ealier, it only signifies of it is INSTALLED.
The blind typing issue happens when a user uses RDC from XP to XP. Some
textboxes won't display what has been typed until the user tabs off the
field. It appears to have something to do with code firing in the
InteractiveChange.
I used to execute SYS(602,0) in the load of the form and SYS(602,1) in
the unload if I detected OS(10) = 272.
This can be problematic if there are grids involved, as each row is
painted individually.
I've now changed the SYS(602) calls to the init and destroy of the
applications foundation class textbox.
</snip>
©2005 Malcolm Greene |
