quote:
Originally posted by Shondoit
What do you mean "not needed at all", it does the job doesn't it?
With a detour, yes...
quote:
Originally posted by Shondoit
He got his answer. It doesn't have to be from the API...
You'll learn more from using APIs (if APIs can be used) than anything else. APIs are the stuff under the hood and do not have the limitations which activex objects like that have.
quote:
Originally posted by Shondoit
Personally, I always forget to 'Free' the Dll's I used, and a lot of scripts I looked at forget it too...
You don't need to free system DLLs (as a matter of fact, freeing them will actually not free them at all) (and as another matter of fact, you probably use more memory when you use that activex than when you use the APIs; moreover in Plus! scripting, once you loaded an activex object it stays loaded; eg: try to delete an activex dll after you've loaded it in your script, you wont be able to do it)
quote:
Originally posted by Shondoit
This way is a much cleaner way, because you don't have to use anything external, so it saves from using DataBloc structures (Interop.Allocate)
I don't find that cleaner at all, matter of opinion probably...
quote:
Originally posted by Shondoit
And by the way, these methods use an official Registry control object (StdRegProv)
Which has probably some restrictions too (like every activex) and which on its term uses the APIs anyways. So why use a detour when you can use the stuff you need directly, without any restrictions...
-------------
EDIT
quote:
Originally posted by Shondoit
(btw: I don't have access to the thread you showed... or something like that)
thread reported to be moved from private beta forum to public scripting forum... my bad, sorry
/ 
