thefool wrote:@dare2: hehe u should see our msn logs
well another request?
ok since u ask me so nicely to find a request, let me think...
well since the lib now spits out the process id from name (wich is the hardest part), everything can be done more easly.
But since pb compiler includes needed procedures only, many procedures wont hurt, and will just be easier to use. So another request is :
GetProcessFileName(processname.s)
hehe
but anyway its a nice lib.
Umm, ok.. here's the new lib.. haven't gotten
around to the help file or the installer... blah blah..
See original post at TOP..
GetProcessFilename() -- has been added ..
- np
Last edited by NoahPhense on Sun Sep 19, 2004 8:42 pm, edited 1 time in total.
Bonne_den_kule wrote:Your library rules . Suddenly a "find process library".
Thanks Bonne. More to come.. I'm in the process of moving, so some
delay might occur. But I have NT4 SP6a installed now. So I will be able
to test my lib on NT4 and 2000, all you guys have to do is test it on XP
for me.
Oh, I got the GetFullPathOfProcess() working.. not sure if thats what I'm
going to call it.. give me some ideas.
I wouldn't worry about that just yet. Usually in betas, there are broken things in there that will not be fixed until the final version. Thus, it may not be your library at all that is causing the problem, but a bug in PB beta. If that is the case, and you "fix" your library to work with 3.92 beta, then the final comes out, you may have to unfix your library in order to get it working again
Thus, I find it better not to ever mess nor support betas and wait until the final version.