[EMAIL PROTECTED] wrote:
What problems do you have with regisitering on the Lazarus site or the bug
tracker?
Did you follow
http://wiki.lazarus.freepascal.org/How_do_I_create_a_bug_report ?
Where couldn't you follow this recipe?
I had an account there but I forgot the password. Yesterday I tried
"recover lost password" and I don't receive an e-mail, I tried registering
then 2 different usernames and 2 different e-mails, but didn't get the
e-mails (in 10 hours).
That is probably for the forums on www.lazarus.freepascal.org. Michael
Hess, can you look at these problems?
For the bug tracker you need to be at www.freepascal.org and it has a
different account.
***
I'll post it when I register, promisse. Ok, some of theese are not bugs,
but for cross-platform compat. But this WndProc behaviour is, I think.
There must be a way for a window to receive a message from another window.
Windows are widget things. The LCL is about controls.
I was trying that all day yesterday: WndProc does't work, and I searched
then for something else and found "OnMessage" and another "HookMainWindow"
which could do it but theese are not in Lazarus.
And the use of window class names is in sending the messages, the API
FindWindow(ClassName, Caption) returns a window handle by searching for
window class name or caption. Like here:
These are winapi calls, for which the LCL probably won't give you an
http://delphi.about.com/b/a/234306.htm
OnMessage:
----------
Occurs when the application receives a Windows message.
type TMessageEvent = procedure (var Msg: TMsg; var Handled: Boolean) of
object;
property OnMessage: TMessageEvent;
Description
Use OnMessage to trap any or all Windows messages posted to all windows in
the application. The OnMessage event occurs when an application receives a
Windows message. An OnMessage event handler allows an application to
respond to messages other than those declared in the events for
TApplication. If the application doesn't have a specific handler for an
incoming message, the message is dispatched to the window for which it was
intended, and Windows handles the message.
The TMessageEvent type is the type of the OnMessage event. The Msg
parameter identifies the Windows message, and the Handled parameter
indicates whether the event handler responded to the message. Set Handled
to True if the message has been completely handled, to prevent subsequent
processing of the message.
HookMainWindow
--------------
Enables a non-VCL dialog box to receive messages sent to the
application’s main window.
procedure HookMainWindow(Hook: TWindowHook);
Description
Use HookMainWindow to ensure that a non-VCL dialog box behaves correctly
as a child of the application, not as a stand-alone window. For example,
switching among applications with Alt+Tab treats the application as a
single task after calling HookMainWindow, rather than treating the non-VCL
dialog box as a separate task.
When the window identified by the Handle property receives relevant dialog
messages, it passes them to the dialog procedure passed as the Hook
parameter.
There is no problem with leaving a dialog box hooked into the main window,
even for extended periods. However, should the dialog box close, call the
UnhookMainWindow method to release the hook.
Too low level too, and not portable enough. So changes that these
methods are going to be implemented is low.
Vincent
P.S. Please, don't send me private messages, but post on the Lazarus
Forums or subscribe to the mailing list.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
