Tip #1 - don't use them. ACU threads aren't real threading. Don't expect control to be shifted from one thread to another all the time. The shifting isn't even controlled by the CPU. ACU shifts from one thread to another as soon as it hits certain verbs (if I'm not mistaken DISPLAY, ACCEPT, FILE IO verbs, etc).
This can produce very bizzare results if you really intend on running things in separate threads.
It is good, however, if you only want to refresh a screen while some intensive file io work is happenning in the background.
If you're comfortable with C/C++, I'd advise running the threads within a a DLL.
Tip #2 - Pay serious attention to the warning above
Thanks for the info. I eventually worked out how to multi thread with limited success. The main problem with this was using a VB ocx. If you've ever worked VB using ocx, you're in for a difficult time trying tio make it work in ACU. You need to code for ALL the events in the ocx even if you have no intention of using them.
I've recently begun experimenting heavily with OCX controls, and am actually quite satisfied with the results. For example, I implemented the control for a Web Browser (so that I can dynamically create an HTML report and show it), and did not find that I had to intercept and handle all the events generated by this control. What exactly are you referring to when you say you have to handle all events? Which control are you working with?
BTW - AcuGT 5.2 has an improved support for OCX's. The AXDEFGEN utility supports Library controls as well as references, whereas previous versions did not.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.