Thursday, March 19, 2020
Yamamoto essays
Yamamoto essays Yamamoto, the man who planned Pearl Harbor increased my knowledge about the people of Japan because it introduced me to their culture, and the life and times in Japan before World War II. In Japan, the family is the basic unit of society. For example, if a Japanese has the unfortunate occurrence of producing only daughters, they will insist that one of their daughters husbands changes his last name to keep their daughter's last name alive. It was, also, not unusual for people to change their last names. Isoroku Tankano was born in 1884. In 1916, he changed his last name to Yamamoto, because the name Yamamoto was an honorable and ancient one in the history of Japan. One such figure was Tatekawa Yamamoto, who fought against the Emperor, and his forces at the Battle of Watkamatsu, during the Bosshin War. Since he was one of the leaders of the rebellion, when he was captured, he was beheaded at Watkamatsu. Since Tatekawa had no sons, Isoroku was also the future of the Yamamoto clan. Not uncommon in Japan was the fact that men got married for the purpose of producing sons to keep the family name alive. This is exactly what Isoroku did. In 1918, he got married to Reiko, who, ironically, was from Watkamatsu. They had 4 children together, 2 sons, and 2 daughters. It was the standard Japanese family, the mother in charge of the household and of raising the children. He never really loved her, because he had many extramarital affairs, and 2 of the women he "loved". The life and times in Japan right before World War 2 are simply explained: The Imperialist Japanese Army, otherwise known as the "young Turks" was steadily gaining power in the government, was assassinating anyone who did not share in their views for a united Asia (Yamamoto received many death threats, because he wanted to avoid war with the U.S.A. or with Great Britain at all costs), and was using propaganda to c...
Monday, March 2, 2020
Intercepting Keyboard Input With Delphi
Intercepting Keyboard Input With Delphi Consider for a moment creation of some fast arcade game. All the graphics are displayed, lets say, in a TPainBox. TPaintBox is unable to receive the input focus - no events are fired when the user presses a key; we cannot intercept cursor keys to move our battleship. Delphi help! Intercept Keyboard Input Most Delphi applications typically handle user input through specific event handlers, those that enable us to capture user keystrokes and process mouse movement. We know that focus is the ability to receive user input through the mouse or keyboard. Only the object that has the focus can receive a keyboard event. Some controls, such as TImage, TPaintBox, TPanel, and TLabel cannot receive focus. The primary purpose of most graphic controls is to display text or graphics. If we want to intercept keyboard input for controls that cannot receive the input focus well have to deal with Windows API, hooks, callbacks and messages. Windows Hooks Technically, a hook function is a callback function that can be inserted in the Windows message system so an application can access the message stream before other processing of the message takes place. Among many types of windows hooks, a keyboard hook is called whenever the application calls the GetMessage() or PeekMessage() function and there is a WM_KEYUP or WM_KEYDOWN keyboard message to process. To create a keyboard hook that intercepts all keyboard input directed to a given thread, we need to call SetWindowsHookEx API function. The routines that receive the keyboard events are application-defined callback functions called hook functions (KeyboardHookProc). Windows calls your hook function for each keystroke message (key up and key down) before the message is placed in the applications message queue. The hook function can process, change or discard keystrokes. Hooks can be local or global. The return value of SetWindowsHookEx is a handle to the hook just installed. Before terminating, an application must call the UnhookWindowsHookEx function to free system resources associated with the hook. Keyboard Hook Example As a demonstration of keyboard hooks, well create a project with graphical control that can receive key presses. TImage is derived from TGraphicControl, it can be used as a drawing surface for our hypothetical battle game. Since TImage is unable to receive keyboard presses through standard keyboard events well create a hook function that intercepts all keyboard input directed to our drawing surface. TImage Processing Keyboard Events Start new Delphi Project and place one Image component on a form. Set Image1.Align property to alClient. Thats it for the visual part, now we have to do some coding. First, well need some global variables: var   Form1: TForm1;   KBHook: HHook; {this intercepts keyboard input}   cx, cy : integer; {track battle ships position}   {callbacks declaration}   function KeyboardHookProc(Code: Integer; WordParam: Word; LongParam: LongInt): LongInt; stdcall; implementation ... To install a hook, we call SetWindowsHookEx in the OnCreate event of a form. procedure TForm1.FormCreate(Sender: TObject) ; begin  {Set the keyboard hook so we  can intercept keyboard input}  KBHook:SetWindowsHookEx(WH_KEYBOARD,            {callback } KeyboardHookProc,                           HInstance,                           GetCurrentThreadId()) ;  {place the battle ship in  the middle of the screen}  cx : Image1.ClientWidth div 2;  cy : Image1.ClientHeight div 2;  Image1.Canvas.PenPos : Point(cx,cy) ; end; To free system resources associated with the hook, we must call the UnhookWindowsHookEx function in the OnDestroy event: procedure TForm1.FormDestroy(Sender: TObject) ; begin   {unhook the keyboard interception}   UnHookWindowsHookEx(KBHook) ; end; The most important part of this project is the KeyboardHookProc callback procedure used to process keystrokes. function KeyboardHookProc(Code: Integer; WordParam: Word; LongParam: LongInt) : LongInt; begin  case WordParam of   vk_Space: {erase battle ships path}    begin     with Form1.Image1.Canvas do     begin      Brush.Color : clWhite;      Brush.Style : bsSolid;      Fillrect(Form1.Image1.ClientRect) ;     end;    end;   vk_Right: cx : cx1;   vk_Left: cx : cx-1;   vk_Up: cy : cy-1;   vk_Down: cy : cy1;  end; {case}  If cx 2 then cx : Form1.Image1.ClientWidth-2;  If cx Form1.Image1.ClientWidth -2 then cx : 2;  If cy 2 then cy : Form1.Image1.ClientHeight -2 ;  If cy Form1.Image1.ClientHeight-2 then cy : 2;  with Form1.Image1.Canvas do  begin   Pen.Color : clRed;   Brush.Color : clYellow;   TextOut(0,0,Format(%d, %d,[cx,cy])) ;   Rectangle(cx-2, cy-2, cx2,cy2) ;  end;  Result:0; {To prevent Windows from passing the keystrokes  to the target window, the Result value must  be a nonzero value.} end; Thats it. We now have the ultimate keyboard processing code. Note just one thing: this code is in no way restricted to be used only with TImage. The KeyboardHookProc function serves as a general KeyPreview KeyProcess mechanism.
Subscribe to:
Posts (Atom)