Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
What is the easiest way to get Window handle value?
Message
General information
Forum:
Visual FoxPro
Category:
Windows API functions
Miscellaneous
Thread ID:
00051377
Message ID:
00052823
Views:
55
>>I thought that the LCK was included with the professional editional of 5.0. I've got basically the same stuff (make, c, c++, include files) I've had in the 2.6 LCK, but no help file. Maybe it's on the CD. I'll have to look.
>
>It is. I don't think there even is a 'standard' version anymore. The functions are documented in the
>standard FoxPro help file.
>
>>As far as ActiveX, I think that you've got to take the good with the bad. Use what you have to and forget the rest. Certainly, FoxHWnd does have its own idiosyncracies. However, if you can deal with it, I believe that it does have some advantages. What would be better is to make the form's handle (and device context) properties, like VB does. I can't believe I just wrote that again, but it sure would solve problems like this one.
>
>Sure. If I really need to I will use an OCX control. But especially in VFP updates are problematic,
>so often times I just write my own or try to plug in at a lower level then call a standard DLL
>from VFP instead.
>
>+++ Rick ---

I knew I saw that stuff somewhere. Boy, I feel like a dolt. Thanks much for pointing the location out. One thing I've noticed about the documentation versus the library is that the names in the library are sometimes truncated. For example, _WFINDTITLE() in the documentation is actually _WFINDTITL() in the library. I haven't had the chance to investigate, but it looks like there are some very useful functions, beyond those documented in FOXTOOLS.HLP, in the library. I wonder why, however, the documeentation isn't in that help file.

Regarding ActiveX controls, I agree about the problems. I think that their usage needs to be handled on a case by case scenario. Sometimes, it's extremely difficult to access the functionality they give you by other means. In this case (FoxHWnd), I think that the control was developed to address the lack of hWnd and hDC properties (the latter of which should have been included). As a result, there shouldn't be the problems that sometimes occurs with other controls which weren't developed specifically for FoxPro.

George

PS I've enjoyed your articles in Advisor. I'm anticipating using them to assist in developing our own web based applications in the future.

g
George

Ubi caritas et amor, deus ibi est
Previous
Reply
Map
View

Click here to load this message in the networking platform