On Fri, 12 Dec 2003, Alexandre Julliard wrote:
No, there is an SBM_GETRANGE16 message apparently, only it's not documented. What is needed is to investigate how that message is supposed to behave, and then implement the proper translation in WINPROC_MapMsg32ATo16.
and what way could it be done in? do you mean writing win16 test app to catch that SBM_GETRANGE16 one? or is it just about handling of ordinary message (SBM_GETRANGE) under odinary win32 system? eghm.. can you explain the process of investigation by using some examples, please? i'd be glad to help.