Recent

Author Topic: why not pack UTF8Char into (wParam+lParam) of TLMessage?  (Read 4055 times)

mek

  • New member
  • *
  • Posts: 8
why not pack UTF8Char into (wParam+lParam) of TLMessage?
« on: August 01, 2008, 01:20:48 pm »
(win32callback:1100)use lWinControl.IntfUTF8KeyPress

that cannot be filtered by subclassing TControl.WindowProc

Marc

  • Administrator
  • Hero Member
  • *
  • Posts: 2649
RE: why not pack UTF8Char into (wParam+lParam) of TLMessage?
« Reply #1 on: August 22, 2008, 09:49:47 am »
First, Subclassing the windowproc in not really supported
Second, messages are onle for existing deplhi compatebility. For performance reasons and better typechecking, we try to avoid them. So no reason to makeup a message for this.
//--
{$I stdsig.inc}
//-I still can't read someones mind
//-Bugs reported here will be forgotten. Use the bug tracker

mek

  • New member
  • *
  • Posts: 8
RE: why not pack UTF8Char into (wParam+lParam) of TLMessage?
« Reply #2 on: August 24, 2008, 01:14:20 pm »
Thanks.

I feel it's more flexible using message filter than derive a new class/set a event hander.

 

TinyPortal © 2005-2018