Why did somebody delete the .dll post i made? I was trying to read from it and learn. Could Craz3d please say what he did, about the CreateObject, im TOTALLY confused!
http://www.google.com
Quote from: Blaze on March 14, 2005, 01:36 PM
http://www.google.com
That doesnt answer why somebody deleted the topic and what CrAz3d said. But in a way i can just use it to search. Bah. I wanna know why my topic was deleted though.
Maybe its the fact that you want us to do all your work for you... and if we don't you say we aren't helping and to remove our posts. :-\
No. What i mean is somebody posted help. One line of code as an example. i was trying to learn and i was the edge of it, and i come bk to find its GONE. now im back to 0%. And they say vl help? ... Im quite annoyed right now
Edit:
I ask for this help AGAIN.
Once ive made my Active X .dll i want to be able to use it. Now Cr4z3d said something about CreateObject, ive forgot now cos sum1 deleted the TOPIC. I think it was
MyObject = CreateObject( ?? ?? ??)
Ok once i've got that. I would Declare it, "My.dll" and then
Dim MyObject as string
MyObject.Connect
Making a .connect in my .dll or something like that.
I THINK its done like that. Whoever deleted the topic, is there a way to put it BACK, just so i can look at it. Im extremely pissed off atm.
We do help, and this matter is being investigated. You might not ever find out what happened, we might solve it interally, but light is being shed on this to find out. Thanks for pointing out the deletion. I'm sure a moderator will own up to the delete and explain internally or publicly what happened. It could be an accident, or there could be a good reason. Either way, sorry for the inconvenience as your useful portions were also deleted.
Quote from: QwertyMonster on March 14, 2005, 01:51 PM
No. What i mean is somebody posted help. One line of code as an example. i was trying to learn and i was the edge of it, and i come bk to find its GONE. now im back to 0%. And they say vl help? ... Im quite annoyed right now
Edit:
I ask for this help AGAIN.
Once ive made my Active X .dll i want to be able to use it. Now Cr4z3d said something about CreateObject, ive forgot now cos sum1 deleted the TOPIC. I think it was
MyObject = CreateObject( ?? ?? ??)
Ok once i've got that. I would Declare it, "My.dll" and then
Dim MyObject as string
MyObject.Connect
Making a .connect in my .dll or something like that.
I THINK its done like that. Whoever deleted the topic, is there a way to put it BACK, just so i can look at it. Im extremely pissed off atm.
Shouldn't MyObject be an
Object, not
String?
Quote from: Grok on March 14, 2005, 03:05 PM
We do help, and this matter is being investigated. You might not ever find out what happened, we might solve it interally, but light is being shed on this to find out. Thanks for pointing out the deletion. I'm sure a moderator will own up to the delete and explain internally or publicly what happened. It could be an accident, or there could be a good reason. Either way, sorry for the inconvenience as your useful portions were also deleted.
Looking at the time it was deleted, but im not accusing anybody here, the only admin on was Kp. No hidden people or anything. Im not accusing him, but hey.
I would like for it to be brought back, if possible. But i did PM Craz3d to say what he did say (if he can remember). And if he does respond with correct information, the topic wont be needed. Although it might for others to get help. Thank you for looking into the problem.
UserLoser: You are correct. My mistake.
dll project code:
Public Sub Connect(address,port)
form1.winsock1.connect address, port
end sub
Host project code
Dim Obj as object
set obj = createobject("Project1.Class1")
Obj.Connect "battle.net",6112
I think I forgot to SET 'obj = ' last time, this should work. You can always keep going with this and probably add your own events
Effect, not everybody is a brainy vb programmer. He "wasted" his time helping me because he is a kind person.
Thank you CrAz3D for your help.
Edit:
I have this at the moment:
Dim MyObj as Object
Set MyObj = CreateObject("BNLC.BNLCCore")
BNLC being my Project name. I put the " in and when i type BNLC. i have no choice, and still no choice even without the ". So im guessing something is wrong? Could somebody please explain what i've done wrong? And how i could fix it? Thanks in advance! :-*
Edit 2: Unless it doesnt give u a choice, and it will still work. But still. Thanks in advance!
Edit 3:I have this
Private Declare Function Mydll Lib "mydll.dll" ()
Dim Obj1 As Object
Set Obj1 = CreateObject("BNLC.BNLCCore")
So if i typed "Mydll.Connect", would it go to the Mydll.dll and go to the function "Connect", and do it?
If it does, why do i need
Dim Obj1 As Object
Set Obj1 = CreateObject("BNLC.BNLCCore")
Bit confused. Explain? :-\
Quote from: QwertyMonster on March 15, 2005, 09:41 AM
Private Declare Function Mydll Lib "mydll.dll" ()
Dim Obj1 As Object
Set Obj1 = CreateObject("BNLC.BNLCCore")
So if i typed "Mydll.Connect", would it go to the Mydll.dll and go to the function "Connect", and do it?
If it does, why do i need
Dim Obj1 As Object
Set Obj1 = CreateObject("BNLC.BNLCCore")
Bit confused. Explain? :-\
No, Declaring a blank library isn't going to make vb read that archive. It will check local archives for one with a project name BNLC, then go to the BNLCCore class module. IIRC
Ok. So i will need all that code for it all to work. But will the person who uses the .dll too in their code, will they need all that, in order for it to work?
Declaring a procedure in a dll, is assuming that your only going to use that function, you don't want to load the WHOLE library, just a bit of it. (or am I wrong?)
Ok right. So once i have compiled my .dll with a function "Connect" in it, just giving out a msgbox saying "Heya!", and gave it to you. What would you need in your code for it to work? Thats what im stuck on. :-\
If I were you, I would declare the dll if its always being used, but it if was a plugin of a sort, that changes, I would do the create object method.
Public Declare Sub Connect Lib "MyDLL"()
vs
Dim Obj1 As Object
Set Obj1 = CreateObject("BNLC.BNLCCore")
--
Connect
vs
Obj1.Connect
Quote from: Blaze on March 15, 2005, 03:04 PM
If I were you, I would declare the dll if its always being used, but it if was a plugin of a sort, that changes, I would do the create object method.
Public Declare Sub Connect Lib "MyDLL"()
vs
Dim Obj1 As Object
Set Obj1 = CreateObject("BNLC.BNLCCore")
--
Connect
vs
Obj1.Connect
Ahh i see! The only thing im now thinking about is, what would the user put in his code in order to use my .dll :-\
The
dim blah as object
SetObject = blah blah(" blah blah ")
Would the person put that?
Both of the two ways I posted before would work for them.
Execelent! Im 100% understand. Now Somebody, do NOT delete this topic. Else ill murder somebody!
Gotta hand it to you Blaze, ur good at teaching.
Thanks Blaze and all others who helped! :-* :-*
I learned to do this from an example on pscode.com they accually have some well written examples and some pretty cool idea's i suggest you check it out if your still alittle unsure on what your doing.
Quote from: NetNX on March 16, 2005, 09:27 AM
I learned to do this from an example on pscode.com they accually have some well written examples and some pretty cool idea's i suggest you check it out if your still alittle unsure on what your doing.
Thanks NetNx. I heard pscode is a good website, ill check it out when i get some free time! :P