Difference between revisions of "User:ShakespeareFan01"
| Line 5: | Line 5: | ||
|} | |} | ||
</div> | </div> | ||
| + | |||
| + | === Mapping of Basic VB Controls to Windows Classes === | ||
| + | |||
| + | {| | ||
| + | | | ||
| + | ||Label||STATIC | ||
| + | |- | ||
| + | ||Frame||GROUPBOX | ||
| + | |- | ||
| + | ||TextBox|| EDIT | ||
| + | |- | ||
| + | ||Push Button||BUTTON | ||
| + | |- | ||
| + | ||Check Button||BUTTON | ||
| + | |- | ||
| + | ||Option Button||BUTTON | ||
| + | |- | ||
| + | ||Combo Box||COMBOX | ||
| + | |- | ||
| + | ||List Box|| LISTBOX | ||
| + | |- | ||
| + | ||Horizontal Scroll|| SCROLLBAR||HS_SCROLL | ||
| + | |- | ||
| + | ||Vertical Scroll||SCROLLBAR||VS_SCROLL | ||
| + | |- | ||
| + | ||Image||STATIC||SS_BITMAP | ||
| + | |- | ||
| + | ||Picture||STATIC||SS_BITMAP || This is more involved as a DeviceContext/hBITMAP need to be created.. | ||
| + | |} | ||
| + | |||
| + | == Windows 16 bit Support == | ||
| + | In NT these are thunked from 16 bit code up to 32 bit code,a virtaliser of an 80486 being used on non IA-32 systems. | ||
| + | |||
| + | An alternate approach to take in ReactOS is to use portions of DosBox/Qemu and fully virtualise a Win 3.x like environment, | ||
| + | a simmilar approach could be taken in handling troublesome Windows 95 era applications, which would at the very least require | ||
| + | some way of chaining an Int20/2F handler.. | ||
| + | |||
| + | Conjecture: Windows 16 bit applications all use 16 bit (286) style selectors? | ||
| + | If so then the segments can be defined on the fly for Win 3.11 style NE code, and outof segment access caught in a virtualiser.. | ||
| + | |||
| + | No idea how this could work , or could be coded though... | ||
Revision as of 01:13, 12 November 2009
| This page is the user page for an inactive user |
Mapping of Basic VB Controls to Windows Classes
| Label | STATIC | ||
| Frame | GROUPBOX | ||
| TextBox | EDIT | ||
| Push Button | BUTTON | ||
| Check Button | BUTTON | ||
| Option Button | BUTTON | ||
| Combo Box | COMBOX | ||
| List Box | LISTBOX | ||
| Horizontal Scroll | SCROLLBAR | HS_SCROLL | |
| Vertical Scroll | SCROLLBAR | VS_SCROLL | |
| Image | STATIC | SS_BITMAP | |
| Picture | STATIC | SS_BITMAP | This is more involved as a DeviceContext/hBITMAP need to be created.. |
Windows 16 bit Support
In NT these are thunked from 16 bit code up to 32 bit code,a virtaliser of an 80486 being used on non IA-32 systems.
An alternate approach to take in ReactOS is to use portions of DosBox/Qemu and fully virtualise a Win 3.x like environment, a simmilar approach could be taken in handling troublesome Windows 95 era applications, which would at the very least require some way of chaining an Int20/2F handler..
Conjecture: Windows 16 bit applications all use 16 bit (286) style selectors? If so then the segments can be defined on the fly for Win 3.11 style NE code, and outof segment access caught in a virtualiser..
No idea how this could work , or could be coded though...
