Postmessage - Windows Function, usage (AREV32)
At 30 AUG 2011 12:12:54PM Richard Hunt wrote:
I want to be able to "postmessage" from an OI stored procedure to an OI form or window. I know the proper format of the "postmessage" statement being…
SUCCESS = POSTMESSAGE(HANDLE,MESSAGE,WPARM,LPARAM)
What I would like to know is what should I use for the variable "MESSAGE"? I am going to capture the "postmessage" in the OI "WINMSG" event. I was thinking about using "WM_NULL" or 0 so that I can avoid and standard Windows messages.
Basically I want to tell the form or window that the procedure caused something to change and for the form or window to check for changes. The stored procedure and the form or window are not related. They are two completely different items.
Basically the form or window is a user status view. And I want to have several stored procedures to notify this window of user status. Things like login, logout, last command, active windows, things like that.
So I would like basically one "MESSASGE" value to capture in the OI "WINMSG" event. I can then use the "WPARAM" and the "LPARAM" variables for more details.
Any suggestions would be appreciated.
At 30 AUG 2011 03:30PM Andrew McAuley wrote:
Why not just send an OMNIEVENT to the form from your SP with the details of what you want it to do? PostMessage is designed for sending Windows' messages and whilst you could send custom messages it seems like overkill when OMNIEVENTS are there as a catchall.
You could even create your own event in the event designer called for example NOTIFY and just send a NOTIFY event to the form passing in what ever you want. Our good friends at SRP covered this some years ago.
World leaders in all things RevSoft
