CompuServe Messages

George, I understand your concerns about API calls and all. I just want to throw in my two cents worth here. I think Microsoft would go out of business if they suddenly decided to alter the API calls so significantly as to endanger the operation of WinApps. I think that's one of the reasons MS engages in such lengthy beta-test periods for both Windows and DOS. As a result, from what I've been able to decipher from Petzold's article in MSJ, Win3.1 *adds* functions to the API bringing the total to almost 1000 including the multimedia extensions. Of course, undocumented functions may change at any moment and non-recommended approaches may become invalid but I feel no threat when I'm making legitimate API calls. Another point I'd like to raise is that in most cases whatever display/graphics functions VB added would only be go betweens the API and the run time DLL. As has been pointed out, this would make the DLL bigger but also the execution time possibly slower. When I started fiddling with Windows programming, I visited MSOPSYS to see what kind of issues the Windows programming vets were up against. Frankly, not that different from here: StetchBlt, BitBlt, DLLs, fonts, modal windows, same stuff. I felt better. One message I read has really stuck in my mind. A novice Windows programmer was seeking advice about taking the plunge into Windows programming. The consensus there was: "if you're an experienced C programmer, give yourself at least six months to learn Windows programming." In all fairness to VB – it hasn't been out that long. Costas There is 1 Reply.