Hi there!

Any chance I can create/send my own arguments for events?
It seems like all I'm able to do is create an event (Event(EventName,
control, ProcedureOnEvent)) and then to call that event I'm only allowed
SendMessage() or PostMessage()... which only allows 3 parameters -- all
integers.

I've got a custom event that needs a non-integer argument to deal with
it more precisely. I already created a global variable of a structure
with the required data and just passed a pointer (integer!) when calling
SendMessage() or PostMessage() but WOW if that's the best solution I'm
pretty nervous about what other junk I'll have to come up with while
dealing with WinDev.

I'm sure there's something I'm missing but I can't seem to find it. Any
help is much appreciated!

Ah sweet, thanks!


I've got a thread running in the background -- runs for a while -
typically ~1 minute. As the thread completes certain steps (let's say
there are 10 steps) the completion of the step throws up its event and
whatever windows are listening for that event catch it and respond
accordingly (the behaviour here would be determined by the event
arguments) -- and on their own thread (that's a wee bit important).

What's great about the events is that the thread can just worry about
its own stuff - it doesn't have to know who/what needs to be updated -
it only needs to shout out to the world that Step 1 is done, now Step 2
is done, now Step 3 is done, and so on and whoever wants to listen can
listen. And that's what I appreciated about PostMessage() -- just post
it, then keep on truckin'.

Cool!

Now how would I make that so that I could have multiple listeners for
the same event? -- if one window reacts to the event (thus, removing the
item from the array) before another window's queue is able to react,
then I may be a little SOL as the other window won't have the arguments.
Each window/listener would require its own global array. Now, that could
work -- until I get 10 instances of the same window. Now I'm not only
posting a message using the unique handle for each window/listener (this
is what I'm currently doing - LOVE it), I'm also forced to alias each
window so that I can target each window's global array BEFORE posting
the event.
Is my thinking correct? -- maybe I'm over-thinking it?

Very interesting!

Just to make sure I understand...

One global associative array (dictionary) (project-wide scope) with a
key of string (the event name).
Its value is a structure with another dictionary which has a key of
integer (handles of listeners) and a value of variant (the events'
argument). Once the listener has handled the event I remove that event's
handle's element.
It will be interesting to see what happens when I run 10 instances of
this thread that I'm talking about and the event fires 10 times at
approximately the same time -- I may need a Guid (global unique
identifier) to make sure that each one gets handled correctly and that
the arguments don't just overwrite each other.

Anyway - I'll put it into practice and see what happens!


Thank you very much for your time, eh!