Welcome Guest. Please Login or Register. Apr 6th, 2018, 12:21am
ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018. Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.
If you require a dump of the post on your message board, please come to the support board and request it.
Of course I am aware that WINLIB2A was distributed with BB4W, and it continues to be. Generally I never delete things from the distribution, even if they become obsolete (assuming they still work). But it's undocumented and I can't remember what the differences are (I have a suspicion that maybe it was designing to support context-sensitive help before *SYS 1 was introduced).
I have a suspicion that maybe it was designed to support context-sensitive help before *SYS 1 was introduced
I can confirm that. Before the introduction of *SYS 1 there was no way to intercept and respond to WM_HELP messages received from a dialogue box. Accordingly, WINLIB2A converts them into WM_COMMAND messages with a special ID value (999), which can be handled by a regular ON SYS.
*SYS 1 makes that kludge obsolete, because WM_HELP messages can now be intercepted directly. Therefore on the introduction of that command WINLIB2A was replaced by WINLIB2B (which forwards WM_HELP messages to the parent window). However on the basis that some programs might still be using WINLIB2A it remained in the BB4W distribution.
WINLIB2A is now undocumented and ought not to be used in new programs. Existing programs which use it can continue to do so, at your own risk, so long as they work as required.
Logged