Christian,
Perfection! :)
>>"1. I copied your VFP2C32.FLL and CPARSER.DLL to my test folder."
>
>cparserd.dll is only needed by the frontend compiler ..there's no need to put it into the apps directory
What I did notice was that I can't path to your VFP2C32.FLL. Everything works great if VFP2C32.FLL is in my current folder. But if I use SET LIBRARY TO C:\CHRISTIAN\VFP2C32.FLL, I get all sorts of errors - both "Can't find function" errors (can't find READINT, WRITEINT, etc) and then my VFP system gets flakey. Is there code that assumes a current directory vs. the directory where VFP2C32.FLL was loaded? Just a guess.
Happy to provide additional testing if you want it.
>>"4. On my system, moving the toolbar to the top of my _SCREEN resulted in violent flashing (attempted docking?). I think you may have to change the value of 19 to 20 in the line of code where you call ClipCursor()? Or perhaps this is a system dependent value? (I'm running XP SP2, small fonts, 1024x768)"
>
>yes, i think one has to use SYSMETRIC functions
On my system, I changed 19 to 21 and everything worked great. I'm going to study how these constants are calculated. Hopefully they're based on a sysmetric() value and not the current phase of the moon (LOL!) when Calvin Hsia was pumping out VFP code.
>> "5. When I tried to re-run your code, I received the following error message.
>
>InitVFP2CLibrary is meant to be called once at app startup ..., not multiple times.
OK, works fine now.
Comment: It would be great if your InitVFP2CLibrary() recognizes that it has already been initialized so that calling it a 2nd time doesn't result in a false error ... I know ... picky, picky, picky :) You can tell me to go pound sand (hope that translates) and I won't take it personally!
> I've already thought about writing only minimal documenation and instead provide an intellisense script that tells one enough how to use the functions. The problem is I really like coding but my feelings about writing docu are quite the opposite :)
I like your idea of the intellisense script with minimal documentation - that's an excellent idea and would be a great start! Besides, you know that no self respecting developer EVER reads the documentation: )
BTW: I share your feelings about THE DREADED
documentation phase :)
Thanks again for your help on this thread! I am very excited about the possibilities of using the "CC" Craig/Christian enhanced toolbar class for all sorts of UI possibilities. Personally, I feel like you guys have already given me VFP 9.5 ... and when you're done with your VFP2C32.FLL, I'll be at VFP 10!
Malcolm