Printable View
I'm trying to find a way to fransfer a picture from a picture box, image box, or file with winsock. I've tryed transfering a file, and i don't like it. Is there a way out there that you can send pictures like you send text with winsock? If so, do you know where i might be able to find some kind of sample/example program? I know AOL Instant Messager can send pictures in a text box, how can I do it?
Here is an example of how to transfer files with the winsock control.
Here is another example, but using a status bar.
That File transfer example has a lot of bugs in it. I didn't really need a file transfer example anyway. I need a picture transfer with winsock. Is it possible? maybe pictureBox to PictureBox download??
A Picture in a picture box is just a series of bytes which of course you can send via winsock. A file is also just a series of bytes and if you know how to do this then it would appear to be straight forward right?
Well not quite. If you took the file transfer method and made your picturebox first save it's image to a file, then transfer the file to the other end, then read it into the recieving picturebox, you would have a working solution that provides you everything you aksed for.
If you want to do it without files, then you need to get into the guts of what a DIB is. All bitmaps when read into a pictureBox end up being stored as a Device Independent Bitmap in memory. SO you need to know how to access this DIB data from code and send/recieve it.
I've done all that with help from the excellent type libraries on http://vbaccelerator.com/ I haven't used winsock though but I believe it would be straight forward enough for someone who knows all the ins and outs of winsock.
One point you might like to remember though: Consider a 156k bitmap (bmp) that you save as a jpg. The jpg ends up at say 20k. You know you have lost some image quality but because of the huge reduction in size, you can live with it. Sound familiar? Well once it's in memory as a DIB, guess what? It's back up to 156k again. So if you end up going ahead and using winsock to send the data, you'll either have to live with the fact that you are sending almost 8 times the number of bytes that you really need to send, or come up with your own compression mechanism (perhaps these algorithms are publically known?).
In my opinion, saving to a file (jpeg) then sending the file or at least the bytes in the file, is a far better proposition.
I'll have a go at doing this myself, only I'm no winsock wiz so it could take me a while :)
Cheers
put an open statement in like:
Dim strBuf as string
Open "C:\FileToSend.bmp" For Input as #1
Do Until EOF(1)
Line Input #1, strBuf
Winsock1.senddata strBuf
loop
close #1
The idea is it loads the file and sends a line at a time through winsock, u then have to reassemble it at the other end by opening a new file and then writing to it each line of data sent and then to save the file with the same name and extension as the original.
This should work.
I've been working on this problem for months now and with NO avail. When I set out to do this project I thought the transferring of the pictures in the pictureboxs would be the easy part. Boy was I wrong! I know its possible but yet I cant figure it out. Anyway, Mike if you hear of anything let me know. I will email you if I do.
Wish us luck,
Todd
When sending the picture using the winsock control send it binary not TEXT(ASCII). Also you need to declare a variable as a byte array not a string. Your code would look something like this.
Dim bySend() as Byte
Dim Buffer as Integer
Dim FileSize as Long
Dim NumberOfBytesSentSoFar as Long
Dim iFile as Integer
iFile = FreeFile
Open FileToSend For Binary As #iFile
FileSize = LOF(iFile)
NumberOfBytesSentSoFar = 0
Do Until NumberOfBytesSentSoFar >= FileSize
'Set buffer to the # bytes you want to send
Buffer = 4096
If Buffer > FileSize - NumberOfBytesSentSoFar Then
Buffer = FileSize - NumberOfBytesSentSoFar
End If
'Input Binary
bySend() = InputB(Buffer, iFile)
Winsock.SendData bySend()
NumberOfBytesSentSoFar = NumberOfBytesSentSoFar + buffer
Loop
Close iFile
That all good and Thanks for the help but how do you get that back into another picture box or saved as a file?
DJTN
Before you start the code that thedee23 suggested, you should send a short string with information about the picture, such as filesize and filename. By receiving the data that thedee23's code sends, you can check if the picture has been fully transferred by comparing the size of the received data and the filesize mentioned in the header (the short string).
As for the filename, you should be writing the incoming data into the file as it comes in and checking the size of the file everytime to see if it has finished. When it has finished, you can load that picture file into the picture box.
Sunny
Before sending the data you would have to let the client know its receiving a file and the filename, then as the client recieves the text it adds it line by line to a textbox using vbcrlf to goto the next line. once achieved the serevr sends to the client that its the end of the file. The client then assembles the file onto their drive and voila. in the next day or two i will have a demo out for use, (maybe tonight).
The code comes from chapter 21 of "Visual Basic Programmer's Library", By Christopher J. Bockman, Lars Klander, and Lingyan Tang (published by JAMSA Press - ISBN 1*88413357-6).
It gives a chat example that share images real-time. The code is too big for posting here, though. Send me your email address, and I'll send it on over....
You can email me @ [email protected]
or use the link below..... AND THANX!
[email protected] <= those are Ls btw...thanks
Sunny
I sent it.... Let me know how it works out.
The file is missing somthing. activex component cant create object....Set SocketsDLL = New clsSocketsDLL.
I tried changing the dill to winsock but winsock is unable to do.. SocketsDLL.SendPic(App.Path & "\foo.bmp")
Where can I find this "socketsdll"?
Todd
Take another look at the project. It has two .VBP files - two projects. One is prjSocketsDLL.vbp and the othe is prjInternetChat.vbp. You need to compile the DLL also. Doing so will register it on your system.
Thanks to everyone who help me. I really do appreciate it! I finally just used my script for file transfer and made the additional forms transparent during the process and then linked my picture box to the file that was sent. It took a lot of patience but I think it's a lot more stable. Now the fun part begins....The cosmetics! (LOL) 8')
Thanx again guys, Now I can sleep.
Todd
Whoa! hey! I'm the one who started the post! Can someone PLEASE send it to me? I really need this! Mail me at: [email protected]
Thanks
Well I thought I had it all worked out BUT come to find out the way that I'm sending my pic can only be used on TCP so if someone is on AOL and the other on cable modem they cant send each other their pictures. :( I'm going to have to send it as a datagram like PSY said:
Open "C:\FileToSend.bmp" For Input as #1
Do Until EOF(1)
Line Input #1, strBuf
Winsock1.senddata strBuf
loop
close #1
The only bad thing about this is that I dont know how to get all this back into the other picture box on the other users machine in one piece. The pictures have streaks and big black lines in them. Am I ever gonna find the answer??
If someone knows how to get the datagram into the other picture box in one piece without overflowing the buffer please let me know.
Todd
Do you mean that AOL doesn't use TCP/IP? Would that be the service, or the browser?
I thought everyone using the internet through dial-ups was using TCP/IP now.
DJTN perhaps you could post your code that receives the data, there is likely to be a problem there.
Sunny
when I send the file to myself it works but when I send it to my friend on AOL I get a wrong protocol error. I connect with a cable modem.
Todd
here, i think, is what you have to do, i have not looked at that file that you all have but you need to connect two computers using winsock, as u would normally, then the server lets the client know that its sending a file and the client to get ready, the server has to open the file as binary, then send it on to the client as normal text, the image is then re-assembled, because, the client knows its getting a file the server is sending the data from that file line by line, the client program cretaes and opens the file and inputs the data line by line as it comes, im working on a demo now, it should work like a normal chat program would between two computers and should work with all that AOL crap. I will post a reply when my demos done.
I do not know much about AOL except what the acronym stands
for. Where I connect from there is no AOL (some may find
that a blessing from what I hear). Anyhow, I assume that
the AOL system is pretty much a closed one in which the
only connections allowed in or out are tied up in their
custom software or front end or something.
I would assumed therefor, that your friend must find out
what sockets he has available that will allow a client to
connect. It is quite possible that AOL do not allow this
at all.
As I said, I know nothing about AOL so this is all
conjecture. Many corporates lock down their internet
access with firewalls and the like so it's quite possible
you are faced with a problem like this.
I'll keep an eye on the thread to see what the final
outcome with AOL is.
Cheers
I suggest he could get someone like me to port scan him when hes online and then to see what ones are available, Od one of his trusted friends to do it.
I'm still having TRAUMA with this script. After I compile the program I can send myself my picture but when I try to send it to my friend on aol I get a runtime error 40006 ' wrong protocol or connection state for the requested transaction or request '. I've tried changing the ports I use and that doesnt help. What am I doing wrong?
Todd
The server is not accepting the connection request, make sure u have a line like this
winsock1.accept requestid
PaulLewis:
To transfer a picture in a picturebox does not require any knowledge of the structure of DIB.
All there is to do is to get the size of the Picture structure (Len(MyPicture)), and use the CopyMemory API to get all the bytes the picture conatins into a byte array, then transfer the data from the byte array to the other side. At the other side we use CopyMemory again to move the byte array into a Picture structure.
A little example might be (it's scratch):
It may not be the accurate code, but it's the general idea.Code:'We have a PictureBox named PIC.
Dim bytPicture() As Byte
Dim lngSize As Long
lngSize = Len(PictureBox.Picture)
ReDim bytPicture(lngSize - 1) As Byte
CopyMemory bytPicture(0), PIC.Picture, lngSize
'Here, the bytPicture byte array contains all the
'info that is needed to construct the picture on
'the other side.
[Edited by Sc0rp on 10-08-2000 at 05:27 PM]
It may be better to use an StdPicture object or an IPictureDisp object instead of a PictureBox.