The Purebasic IDE currently reads API calltips from one huge file called APIFunctionListing.txt.
This file is extremely outdated, but I think the community would be able and willing to update it.
But to make this happen it really needs to be spitted into multiple files.
We already have a connection between *.lib files and *.imp files inside PB_compilerhome + "\PureLibraries\" .
So if we would have a directory called APIFunctionListing that will be scanned for separate *.txt files,
it would not be a frustrating job for everyone how is willing to help, to update them.
APIFunctionListing - split into multiple files
Re: APIFunctionListing - split into multiple files
It would be nice to have this updated. In the meantime, the current list updated to properly show parameter details... Example;
VariantTimeToSystemTime
to..
VariantTimeToSystemTime (dblIn, lpSystemTime)
however, these APIs probably weren't tested and perhaps that's why no interest of having complete API calltips.
Currently, VariantTimeToSystemTime is wrongly defined, so I'm guessing there are even more from that APIFunctionListing file like that.
VariantTimeToSystemTime
to..
VariantTimeToSystemTime (dblIn, lpSystemTime)
however, these APIs probably weren't tested and perhaps that's why no interest of having complete API calltips.
Currently, VariantTimeToSystemTime is wrongly defined, so I'm guessing there are even more from that APIFunctionListing file like that.
ʽʽSuccess is almost totally dependent upon drive and persistence. The extra energy required to make another effort or try another approach is the secret of winning.ʾʾ --Dennis Waitley
Re: APIFunctionListing - split into multiple files
Yes, these API's are defined in the imp files. Look at the oleaut32.pb in svn.purebasic
Having respected APIFunctionListing text files it also would be easy to find wrong ones.
Having respected APIFunctionListing text files it also would be easy to find wrong ones.