|
|
Post by dragonjim on Feb 25, 2017 17:43:35 GMT 1
Hi,
Thanks for that - I never realised that could happen.
Just out of interest, were you declaring Win32 functions using Declare or library functions using $Export?
|
|
|
|
Post by dragonjim on Feb 26, 2017 12:33:52 GMT 1
You are absolutely right that GFA has many of the older Win32 functions integrated into its commands and functions list, and those that you were using are among them. However (and there always seems to be a 'however' hanging around), if you Declare them in your programming as you have done, GFA no longer accesses its internal register when the functions are called but treats them as it would any other declared functions which are not integrated (this may seem odd but can, on occasions, be useful to bypass GFA's internal error trapping to retrieve an error code).
The reason I asked about which type you were exporting is that there is an odd error with GFA libraries in that, if you declare and use a non-integrated Win32 function in a library but do not export it (using $Export Dec * for instance), then no other commands or functions seem to be exported either. However, this does not seem to be the case here.
I can not reproduce the problem this end, but will add a note to the help file just in case anyone else has the same experience.
Just a thought...what happens if you keep the declared functions in the library and comment them out in the program itself?
|
|
