Oxygen Basic
Information => Open Forum => Topic started by: JRS on July 21, 2013, 10:59:57 AM
-
Charles,
Can DLLC be used to provide a standard Windows callback function to deal with messages from common Windows controls? I know all of our testing with callbacks has been using IUP but it seems that concept is generic enough to use with the Windows API in general. (like your SAPI example)
If you have a moment, could you show a DLLC example of a Window with a close button and label saying "Hello World" and the DLLC callback handling the Windows messages for the Window?
John
-
I'll give it a go,John, but the Windows message loop takes a lot of processing power, so it may involve adding some extras to DLLC to produce a workable system.
-
Can DLLC have it's own Windows message loop handler that acts like the IUP event function? I don't see anything having to change as far as the callback work you have already done.
-
Yes, the message loop is the heart of a windows program. But it can be threaded for asynchronous operation.
-
(https://upload.wikimedia.org/wikipedia/commons/3/33/Rumpelstiltskin.jpg)
It would be nice to have a DLLC message loop function that you could specify the windows messages (events) the script is interested in. A way to send Windows messages would also be important. All the messy message cracking / filtering should be done at the DLLC level.
Just thinking out loud ...
-
Windows message loop:
(http://ourstrokeofluck.files.wordpress.com/2011/04/hamster-wheel.jpg)
-
Where all the under the covers magic happens. I like your idea of running the message loop in a thread.