3 ms·
I agree, it was super useful.i also loved the way you could call any DLL function on the system, making it very useful as 'glue' However it severely missed mul
by GekkePrutser 5y ago
I agree, it was super useful.i also loved the way you could call any DLL function on the system, making it very useful as 'glue'
However it severely missed multi threading. You could make things semi -multithreaded by making sure everything was event-based but there were still so many calls that would lock the UI.
- shireboy 5y agoYou’d just pepper Doevents() everywhere and it almost seemed multithreaded.
- nedsma 5y agoI have forgotten that trick. Good ol' times. :)
- GekkePrutser 5y agoI did, but many operations would still lock. Database operations in particular. But yeah DoEvents ftw.
- ptx 5y agoSince win32 requires customizing the main event loop to handle e.g. non-modal dialogs, doesn't running nested event loops all over the place (which diverts the messages away from the custom main loop) break things like that?
- layer8 5y agoYou could run stuff asynchronously using a hidden window. Basically you could use the full win32 API and use VB procedures as callbacks (e.g. as window procedures for your own window subclass). The book “Hardcore Visual Basic” explained how to do it: https://classicvb.net/hardweb/hardbook.htm https://classicvb.net/hardweb/hardbook.htm