Обработка удержания клавиши.

[соdе=asm]код[/соdе]

возможно

Код (ASM):

1. cmp msg,WM_KEYDOWN
2. jne    @f
3. mov key_press_flag,TRUE
4.  . . . .
5. cmp msg,WM_KEYUP
6. jne    @f
7. mov key_press_flag,FALSE

 

Полный 30h,
после нажатия на клавишу в wParam будет код клавиши, например после нажатия на W/w/Ц/ц в wParam будет код VK_W

 

Полный 30h,
кнопку можно создать

1. через ресурсы (так делают 99,8%)
2. через CreateWindows окно класса BUTTON
3. через Template-структуру
4. вывести рисунок отжатой кнопки, а когда по этому рисунку жмут, рисунок меняется на рисунок нажатой кнопки
5. и т.д. всего 20 с лишним способов

Button Style	Description
Control Buttons
B1	No BitMaps. This button was drawn internally with colored text and background and does not have the BS_OWNERDRAWN style. It was created using SetTextColor, SetBkMode, FillRect and TextOut functions in the ButtColor procedure. In the procedure you have an option of filling the whole rectangle or creating a border and or frame. You can give it the appearance of a flat or raised button and you could get creative by using a CreatePatternBrush or CreateHatchBrush. I created a HiLite border around the rectangle on the Mouse over stage that looks like the default Windows HiLite border.
B2	Three BitMaps. This button is a standard Windows control button with a BS_BITMAP style. The images are created by using the SendMessage BM_SETIMAGE. The button has the default Windows HiLite border around the rectangle.
B3	Three BitMaps. This button has the BS_OWNERDRAWN style and the images are created with the BitBlt function. Note the images fill the complete button rectangle, No unwanted Windows default border
B4	Three BitMaps. This button has the WS_CLIPCHILDREN and BS_OWNERDRAWN style. The WS_CLIPCHILDREN style must be specified if you create a non-rectangle region. A region was created using the CreateEllipticRgn and the images are created with the BitBlt function.
B5	No BitMaps. This button has the WS_CLIPCHILDREN and BS_OWNERDRAWN style. A region was created using the CreateRoundRectRgn and the button was created using the same procedures as Style B1.
B6	No BitMaps. This button has the WS_CLIPCHILDREN and BS_OWNERDRAWN style. Two CreateRoundRectRgn regions were created, one for the button and one for its parent Window. The button was created using FillRgn, FillRect, and FrameRgn functions.
PLAY	Two BitMaps. This button has the BS_OWNERDRAWN style and the images are created with the BitBlt function. Note the images fill the complete button rectangle, No unwanted Windows default border
EXIT	Two BitMaps. This button has the WS_CLIPCHILDREN and BS_OWNERDRAWN style. A region was created using the CreateEllipticRgn and the images are created with the BitBlt function.
B7	No BitMaps. This is Windows default button.
B12	No BitMaps. This is almost a transparent control button. It uses WS_EX_TRANSPARENT for the extended style and the BS_OWNERDRAWN style and the parent window must have the WS_CLIPCHILDERN style. But if you drag another window over the button or have any activity with the button it reverts back to the default button face color. To sort of fix the proplem I intercepted the WM_ERASEBKGND message and filled the button rectangle with the parent windows background brush, which would work ok if you didn't have a parent window background like the one that is used in this demo, you can see the mismatch in the pattern, but can restore the button to transparent by resizing the main window. In Windows 2000 you can use WS_EX_LAYERED extended style and the SetLayeredWindowAttributes function to have a true transparent control button. This button has the same appearance and function as the Toolbar button Style B13 and the HotSpot button Style B14.
B15	One BitMap. This button has the BS_OWNERDRAWN style and the images are created with the BitBlt function. Note the image fills the complete button rectangle, This is a flat control button that has three stages. 1. Mouse off Creates the image and draws text on the bitmap. 2. Mouse over Creates the image and draws a raised border and text on the bitmap. 3. Mouse down Creates the image and draws a sunken border and text on the bitmap
ToolBar Buttons
B8, B10	are not subclassed and have the standard toolbar button behavior.
B9, B11, B13, B19	are subclassed in a common procedure and have have three stages, Mouse off, Mouse over, and Mouse down. All of the ToolBar buttons have the CCS_NOPARENTALIGN, CCS_NORESIZE, TBSTYLE_LIST, TBSTYLE_FLAT, and CCS_NODIVIDER style.
B8	No BitMaps. This is a standard toolbar button that has Text only. Note the TBSTYLE_LIST Style must be specified for Text. The Text is created on the button with the TB_ADDSTRING SendMessage. Notice the Windows default rectangle around the button on Mouse over and Mouse down.
B9	Three BitMaps. This is a standard toolbar button that has Images only. The Images are created by using the TB_SETIMAGELIST and TB_CHANGEBITMAP SendMessages. Notice the Windows default rectangle around the button on Mouse over and Mouse down.
B10	One BitMap. This is a standard toolbar button that has Image and Text. Note the TBSTYLE_LIST Style must be specified for Text. The Image was created by using the TB_SETIMAGELIST and the Text with the TB_ADDSTRING SendMessage. Notice the Windows default rectangle around the button on Mouse over and Mouse down.
B11	Three BitMaps. This is a custom toolbar button and the images are created with the BitBlt function. Note the images fill the complete button rectangle, No unwanted Windows default border
B13	No BitMaps. This is a custom transparent toolbar button and the text and border are created with the ButtonType4 procedure. This button has the same appearance and function as the Control button Style B12 and the HotSpot button Style B14.
B19	No BitMaps. This is a custom colored toolbar button the color, text, and border are created with the ButtonType4 procedure. This button has the same appearance and function as the Control button Style B18 and the HotSpot button Style B20.
HotSpot Buttons
B14, B16, B17, B20	No BitMaps. The HotSpots has a three stage appearence, MouseOff, MouseOver, and MouseDown. These HotSpots are basically the same each has an array of X – Y coordinates and when the WM_MOUSEMOVE intersects one of these coordinates it calls a procedure to draw the design of the button. The same is true for WM_MOUSEDOWN and WM_MOUSEUP.
B16, B17	are created with calls to the CreateHotButt procedure, which calls CreateRect and ButtColor.
B14, B20	are created with calls to ButtonType4 procedure
B14	has the same appearance and function as the Control button
B12	and the Toolbar button Style B13.
B20	has the same appearance and function as the Control button
B18	and the Toolbar button Style B19