jim hughes

version.h says #define OWL_VERSION(v) v(6,36,7,0) When I have it looking the way I want I'll give you a screen shot and a summary.

Ha ha - my application is too small and unimportant to merit such an honor. Maybe after I add some new functionality... It's a serial communication (terminal) program. Yes, serial - remember that? BBSs, CompuServe etc. I wrote it in 1991 with OWL 1.0 (!) for Windows 3.1. Before that, I used Turbo C. Before that, Turbo Pascal. Philippe Khan was a hot new tech entrepreneur - today he's worth a lot of money. So, some Borland history here. OWLNext seems to work very well.

Ha ha - my application is too small and unimportant to merit such an honor. Maybe after I add some new functionality... It's a serial communication (terminal) program. Yes, serial - remember that? BBSs, CompuServe etc. I wrote it in 1991 with OWL 1.0 (!) for Windows 3.1. So, some Borland history here. OWLNext seems to work very well.

I hadn't done any software work in over 12 years, so my biggest problem was just remembering how things worked in general. I did encounter some confusion with Windows message handling, having to figure out when I would be just overriding a virtual method in OWL vs. needing a message map entry in my own code. But I have the OWLNext source for reference.

Previous post is mine.

Thanks, I missed the part about needing 6.36 for VS 2022.

Community Edition is referenced on the Supported Compilers page. At a first glance into vcmake.bat it looks like the VSINSTALLDIR environment variable isn't as expected... I guess I could start trying to modify those things... The VS Community Edition IDE doesn't find any compatible project files in \source\owlcore.

I installed the current Visual Studio Community edition, and unzipped OWLNEXT 6.30. As per the Wiki, I opened the Visual Studio Command Prompt, went to OWLnext\source\owlcore and tried to run vcmake.bat. I got "Error: unable to locate a supported compiler". Doesn't the free Community Edition work with OWLNext?